Object insertion flags.

These are flags passed to object_insert_in_map() and object_insert_in_ob(). Note that all flags may not be meaningful for both functions. Most are fairly explanatory: More...

These are flags passed to object_insert_in_map() and object_insert_in_ob(). Note that all flags may not be meaningful for both functions. Most are fairly explanatory:

• INS_NO_MERGE: don't try to merge inserted object with ones alrady on space.
• INS_ABOVE_FLOOR_ONLY: Put object immediatly above the floor.
• INS_NO_WALK_ON: Don't call check_walk_on against the originator - saves cpu time if you know the inserted object is not meaningful in terms of having an effect.
• INS_ON_TOP: Always put object on top. Generally only needed when loading files from disk and ordering needs to be preserved.
• INS_BELOW_ORIGINATOR: Insert new object immediately below originator - Use for treasure chests so the new object is the highest thing beneath the player, but not actually above it. Note - the map and x,y coordinates for the object to be inserted must match the originator.
• INS_MAP_LOAD: disable lots of checkings done at insertion to speed up map loading process, as we assume the ordering in loaded map is correct.

Note that INS_BELOW_ORIGINATOR, INS_ON_TOP, INS_ABOVE_FLOOR_ONLY are mutually exclusive. The behaviour for passing more than one should be considered undefined - while you may notice what happens right now if you pass more than one, that could very well change in future revisions of the code.