- User Since
- Sep 21 2023, 2:30 AM (10 w, 5 d)
Fri, Nov 24
@Geez it seriously happened again. please for the love of god get this fixed. EVERY PLAYER ON LA 4296 just lost their spawn locations... for the 3rd time now
Wed, Nov 15
This happened again last night
Fri, Nov 10
I've also noticed that server restarts happen much much faster. Perhaps some cleanup cron isn't running properly?
Thu, Nov 9
Agree with the others. No specific in-game event seems to be the cause. It's constant.
Wed, Nov 8
Experiencing same issue. Very very unplayable.
Mon, Nov 6
ping, i guess we're just waiting for the wipe?
Nov 2 2023
in the meantime, can you restore 969A926DAA66251431068AF0057DB97A781762E8 ?
Oct 30 2023
LA-4296 in wee hours of the morning on 10/28/2023. Maybe 1am or 2am EST on 10/28/2023. This happened during a raid and allowed enemies to wipe out our base because no one could login to their existing logout locations.
Oct 28 2023
It happened again
can you restore logout positions for all players who haven't logged in yet?
Oct 5 2023
Tip for the suggestion box: When this issue happens, probably could write a little script to restore for all affected accounts on all affected servers.
Oct 3 2023
Sep 26 2023
Sep 22 2023
Please restore this ID if possible: 3C5AD4B3A76CBCDB7A3D86A011EFB94808B97B9C
I've already ran this character back to where he was. It is a bit disconcerting that a DDOS mitigation removed the field in the DB that stores player logout locations. I'm an experienced IT professional with deep knowledge of databases and code. Can't fathom how removing the field in the db that stores logout locations has anything to do with DDOS mitigation.