BYOND 4.0 Version 415.980 Release Notes

Fixes

• We accidentally made 413-414 require an updated client to play old games hosted on new builds. 415 is much more lax in this regard, so hopefully we won't be spammed by "where's the update???" messages.


• New movement foo was broken in the release builds of 413-414, causing held-down keys to be inserted into a buffer incorrectly.


• Ctrl+key and Alt+key macros did not work properly if the key was a character and an input control had focus.


• client.pixel_x/y could cause crashes in some situations. This was most visible during world reboots. (Foomer, Theodis)


• The limit on winclone()- and browse()-created windows was too conservative, since it didn't always account for windows that weren't in use. To avoid extra complexity, we've tentatively removed the limit for now. (Xooxer)


• Setting border=1 in browse() had no effect. Now a sunken border will appear around the browser control in a popup window. (Unknown Person)


• Savefiles containing infinite numbers could not be imported as text. DM is now capable of parsing 1.#INF as infinity, and -1.#INF as negative infinity. (Xooxer)


• Deleted objects that were later recreated could, in certain cases, show up incorrectly (or not at all) on the map until that part of the map was refreshed by leaving the area and coming back. (This is probably the same bug which caused invisible mobs in some games, as reported by Leftley and others.) (Xooxer)


• The Reboot query in the UI was sometimes automatically processed (incorrectly). (Polantaris)


• Downloading a very very large .zip file from the hub, containing a great many smaller files, could cause a stack overflow that crashed the pager. (Vegettassj9)


• Extracting a single dir or animation frame from an icon could cause a crash if the dir and/or frame did not exist for some of the states within the icon.


• In the window editor in Dream Maker, when changing the ID of the currently selected control, the ID would not update in the editor panel. (Audeuro)


• Controls that overlap within a window should (in theory) respect their Z order when painting, avoiding some annoying issues like controls appearing to move in front of other controls.

Features

• You can now start a game in single-player mode without launching your BYOND pager and logging in. If the pager is already online, your key will be used, but otherwise you will play as Guest. (If you need to access a savefile or something using your regular key, don't use this feature.) In Guest mode you can't host a game or join a game that is online. To always use the old behavior instead and auto-launch your pager when you start a game, you can change this setting in your preferences in DS (or the Games tab in the pager preferences).


• The command ".command" can be used to input a command just like using the Client | Command menu item in Options & Messages. A box will pop up, prompting you for a command. Any kind of command will work in this window, including the commands like .click and .reboot you can no longer run via input controls. This command can also be run via winset().


• The input control now has an is-password parameter that can be used to mask passwords with an asterisk. Reading the contents from the input.text parameter will still work, but the Ctrl+C copy operation (and associated menu item) is blocked.


• Setting the client.control_freak var to 1 at compile time will disable the Options & Messages window and most commands within (those commands can still be used by the skin itself), local user-defined macros, user-customized skins, and the default F2 screenshot macro.


• Built-in commands like .click or .winset can't be entered into an input control, but can still be used in macros, menus, buttons, etc. and in the Client | Command menu item in Options & Messages.


• world.Export() has an optional (currently undocumented) third argument: "flags". Currently the only flag is 1 (tentatively WORLD_PERSIST), eg:

   usr << world.Export("foo.com:1000",null,1) // pass a "0" in a subsequent call to this address to close the connection

  When this is set, the server will keep the connection open so that subsequent world.Export() calls to that address are more efficient. For now, this doesn't work with HTTP world.Export() calls. It also doesn't support a convenient way for the recipient server to communicate back to the host server through the persistent connection (outside of the world.Topic() return value). For now, if the recipient wants to contact the host at an arbitrary time, it must open a separate connection through a world.Export() to the host's port. Yes, this is stupid.
  In theory, this system can be used to communicate between BYOND and outside (eg, C++/Java/etc) servers. We'll document the communication protocol to make this easier.

414 Release Notes | View All