Testing 245: Sovereign Worlds!

[james]

Update OP with details of Testing 245.2.

Can anyone still reproduce the issue where you were unable to warp to a private world?

@james

Testing 245.2:

• Fixed an issue where adjusting a private world’s color palette would clear a runtime cache of chunk timestamps used for informing clients the timestamp of chunks they need to request via the CDN. This would cause clients to be able to get out-dated versions of chunks even with client restarts requiring a server restart to reload the correct timestamps from disk so that clients would then be informed to request the up-to-date timestamps again.
• Fix bug where blinksecs were shown on a World’s Resources/Settlement tab view.
• Improve display of timing information for player (and exo) worlds to more closely match Beacons behaviour outside of Warp Conduit (which doesn’t show any extra stylings for beacons and so does not for worlds either to be consistent):
  • show a “fuel bar” for worlds alongside their life time with thresholds appropriate for exo and player worlds (exo being shorter with max at 7 days and “low fuel” at 1 day compare to player with “low fuel” at 7 days and max currently set to 180 days).
  • show different icon colours in worlds list for player and exo worlds to highlight those that are “low fuel” or that are locked player worlds and for player worlds whether they are owned by you or someone else in addition.
  • show a warning symbol in red/black matching beacons when a world is “low fuel” or “locked”.
  • show a red warning symbol in the Places screen alongside the “Worlds” tab button matching the Beacons tab whenever there is a world in your list that is “low fuel”.
  • don’t show “(locked)” tag on world descriptions in the Places screen where that information is otherwise shown via the glyph color and warning icons (takes up too much space).
  • don’t show the “in your list” icon for worlds in the Places screen except for the Current World entry (by definition any other world is in your list… so pointless to show with an icon that it is in your list.)
• Fix issue where when changing world colours at private world start-up, the results of gleam lighting would not always update correctly to represent the changed colour of the gleam blocks.

Known Issues:

1. Some players appear to crash their worlds when entering via an in-world Warp. The worlds then don’t recover. You can warp from the Sanctum using the new Worlds tab. Possibly Resolved with Testing 245.1. Can anyone reproduce this?
2. Editing some (or too many) of the world colours locks the World Control. This requires a restart to fix. Resolved with Testing 245.1.
3. Sometimes the worlds chunks will appear to return to their original state. The server thinks the chunks have been modified, but the client presents them in their original state. Resolved with Testing 245.2.
4. It’s possible to crash the client by rapidly opening + closing the World Control.