@psy372 Yes definitely better this way, I tried using the update method but was missing the second parameter since the APIs for LokiJS are quite lacking, thanks for sharing

Glad to help! Although I think this should be left as unsolved to allow the actual bug to be fixed, mine is just a workaround and does not allow for example to join community servers

A temporary workaround that I've found is adding a badge specification for your user in storage, either db.json or whatever you're using.

For example, in my db.json file I've found the object containing my user's data:

{
  // ...
  "cpu": 100,
  "cpuAvailable": 0,
  "registeredDate": "2020-06-18T23:37:08.049Z",
  "credits": 0,
  "gcl": 0,
  "username": "silas",
  "usernameLower": "silas"
  // ...
}

Add the badge field with the following fields:

  "badge": {
    "type": 12,
    "color1": "#999999",
    "color2": "#999999",
    "color3": "#999999",
    "flip": false,
    "param": 26
  }

Feel free to change the values, and save. You should now be able to see the map, which means it's probably an issue with the client handling of first time login.

Note: this obviously does not fix login on private servers where you don't have access to the database.

Hope this helps someone!

Same here, I've been trying to connect to any community server I wasn't signed up to and got the same issue. It might have something to do with the player creation or the new world selection screen (persistent world, seasonal etc)