225 Release Notes

Fixed: Dream Seeker wasn't properly drawing 24-bit icons.
Fixed: File directory changes were causing problems when saving files on disk.
Fixed: Dream Maker's map icon state generation wasn't working properly.
Fixed: Newlines inside strings in the instance editor were corrupting the map.
Fixed: There was a client command-line bug which was preventing insertion of spaces after an escaped quote inside a text value.
Fixed: Infinite loops involving growing lists weren't being detected.
Fixed: The initial size of a list (as specified in the variable declaration) was being chopped off at 65535, even though it is possible to make lists as big as 2^32 (if there is enough memory).
Fixed: Savefiles were not getting flushed right away when you didn't bother to close them before opening the same file again.
Fixed: The server was crashing when trying to write more than 65535 bytes to a single savefile buffer (like a large cache file).
Fixed: There was an obscure bug caused by doing things like savefile.dir.Add("dir1/dir2"). If both dir1 and dir2 did not previously exist, only dir2 was getting saved to the file, which had the strange effect when reloading of not showing up until you create another directory for it to attach to.
Fixed: Map pop instances were getting duplicated after a map save and reload.
Fixed: Empty regions on the north border of a map were not always saved properly.
Fixed: switch() was reporting phantom errors for certain statements involving integer ranges.
Fixed: Argument definitions which declared a variable type and assigned it a default value were generating a spurious compilation error. (Example: mob/verb/test(mob/M=null)).
Fixed: It was possible to get an erroneous double expansion if you hit space-bar twice very quickly when the expansion list was being handled by the server rather than the client. You can't get away with that kind of shenanigans anymore.
Fixed: Verb arguments of the form (obj/O in List) were not working correctly when List was an expression that could not be evaluated immediately on the client (ie a server list). It was allowing you to input objects in view as well as objects in the specified list.
Fixed: When a turf changed on the map to a form the client had never seen before, there was a moment in which it flashed blank before the new turf properties could be loaded. It was supposed to be falling back on the previous turf during that time, but was failing to do so. Now things should be hunky dory.
Fixed: Empty bodied "if" statements were not being parsed correctly
Multiple inclusions of the same dmp file are now ignored, just like dm files.
Addresses with a blank host part (byond://:2000) are now treated as though the host were "localhost". The reason this is convenient is that in worlds that aren't registered, world.address may be unknown. So if you form addresses by doing "[world.address]:[port]", the address part might be empty. (This happens to be how startup() forms its return value.) At least the resulting address will work on the server machine.
The "\t" macro can be used to produce a tab inside strings (ala "\n" for newlines).
Extra whitespace at the end of code file lines is striped before saving the file.
Optional arguments with expansion lists that could not be evaluated immediately on the client (ie server lists) were not working correctly. For example: mob/verb/MyVerb(arg1 as null in list("a","b"),arg2 in list("c")) was not allowing the user to type 'MyVerb c' as a valid command.
Note that "as null" does not mean _only_ null but null or anything in the list. You could do "as null|text," but that actually means null, or a text value, or anything in the list, which is not the same thing. Another way to make an argument optional is to assign it a default value (arg1=null in list("a","b")). That has the same effect as using the null input type. Note that one should _not_ simply add null to the expansion list to make the argument optional. The client requires immediate access to information about whether a given argument is optional and the expansion list is server-side information which is therefore not immediately accessible.
The proc "waitfor" setting and the "waitfor" instruction are now obsolete, because that is the default behavior. That means sleeping operations (like sleep(), prompt(), startup(), shell(), world.Export(), and pay()) no longer cause execution to return immediately to the caller while the current proc sleeps. Instead, the caller sleeps too (and the caller's caller and so on). If you don't want to wait for a sleeping operation, use spawn(). Also note that the server never sleeps, so procedures that are called by the server (like Enter(), Exit(), New(), Del(), and so on) will still return to the server if they sleep.
When an object is deleted, all procedures with that object as their source are terminated. This allows you to start up tickers and other sleeping procedures without worrying about somehow manually terminating them when the object dies. (If you don't want them to terminate, you can dissociate them from their source by setting src=null.)
Dream Seeker's info display has been considerably simplified. The "target" verb panel no longer exists. There is still a "stat-object", but it is controlled explicitely by the designer (and will most often just be the player's mob). Also, since there is no client-side switching of the stat-object, the right-click context menus are simplified: they no longer show the name of the targeted objects, and therefore only appear at all if the objects are targets of available verbs.