ATLAS Dev Tracker

To get back on topic, we have had the ban list in place since the launch of the title and have been actively banning folks since.. probably day 2 or day 3. Once we've enabled BattlEye, the number of bans are increasing tenfold and we're updating the global banlist to include those BE bans so that any unofficials who may not run BattlEye, but use the list can still prevent these rule breakers from playing on their servers. Since then we have wiped a few more companies, and today we ended up wiping+disbanding one as the leadership weren't able to keep some of their members from playing by the rules. You'll see that list continue to grow, especially as we make more tools to identify users who have broken the rules and are playing unfairly.

I have thought about doing something that's more akin to a 'hall of shame', but not really sure how that would fly... for now having these users banned and added to the banlist so other servers can make use of them is sufficient.
...

@mndfreeze has it. When we release a major version, you'll always need to restart your clients (and sometimes Steam) to download the update, otherwise, you won't be able to connect to any updated servers. This is in the case of going from v15 -> v16, etc.

Sometimes we'll release minor client updates, they're usually just to make sure the client is aware of changes on the server but aren't necessary to play/enjoy the game, though we always recommend downloading them if we do push them out. For instance, with the FOY update, when we added the additional fountain, it required a client-side update so without it, you would have only seen the one -- which would suck cause you may have ended up travelling to the island where you couldn't see it.

Typically our updates are server-side so they don't require clients to download patches, just redeploying and updating the servers.

Following up on character loss issue; we've fixed some cases where people were unable to connect to their characters with v15.67 and we are continuing to investigate reports. It is a priority for the team. In the interim, we recommend creating a new character if you are still effected as we cannot restore them at the moment. We appreciate your patience while we work through this and we're sorry for any inconvenience this has caused.

If the character you lost was the owner of your Company, please submit a support ticket here so we can have a GM assist you in regaining ownership.

If you would like to tell us the steps leading up to this occurring for you, please do so as it may be useful to our ongoing investigation. Include the Network on which you were playing at the time and the server. Please keep it concise ie: Network/Server/Steps prior the the issue:

Did you experience this:
- When logging in after a deployment
- Aft...