Unless they’re gonna auto level thralls, another gathering multiplier is worthless. Just like it was for half of the items I lost by using foundations I paid extra for!
Same here, it seens to be generalized on all servers
I’m on official european PVE server no #3033. Last time I logged off was 31 August arround 9:30 am CEST. Today is 2nd September,18:10 CEST and all of my placed thralls, pets and mounts dissapeared on today, on 2nd September 5:29 am CEST. For f*** sake!
This is bad. People lost thralls that aren’t available anymore. Two older clans on our server have said they aren’t coming back.
Can some1 notify Conan Exiles youtu.be content creators: wak4863, KiahOnFire, Eradicati0n, Pixelcave, smskcntr and other to put out a warning video about this happening?
1 Like
It is too late, the damage is done.
2 Likes
I will with hold judgement until server reset. But honestly reset immediately and roll back things. People might piss and moan but they would get all thralls back. How ever you look at this it is one huge screw up. And funcoms rep its the best right now. So what ever you guys do make sure it doesnt damage your rep further.
We lost ALL THRALLS from clan, RARE ONES WITH RARE WEAPONS and EXPENSIVE ARMOR.
Looks like they’re reacting:
The server I play on is being rebooted right now. Let’s hope it’s a rollback, or that one will happen soon.
2 Likes
I hope you recover everything lost.
I wouldn’t like to drop the game, lose all money I put in game and report to PSN, but I will if no solution is presented.
Please let us all know if things get fixed
The reboot of the server I play on is complete. The thrall decay time was set to 10 days. No rollback, though.
1 Like
Another reboot is happening right now.
1 Like
Thanks for the update
1 Like
Dude, read what I wrote. They didn’t just post that, they rebooted the server, they set the decay time back to 10 days. And now they’re rebooting again.
They’re doing something. Don’t be a Karen and take it out on the one person who was unlucky enough to be working over the weekend, it’s not their fault.
1 Like
I hope they will not try “locate and separate” cause of problem for months.
The cause was crystal clear, and they acknowledged it: someone put the wrong number into a setting and it got deployed to all the servers. The root cause of that is that they don’t have processes in place to prevent this sort of mistake from happening, but that’s a different story.
Why? You are the only one I see acting like Karen. Everyone else is upset but not being a dick about it.
Sadly, no rollback this time either. Let’s hope they’ll reconsider.
1 Like