ATLAS Dev Tracker

Show 'n Tell

Avast, Pathfinders it be time for a new Show 'n Tell Showcase!

Hear ye, hear ye! We be treasure huntin' fer the finest of ATLAS community creations! Show us yer mighty fleets, paint pieces, flags & sails, impenetrable forts, hellish tats, scenic screenshots, 'n entertainin' videos!

Each week, we'll be runnin' a contest where we'll select th' best o' th' bunch 'n award tha winners wit' a cash prize! Submit your entries in this 'ere thread for us to be viewin'.

We’ve created this dedicated thread for submissions. Don’t hesitate to show us what you’ve got. Last week's entries were amazing and we look forward to what you have for us this week!

A cannoneer engages in direct battle with the legendary Ghost Ship

This is a friendly contest and not intended as something highly competitive. We'd like to showcase your creations in their many s...

Aye, we're looking into the reports people have put in on the forums/discord, etc. The gun changes were made so that they would be more impactful versus higher armoured characters and as a result, their base damage was reduced. However, our gameplay team are investigating an issue where some damage multipliers may be impacting wild creatures as well as tamed.

No worries! We will get there and I understand it's frustrating at the moment, but once we've had some more time to flesh out these systems we'll be taking a pretty firm stance against cheaters, BattlEye and the ticketing system will just be the beginning -- albeit, tickets are handled manually and by a human so they're not dealt with as rapidly, and we want to be confident before issuing a ban / wipe against a player. Which is why the sooner BattlEye and our other tools are in, the better -- and therefore a priority for us

We'll be investigating reports as they come in through our ticketing system and issuing sanctions where we feel like it's necessary, it takes a while to get all these systems running but we will be clearing out the trouble players. Though it shouldn't take us much longer to get BE ready, hopefully within the next few days it'll be good to set live. We just wanted to ensure that this major version was out the door first and deal with any critical issues that may arise from it.

Could you elaborate? We're investigating reports now and whilst there are some issues and concerns we plan to address, the majority of the notes should be functional as intended as expected.

Our QA team are investigating the resource reports at the moment