BulkLimiter

the message property to use when doing something to one of our contents would cause our overall contents to exceed our capacity

the message property to use when doing something to one of our contents would make it too large to fit all by itself into this container (that is, it would cause that object's bulk to exceed our maxSingleBulk)

A container can limit the cumulative amount of bulk of its contents, and the maximum bulk of any one object, using bulkCapacity and maxSingleBulk. We count the cumulative and single-item limits separately, since we want to allow modelling some objects as so large that they won't fit in this container at all, even if the container is carrying nothing else, without limiting the number of small items we can carry.

By default, we set bulkCapacity to a very large number, making the total capacity of the object essentially unlimited. However, we set maxSingleBulk to a relatively low number - this way, if an author wants to designate certain objects as especially large and thus unable to fit in ordinary containers, the author merely needs to set the bulk of those large items to something greater than 10. On the other hand, if an author doesn't want to worry about bulk and limited carrying capacities and simply uses library defaults for everything, we will be able to contain anything and everything.

In a game that models bulk realistically, a container's bulk should generally be equal to or slightly greater than its bulkCapacity, because a container shouldn't be smaller on the outside than on the inside. If bulkCapacity exceeds bulk, the player can work around a holding bulk limit by piling objects into the container, thus "hiding" the bulks of the contents behind the smaller bulk of the container.

no description available

Flag: reveal any hidden items contained directly within me when my interior is explicitly examined, via a command such as LOOK IN <self>. By default, we reveal our hidden contents on examination; hidden objects are in most cases meant to be more inconspicuous than actually camouflaged, so a careful, explicit examination would normally reveal them. If our hidden objects are so concealed that even explicit examination of our interior wouldn't reveal them, set this to nil.

the message property to use when we're too full to hold a new object (i.e., the object's bulk would push us over our bulk capacity limit)

Adjust a THROW destination. Since we only allow a limited amount of bulk within our contents, we need to make sure the thrown object would fit if it landed here. If it doesn't, we'll redirect the landing site to our container.

Check a bulk change of one of my direct contents.

Check to see if a proposed insertion - already tentatively in effect when this routine is called - would overflow our bulk limits. Reports failure and exits if the inserted object would exceed our capacity.

Examine my interior. This can be used to handle the action() for LOOK IN, or for other commands appropriate to the subclass.

examine my interior, listing the contents with the given lister

receive notification that we're about to insert an object into this container

Verify putting something new in my interior. This is suitable for use as a verify() method for a command like PutIn or PutOn. Note that this routine assumes and requires that gDobj be the object to be added, and gIobj be self.