270 Release Notes

Fixed: Certain information in the registry was being truncated. (Gabriel)
Fixed: Lengthy file transfers via world.Export() were timing out. Also, such file transfers now take advantage of the accelerated data transfer code, which should be about twice as fast as before. (Deadron)
Fixed: The UNIX server had a networking glitch that was ultimately responsible for world.Topic() failing to return when it happened to call startup(). Also, if world.Import() was called when there was in fact no file being sent, it would never return.
Apparently the 269 "fix" to prevent DreamSeeker from staying in memory after closure didn't work for all platforms. Since we don't have the necessary machines to reproduce this, you can help us out by doing some tests on your own. We added a few new tricks and reinstated the DS "quick-closure" (in which the pager disconnects in the background). Verify that this is the case: run DS and use a task manager to make sure that it is exiting properly within twenty seconds or so of closure (most of the time it should be instantaneous). If this fails to happen, you can restore the old-style behavior by typing ".configure quick-close off" on the DS command line. Check to see if that works; if so, then we can make it the permanent default. If not, we'll have to get back to the drawing board.
Added Entered() and Exited() procs. These are called after a successful Move(). The existing Enter() and Exit() procs are still called before the movement (to check if it is allowed). By default, these new procs do nothing.
This arrangement is cleaner, because it makes the question of whether a movement is possible separate from the action that should be taken when the movement is executed. Often, you only want to specify one or the other.
Directly setting loc still bypasses all movement side-effects. If you want to force a movement but still execute any normal side-effects, you would do it something like this:
To be completely accurate, you would want to check if the movement is taking place in the map. In that case, Entered() and Exited() are called for both the turf and the area (if the object is crossing over an area boundary). That's how the default Move() proc works.
Added alert(User=usr,Message,Title,Button1="Ok",Button2,Button3). This is similar to prompt(), except it displays a message in a box with up to three buttons for the user to click on. The name of the button that was selected is returned. The first button is the default response (which is what NPCs will automatically choose).
As with prompt(), you can omit the first argument altogether. Example:
or make it a choice:
All of the prompt and alert dialogs (aside from the file prompt) are now "modeless", meaning that you can still use the command line, menus, and other interface components while they are displayed. In fact, the prompts won't even disrupt your current typing on the command line. This was a somewhat big change, so be on the lookout for problems.
Irc mode now understands the ^B and ^_ control characters that many modern IRC servers transmit for formatting text. It also auto-responds to PING requests.