BYOND 4.0 Version 475.1080 Release Notes

Fixes (more info)

BYOND Pager

• Updating a game/library while it was already being downloaded was causing the pager to send an additional request. (Zaltron)


• Sometimes when the pager had a poor connection to the hub, it did not recover gracefully and could get "stuck" in a state where it would only properly reconnect after several hours or if the pager was fully shutdown and restarted. (Falacy, Android Data)

DM Language

• The ASSERT() macro did not compile correctly when provided a list index, e.g. ASSERT(L[i]). (Kuraudo)


• Because call() looks up procs by their verb name, it failed to look up the proc correctly in some cases like call(usr,"my_proc")() even if /mob/proc/my_proc existed. If the regular search fails, call() will now fall back on trying to find the proc by its exact name. (Forum_account)

Dream Daemon

• Linux DD was not calling world/OpenPort() at startup. (SuperAntx)


• Failure to write a file on the server was not always handled gracefully, sometimes leading to a crash. (Tenkichi)


• Certain seqeuences of events during a user login could trigger a server crash. (Falacy)


• Starting multiple servers within a very short time prevented some of them from communicating properly with the hub. (Falacy)


• Certain string handling operations used by the Dantom.DB library were crashing. (Android Data)


• Dream Daemon was incorrectly reporting persistent world.Export() links as connected players.
  
  Also, measures have been added to prevent abuse of world.Export() in this fashion. (DopeboyMagic101, MasterRyuu123, Maximus_Alex2003)


• When switching to a mob with see_invisible=0 from a different value, Dream Seeker wasn't always informed of the change. (Android Data)


• Banning an IP address for the session did not work. An IP address ban was only effective if it was permanent. (Lummox JR)

Dream Daemon & Dream Seeker

• When rebooting games, some users could lose connection with a message about a security certificate failure or (in newer versions) a network read error. This could be caused by a the server and client getting out of sync, which has been fixed. Both the server and player must be using this version or newer for the fix to apply. (Android Data)

Dream Maker

• The instance editor was not always properly displaying its contents or preserving its size between runs. (SilkWizard)


• The map editor was drawing the wrong z-level in some cases. (SuperAntx)


• Importing a blank icon could crash the icon editor in certain cases. (Pyro_dragons)


• Pasting an icon from an external application into the pixmap editor did not work correctly. (Bravo1, Moonlight Memento, Kumorii)


• Copying and pasting a small piece of an icon pixmap into an icon file with a smaller overall size than the original would shrink the pasted piece unnecessarily, and possibly create extra icon states depending on where it was pasted. (Aeon Games Inc)


• The splitters in Dream Maker showed pieces of window titlebars, which caused odd behavior with some Windows themes. (Fugsnarf)


• Saving an animated icon in .gif format caused artifacts. (Isenggard, Oseliman)


• The "lib" section wasn't properly appearing on refresh actions when no libraries were present in the project initially. (Haywire)

Dream Seeker

• Luminous tiles that were also opaque did not always spread their illumination correctly. (Geldonyetich)


• Sending a null sound to a specific sound channel did not stop sounds already waiting on the channel. (SuperAntx)


• Displaying a ridiculously high number of icons could crash Dream Seeker. (Tsfreaks)


• When macros were defined in a .dms file as they were in older games, and the macro ended in \..., the text was not placed in an input control. (Higoten)


• Module music files were ignoring pattern jump commands used to loop, and instead repeated from the beginning. These files will now loop correctly when the sound is loaded with repeat=1, but please note that it will not be possible to turn the repeat setting off; the sound must be cleared by sending a null sound to its channel, or stopping all channels. (Mega fart cannon)


• Grids sometimes displayed a vertical scrollbar in situations where they would have been able to fit the whole content. (Quaddw)


• winget() was interpreting single-value results incorrectly, acting as if text was in an escaped form. (Tsfreaks)


• Changing world.maxx and world.maxy at runtime (especially world.maxx) would shift images attached to turfs over to other turfs. (Vermolius)


• When the left mouse button was held down, right mouse actions could generate right-click messages even if right-clicking wasn't supposed to be enabled. (Tsfreaks)

Features (more info)

DM Language

• world.Export() now takes an extra argument which may be a client or list of clients. If used, the keys from those clients will be sent to the remote server in a list, indicating that the sender has verified they logged in. world.Topic() receives this list (or null, if it is not used) in place of the old key argument.

Dream Daemon

• world.Export() calls are now visible in Dream Daemon, showing the IP address of the sender. These appear in the Players tab. Any individual connection can now be banned for the session or permanently.

Dream Seeker

• Dream Seeker has been updated to the latest version (as of this writing) of FMOD, 4.32.01. This will most likely have no effect, but let us know if there are any issues.

474 Release Notes | View All