Release v1.51.0 - Instance rooms

This release is yet another step to make on-boarding for new players easier, by allowing private tutorial start areas. But the feature can have many other uses cases.
Let’s introduce room instances!

Features

Room instances

It is now possible to set a room to be instantiated - meaning that everyone entering the room will exist in their own instance of it.

For multiple characters to share an instance, you can either:

  1. Lead/follow someone when entering an instance room.
  2. Summon someone while inside an instance room.

Moving from one instance room to another will have your character remain in the same instance. But if you move into an ordinary non-instance room, you will leave the instance and be unable to return to the same instance unless summoned by someone else still inside the instance.

Creating instance rooms

Anyone may use an instance room, but you must be a supporter in order to set a room as an instance room, as instances will eventually drive more resources and cost.

To set a room as instance, type:

set room instance = yes

For more info, see: help set room

If you have characters in the room, who has the room set as their home, the sweep command will send the characters to their own instance of the room.

Thanks to @Vernon_Otter, @Xetem, and others for helping me shape this feature in this topic!

GitHub issue #122 - Room instances

Improvements

Use greeting screen for welcome page

The same greeting screen shown when visiting https://wolfery.com while not logged in, can now be found at https://wolfery.com/welcome.

Thanks to @Kasseth and @Soulwing for pointing out the discrepancies to me.

GitHub issue #118 - Use GreetingScreen for welcome

Mobile screenshot

The screenshot link on the welcome screen will now open up a screenshot of the mobile interface when clicked while using a smaller screen (less than 720 pixels wide). On larger screens, the desktop interface will show.

Thanks to @Aemilia and @foxbird for posing for the screenshot once more.

GitHub issue #120 - Mobile screenshot

Renamed set room attributes

Boolean (yes/no) attributes for the set room command has been renamed to not include the prefixing is- :

set room isdark = yes

New attribute name:

set room dark = yes

The old attributes (isdark, isquiet, etc.) still work, but has been deprecated.

Fixes

Blank screen when navigating back from login
When you clicked Go to login on the greeting screen, and then pressed the browser’s back-button to return from the login to the greeting screen, you would be returned to a blank screen. This has been fixed.
GitHub issue #116 - Blank screen on back from login

Room details not found in cache
When entering a room or instance set as private, an error may occur:

Error: Resource core.room.XXX.details not found in cache

This error could cause parts of the client to stop working, requiring a reload. This has been fixed.
GitHub issue #125 - Room details not found in cache

Console command duplicated on Android
When using Samsung Keyboard as virtual keyboard on an Android device, certain roll commands (eg. roll 2d10) would result in unexpected behavior, with parts of the command being duplicated. A workaround has been added to avoid this behavior.
Thanks to @SirBadmin for reporting the issue in this thread!
GitHub issue #128 - Console command duplicated on Android

iPhone reconnect issue
While not an actual fix, we’ve tracked down the reason why some iPhone users have experienced reconnect durations of a minute or more, instead of just a second or so. And the solution is:

:warning: Disable Apple’s iCloud Private Relay

iCloud private relay seems to have a bug that corrupts the WebSocket data being sent to the server, forcing Wolfery to close down the connection.
Thanks to @Shinyuu for helping with the replication of the issue, and to @farcaller for analyzing the data and tracking down the cause!

HTML passed unescaped in messages
While resolved in an earlier hotfix-release, I want to pass thanks to @WakuWaku and @Mirrdae for being quick on reporting and analyzing the bug introduced in release v1.50.0, where HTML could be included in messages without being escaped.
It was reported in this thread and this GitHub issue.

4 Likes