**KNOWN AW ISSUE**
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
Mimbo ★
Reactions
Comments
-
If you have this issue you can “fix” it by selecting a new team to place and effectively leaving the bg. That resets things and gets rid of the error. Some weird caching bug or something
-
Out of curiosity, I clicked this. I figure “eh, let me see what happens. Worst case scenario, I can have people place again and manually adjust.” What could possibly go wrong, right? I can tell you this: it wipes the placements for the tier of map you are currently aligned with. While enabled, we couldn’t even adjust to a…
-
Do they really have to state something in black and white every time a bug arises that is obviously unintended that we shouldn’t abuse it? They’ve made definitive statements against them in the past broadly speaking. Its better to assume it’s not safe than to abuse it and be upset about the ramifications
-
I wasn’t arguing that they should/shouldn’t come into play, just highlighted that it was a conversation. That said, bugs like this that impacted economy /pve aspects of the game resulted in bans when abused. This impacts multiple aspects of the game. While I don’t think leveraging the incursions bug should necessarily…
-
I think “don’t do it” is the underlying implication. It’s clearly a bug that circumvents the scoring mechanics in war. It’s not intended. That’s why there were comments suggesting bans. TLDR: DONT DO IT
-
It’s also not okay to snap at a community manager like that. Typically, community mangers are front facing guys, they aren’t the ones diving into the weeds of the lines of code to determine what’s going on. Jax isn’t at fault. He takes the heat because of his community facing position, but he’s doing the best he can when…
-
The initial post came across (to our alliance at least) as us being accused of cheating. But the exact images that were shared displayed what appears to be a sync issue more so than a demonstration of the bug that is being discussed.
-
If that were the case, we wouldn’t have dropped ab to the node. Instead we got 0 ab. So, while your comment has merit in some cases, it’s honestly a baseless accusation here.
-
The funny thing is some of our officers would post that 😂
-
Leader of TDS-1 here. The second attempt was with a weapon x and it got it down to 26%. I stopped monitoring that fight and we didn’t care about the ab — so why lose items to it. We note all the ab we earn and have logs from our discord chat that can show that we told people to burn it down. If this is a bug, we were…
-
This happened to someone, an officer, in my alliance. They attempted to join with their 7r3 silk and two others for the lane/minis. Removed silk and added overseer and was able to join. Silk was on the war defense map 2 tiers below us. This was a T1 war. Because we were in T1 we cannot even so much as view the challenger…
-
Never set dummy data. Never know what might happen//what won’t be removed. I’ve seen funny dummy data before because it wasn’t deleted.
-
Exactly this. I lead Danxor’s alliance. Had a feeling that the code got messed up and that setting “Next Week” when it was briefly available in that window would lead to it transferring to “Current Week” when the fix was pushed. As a result, I quickly scheduled all days in all BGs. Just happens I had a moment to hop in…
