Theo Riginal

Sad how little you addressed of the forementioned bugs within a year! I found a new embarrassing one: You can't turn off friendly-fire even in PVE or the repair hammer is broken! Seriously? How can that be linked!? Wildshot Devs

Interesting, I never noticed this problem because I've always built within 12x12 or smaller. But this seems to be a feature not a bug

New rule: You can't call it seamless travel between server grids when it happens that the game often crashes with a fatal error (not only but also when travelling) and you can be surprised after restarting the game and managing to log in again (if you came around the classic infinite PrimalGameData_BP loading ) by your ship being scuttled by SOTD ships and whales How about a global trajectory of SOTD ships and whales so the surrounding grids can indicate those dangers?

At least the PC shop, where I paid the service fee and gave my PC to inspection for investing this bug, takes a second look at it again free of charge. Their first solution turned out to be wrong, afterall.

Update 1,5 is live! What changes did it bring? Positive: More figureheads More char skins More versatile and challenging SOTD sea fights due to variation of ship types Improved grappling hook mechanic Better (+more logical) NPC recruitment (first hour free claiming without costs for rescuing them from the water) Negative: Aweful new claim system, now forcing you to grind for land tax and discouraging settlement or allowing others to build on your island Still no offline protection for people who can't be online 9 hours each day on the defense Inofficial servers which didn't wipe all NPCs and player chars got converted to dwarfs (you broke your word on inofficials not requiring wipe!) (Instead of adding direction to the HUD!) Removing the option to open Atlas while on the ship steering wheel Also removing right click to see compass properly when on steering wheel Own structures now collide and damage your ships, so no more bridges to ships possible

NOOOOO! WRONG! Forget what I said! Same kick again under new 1.5 update on official servers with my new i7-4770K CPU! After all the expenses and waiting... still as clueless as before, but 300$ poorer!

I got the solution (to my case at least) if someone still is around with the omniscious Corrupted Memory #0 BattleEye kick! "All I had to do" is to buy another CPU for my mainboard after exchanging and checking about every system component. So only your fault to repeat the errors known from Ark & PUBG to go with BattleEye again Grapeshot, the rest is on BattleEye. And BattleEye support did afterall answer my ticket, but didn't help either. https://imgur.com/MHvDpjX https://imgur.com/YGuuw4X Anybody wants to buy a working i5 4670 that just cant play BattleEye games?

And apropos offlining, to give you a headsup on good game atmosphere in PVP and game theory... I'm gonna call out the upcoming changes a bad compromise for both sides, before you even launched them! Here's why: X hours windows to be raidable, rest of time fully raid-safe? Who has the time to arrange his agenda according to X hours in a game? If my years of Ark server experience taught me one thing, it's There are 2 main sides, PRO ORP and ANTI ORP PVP players. One side is concerned not to lose their stuff when logging off, the other side is more concerned that they can raid everyone at anytime, unheard of their online status. Without human mind controlling and helping in defense the offline raid is - naturally given - easier to perform and less of a risk to fail or suffer losses oneself than the raid on an online tribe/company. So without any counter-measurements installed, offline raids will be the more practiced method, which can lead to a harsh, destructive server climate and many PRO ORP players quitting frustrated having to start over and over again. No problem for the ANTI ORP side, they say offlining is part of PVP and usually recommend PRO ORP players to go play PVE. But in the case you try to bring in both sides under the same roof, it turned out there's a good differentiated ORP setup possible that fits many PRO and ANTI ORP PVP fans. An ORP which is set to have a good cooldown before having effect (to prevent offline fleeing) and only multiplying structures and tames' health or damage taken. It Makes you free of scheduling your playtime and is the needed incentive giving balance more towards going for online raids. In this scenario everybody is raidable all times unheard of their online status (ANTI ORP concern) but it requires more ammo/time to do so, in order to balance online raids to be equally lucrative in terms of effort/reward, providing offline structures and actors with more durability and thatfor some basic offline protection (PRO ORP concern). Why not trying to implement such a system right into the game, it could even balance the daily player vs. WE-only player inequality (having i.e. a 7 day runtime of ORP untill its effect is automatically disabled) and could initiate an auto-decay of structures if players haven't logged in for even longer periods of time (to keep server clean and unused space available). Edit: And please dont remove the claim flags, that was about your best improvement from Ark to Atlas imo. With it you need at least to conquer and kill sleepers in the first claim of someone, by player or cargo saddle canon. Without the need to place in claims, you dont need anything more than 1 foundation, a mortar and some mortar shots to wipe anyone offline.

- And why the hell comes 'no collision on' with 'ignore claims' to allow to place a structure ANYWHERE instead of just despite terrain collision?? Have you got an idea what an offline raiding mayhem that caused?

- Why do ships deleted by admins leave behind rudders with the ship name on and WORSE, why can you get stuck, red-pvp-damaged and scuttled when sailing through such removed ship remainings?

- If you replace a floor (foundation) with another one, it only has 5000 instead of 10000 hp, as if you stacked them. Guess that's another unnoticed bug.

-Why do some things you put in an inventory BECOME AN UNFUNCTIONAL and UNREMOVABLE BLUEPRINT in the first slot of the inventory you put it in? It destroys the 2 items that are converted into an unfunctional blueprint AND blocks 4 slots in the inventory for good! GG

-What purpose serve the saddle blueprints? You can only craft them with the skill learned anyway and they aren't in ANYTHING better than what you can craft without the blueprint for it. Same for scissors blueprint. It's like the Compass Blueprint in Ark, one must think you don't know what you're creating (since absolutely useless) or you want to annoy people finding blueprints on purpose. Not sure what's the worse option...

- Why are there "fake islands" (often only for me and not my team mates), through which I get the noise and shaking of the whole ship when we drive through? I thought there's only server-sided and client-sided. Apparently there is also something like "only-certain-clients-sided"

I create this topic as a collection of bugs or "sub-optimal" settings in Atlas you might not have noticed. As my forum history here taught me, I can't even expect a reaction let alone support, but I'd be glad already if you only noticed some of the problems! My 3 most burning questions so far... - Why do you have BREEDING TIER 3 already in the beastmastery skill tree to spent points on it, if it's NOT IMPLEMENTED yet? -Why do players die without a chance in heat or cold events? Do you think that's beneficial to the gameplay? -Why is bear taming now improved while elefant taming is nearly impossible to get to feed it without getting hit? Gameplay beneficial? I add to the list when I find or remember more unexplained problems.

Just let it slide, WildShot. GJ Let it slide and no one will care after a while. That's the responsible action. Then 3 years later on your next total conversion eh.. new game bring back the same problem for a third time. GG Had to give my PC to inspection because it didn't boot anymore correctly after about 20 times I (only) exchanged RAM slot occupation because EVERYTHING ELSE didn't help (not that this did)! Now it will cost me multiple times the game price probably, to diagnose & fix my PC entirely which wasn't broken before! Still no info given about the "Corrupted Memory #0" cause... And we are still as ignorant as before... If it was a pre-existing hardware failure, why wasn't it ever a problem for Ark untill Atlas implemented BattleEye, I wonder? Ark produced already regularly so many Bluescreens to cause any hardware problem on my PC, I guess. Would have been nice at least to get some infos on it. I'll write back on this topic if I get the PC back fixed and this kick still happens... (unless banned before).

Great, now the ONLY good server decided also to go with activated BattleEye. Now I cant play Atlas anywhere anymore! Re-Installed my whole Windows 10 and installed nothing but Steam and Atlas; same unexplained BattleEye problem! Still no comments, Jatheish or anybody??? You stole 30$ from me, pirates! BattleEye Support ignores my bug report ticket just like you of course. The very least would be to state what causes this error! The VERY LEAST!

1) Set up how? Uninstall or give permissions? I tried AVG and Avira both seem not to block any BattleEye operations. Built-in OS? 2) What's a bramier? Couldn't find that word's translation 3)Tried that already, only gets me a new prompting window after reinstalling and first starting the game, but kick still occur afterwise. 4)Disable UAC in your OS is only for trouble shooting and shouldn't be kept for long. It’s what makes it safe for you to run an administrator account as your daily user account. 5)Change of region? Where and to what purpose? Aslong as they deal with chicken shit like organic paste for stone structures, and can't reply in such major gamebreaker threads that prevent people from playing on their official servers for weeks now, how can I think they really deal with it? No answers or help given up to this point. As great as the pirat game idea with customizable ship building is, as bad is some of it's execution and customer support, sadly.

You might have the BattleEye kick AND the character loss issue from the other thread. Too bad we dont get any answers or help here in the official forums! I wonder which Grapeshot fool has set the schedule to fiddle around with crap like putting organic paste requirement for stone structures, while they ignore major game breakers like the permanent kicks from BattleEye and character deletion! You guys have priorities...

Hmm, why do you think it's related to BattleEye? Because I get kicked within 60 seconds by BattleEye for "corrupted memory #0", others get a "not responding.." message for their kick, but we all didn't get our char deleted. It's still in game but not longer usable than a few seconds. I couldn't trick it with any of the workarounds mentioned so far and there is still no single official developer answering here, sadly.

Offtopic The people who can't login because of BattleEye can post here, not just any bugs!

Still not even a statement about the BattleEye gamebreaker good job Jatheish and Co! But awesome update, I always wanted stone structures to require organic paste...

1 week passed without any fix for the BattleEye problems or any further information given! I still can't play on any official server without being kicked after seconds for a mysterious "Corrupted memory #0 kick" which nobody explains or isn't even detectable by any MemTest86 ! Jatheish Live Producer & Lead Community Manager went on hollidays? Worst customer support ever, don't you even discuss the game-breakers you release anymore?!

SInce no information is given although half the player base still gets kicked from your official servers within seconds, here's my how to better game support! 1. Bug Prevention Test new features and patches offline on several machines before taking them online. Early-Access is no carte blanche to use your players as paying beta testers. Make sure you can roll back patches and implementations in order to prevent game-breaking bugs remaining for days. 2. Bug Detection After every patch, check your forums for problems players report and cathegorise them. If those are all solvable within hours and a small patch, announce its release early to warant your player base's patience for the denial of service in the meantime. 3. Bug Correction If you need more time to resolve certain bugs, roll-back your patch and work on it offline in order not to let half your paying player base hang! If you cannot (due to legal or technical obstacles i.e.) take it back, be transparent to your players and state the facts if and why not and when there will be a solution. Keep an eye at these simple ideas of respecting the community who invest money, time and emotions in your unfinished product (just like you) and no reasonable player would be frustrated of your handling of the situation.

Guess not much happening from Grapeshot or BattleEye team to adress this. Let me know, if you're hiring better customer support that actually helps and answers...