* COMPATIBILITY: Excellent! (But you will be unable to play with others until they also upgrade to A76)
* Use of /bkgnd command is now a 'cheat'
* First Use of cheat on a new character must occur in solo mode. (so to make a cheat character, you need to be in solo mode, enable cheating in the book of options, then issue the cheat command. Should be very difficult to do this 'by accident'). Once your character is sporting its cheat count, it can cheat again in multiplayer mode as often as it likes.
* World Designers may now have as many as 1000 maps in their world (well, you may run out of other resources first, but WoS will no longer restrict you to 256 maps).
* World Designers may now use as many as nine 'extension' bitmaps per object class. So, if you need more filmstrip images for your Very Many Shields (tm), you can have a shield.bmp, shield_1.bmp, shield_2.bmp, ... shield_9.bmp Each filmstrip, of course, holds many images.
* NEW COOKIES
monster.lastFightCount
this one tells you how many monsters took part in the last fight (it is cleared to 0 at the start of a scene, and counts the number of hostile monsters added if it is a fight scene (from map or FIGHT command). Friendly monsters are not counted. Pets are not counted.)
monster.lastFightIdNN
This one lets you get the monster id of one of the monsters in the last fight. For example, if monster.lastFightCount returns '7' it means seven monsters were in the fight. You can then ask for monster.lastFightId1 through monster.lastFightId7 to get the id of the individual monsters. Then use
SET monster.id, monster.lastFight4
(for example) to set the monster selector to the 4th monster of the last fight. Then use the normal monster cookies to get whatever information you need about that monster.
Note that monster.alignment is a string you can use for anything you like. for example, you might use it to specify how many goo-goo points you get for killing the monster. You might cram several pieces of information into it. That's up to you. I just point it out here for no particular reason.
* MENU command can have up to 30 options. But you are still limited by the length of a single line of text in the quest file (1000 characters?) so you may get fewer than that if your names/labels are long.
* New MAP FLAG 524288 0x00080000
MAP_FLAG_NO_WAYPOINTS disable automatic waypoint calculations (good for mazes)
Note that you may also now use hexadecimal values when defining your map flags. If you don't know what that means, then keep using the decimal values.
* TAKEing equipped items should no longer freeze the game.
* NEW ITEM FIELD (hidden in column 5, after the EquipToken) "Item Flags"
First flag is #1 -- cannot be given. Makes an item like a seed in that it cannot be given to another player. (seeds remain hard-wired to not being given)
* NEW ITEM FIELD (also hidden in column 5): "Max Count"
This lets you specify that a player can have no more than N of this item at any given time. Note than N must be less than the current wallet limit (you cannot use this feature to increase wallet size, I mean).
* NEW COMMAND: EJECT
This is identical to the PARTY command, only it also boots the people from the scene in addition to removing them from the party. Remember the conditional specifies who gets to STAY, not who gets ejected. I imagine this will be horribly confusing, but that's life!
-------------------- He knows when you are sleeping. Posts: 10721 | From: California | Registered: Dec 1998
| IP: Logged