The event was coming down the pipeline well before any of this happened, for the record. I was also unaffected by what happened, but thanks for thinking of me
@stallion119!
Pretty much. We know they're aware of what happened, so it's safe to assume that it's being worked on and there's no need for regular status updates just to keep repeating 'we're working on it'. Everyone else, do try to remember that it took them pretty much an entire month to address the Oracle exploit and it's barely been a day since. To be a stick in the mud, this means it could potentially be several days or even weeks before this problem is fixed. The developers only have so much time in a day, and what we think is simple may not actually be so simple or be done as quickly as we think it would be, viewing things from the outside. Again, it took them nearly a month to fix this exploit in the first place because they first had to brainstorm solutions, while being busy working on upcoming content like events, Oceanic Future additions, the newly-released army management improvements, and whatever other things are going on that we haven't seen mention of yet. Unexpected/unforseen issues like what's going on right now, regardless of how incompetent/unqualified you think the dev team is, are going to have to somehow fit into what's already a busy schedule. At least, that's why I think things like this usually take more time than we'd like to get fixed. Waiting feels worse when it's waiting for a bad thing to be addressed versus waiting for something like an exploit to be fixed (since players typically benefit from exploits), but by and large both things typically take about the same amount of time to get fixed.
I think I ended up talking in circles a bunch of there, but sometimes I'm just bad at being brief.