BYOND 3.5 Beta 5 Release Notes
Version 348.905
- Fixed: a link to the Sound notes in the online Dream Maker help was incorrectly handled by the help viewer. (Jon88)
- Fixed: Dream Seeker didn't always send info to the hub when it disconnected from a game, resulting in ghost pager location entries.
- Fixed: Blend() with solid color and ICON_UNDERLAY acted as ICON_OVERLAY instead.
- Fixed: 347 client file uploads to 347 servers could cause the connection to be closed. (Neonlare and DarkCampainger)
- Fixed: rebooting a world hosted in 347 disconnected all 347 clients. (Audeuro)
- Fixed: worlds compiled in previous versions of BYOND expected MIDI files to always play one at a time. BYOND 347 introduced a change which allowed multiple MIDI files to be played at once, resulting in overlapping songs in worlds built under the old assumption. Now running old dmb files will respect that assumption and only allow one MIDI file to play at a time. Any world recompiled in BYOND 347 or later will allow multiple MIDI files to play at once.
- Fixed: world.hub_password could accidentally be initialized to a random string if not explicitly set in the DM code. It now correctly has no value if not set in DM.
- Fixed: if the BYOND key logged into a Dream Seeker client differed from the key logged into BYOND Pager, the pager erroneously reported that client's location as belonging to the pager key. Now, no location is reported for any client whose key differs from the current logged in pager key.
- Fixed: worlds hosted in BYOND 347 did not honor the host's visibility setting.
- Fixed: in Dream Maker color preferences, the foreground color is now used as the default for the "number" color. The "identifier" color setting has been removed.
- Fixed: the system tray icon stopped updating its appearance after using Windows XP's "Switch User" feature and later returning to the session.
- Significantly improved the way that BYOND Pager tracks and reports game locations to the hub.
- Reduced occurrences of redundant communications between client pagers and the hub.
- If the pager can't contact the default hub address, it will now try an alternate address. If the alternate address works, it will use that for subsequent sessions as long as it continues to work. Note that this occurs only when the Hub Address preference is left empty (Preferences -> Advanced -> Hub Address).
- If the pager exits while Dream Seeker clients are still connected, the clients will now automatically reconnect if the pager starts back up with the same BYOND key.
- If the pager can't execute one of the other BYOND programs (Dream Seeker, Dream Daemon, Dream Maker) for any reason, it now notifies the user instead of silently failing.
347 Release Notes | View All