#[NOTED] Battle Error
54 messages · Page 1 of 1 (latest)
@sacred holly we just pushed a fix for this, please let us know if you continue to have issues (you will need to update your client)
[SOLVED] Battle Error
Just saw the (!) to update, thanks!
I have the current version and am still getting battle errors like this
Having battle erros like this still
had this error 9 times today. it is very frustrating at this point and clearly the fix didn't fix it....
Still having this error too after the fix
Just curious, are you on version 0.54.1 ?
yes the game was working fine, until the patch that occurred yesterday. + the update i had today
Got it, thanks 🙂
i believe this is the latest version, and also what is causing the error i believe.
Still happening.
The team is working on a fix, will update once that's ready 
It doesn't happen every battle, which is weird? Maybe something specific to said map or objects/enemies on it
It happened on the "special boss" with the Effive Boss for me, and a handful of others from the campaign. I'm trying to pay closer attention to which ones and which units are placed, if it is a unit/soul or something like that setting it off. (I just like looking for patterns)
yeah having the same issue for a streamer i check here for
So I believe this fix will go out with tomorrows release. Thank you for the reports and for your patience 
@here hello! Is anyone still experiencing this after the update today?
@split rock people have been mentioning that the error has something to do with mages being or not in a battle. I do recall seeing mages in my battle whenever the error occurred. They said something goes wrong with the mages projective when in contact with enemies? Dunno if that is the case, but we had error right after the patch today, so it is not solved yet
ok thank you tatsu!
Agreed! What I've noticed is in the next battle after the battle error there are flames still on the new map. They go away if you refresh/reload. Got me thinking about artilleries or mages as well!
I was alerted to an update and tried to update SR. Then I can't reopen it
Update I did a fresh reinstall and it's working for me now
Awesome, @nova creek - let us know if you still run into this.
@here apologies for the ping (again) - a hotfix has just gone out for the Battle Error error. This is a suggested update, not a forced one, so you may need to update and/or refresh.
I haven't had the battle error since the most recent update, but mage fire and sludge artillery stays on the screen where it was fired in the future battles.
can confirm >>
after applying this manual update, its fixed for me. I had the issue for 3 days at least
@bright flare this might help
I haven't had an error on anything since the update, except for just now. Same battle error in the map "Stream and Let Raid"
I’m still getting this battle error.
are you on the newest version of Raiders?
Yup
just got this battle error on special boss map. had to restart couple of times before it finally went through.
[SOLVED] Battle Error
Been getting it still btw; In campaign now also.
I'm getting a battle error.
I've tried refreshing multiple times and it's still popping up.
had to update now getting this
Do you have Raiders open while attempting to update?
We are looking into this, sorry Beth!
Thank you! I saw that you posted in the raiders channel. You got this, Flocci! 
i cant load back into my battle to run it. Is there a way to fix it or is it currently being fixed?
They are looking into it and trying to get it resolved as we speak. 
thank you beautiful. I will wait then lol
Everything was fine for me until just now. I started a battle and am stuck on the loading screen. Tried to close the program and restart. The bot is still counting down, but no one else can access the battle either.
I tried ending the battle early through settings. This allowed me to restart the battle for a retry token (which sucks), and then upon starting the battle over - I'm stuck in the loading screen again. 😕
Kermond noted in another thread that a new client may ne necessary and they are working on it.
Reference: #1103386078108467290 message