I've mentioned this on the battle update thread, but it might need to be here. When I did battle quests yesterday at L17 it said I was 'still in a battle' after I had beaten the opp and gone back to the quest page to do the next one, I kept trying but it just made me battle the same opp 3 times,until I went and forfeited it. today I just went to start normal battles and its saying im still in a battle again, so I had to forfeit again, my stats page doesnt show losses though,I imagine because in reality Ive won the fight.
Is this still ongoing? If so, what browser are you seeing it on?
Im editing this post, i said it was sorted, but its still happening, just now, I won Oslyae the montre, went back to the battle page, after clicking red game over button, and tried to move on to the next opponent, but it says Im in a battle, so I go to the battle, fight again, win, click game over, and it shows me Ive won and the prize, and the count is going up, but when I try to go to a different opponent is says Im already in a battle, and there is Oslyae again,so I end up fighting the same one over and over, Im going to see what happens if I forfeit.
I had to click to forfeit twice before it changed to a normal page, its like its adding up the fights im doing and im sort of 'behind' myself somehow ,I'm not good at explaining!
I've checked the statistics for Oslyae and it says Ive won 8 times, and not lost or drawn despite having had to forfeit? Im confused lol. Sorry its on Chrome Windows 7.
Hey - this is the topic you mentioned in comments, correct? :)
Are you able to test it on another browser by chance? Wondering if it's a caching issue with your Chrome.
I downloaded Firefox and tried that, I've just fought 4 different opp's about 12 times altogether, and it worked fine,no problem with saying I was still in a battle. Why the problem with Chrome? that is my preferred browser if possible, could you say how I can stop it happening? thanks for keeping having a look at this, your very kind.
Hi Sorry about such a late reply here - is this still happening with chrome? When it does, are you able to correct it by clearing your cache? I don't think I've seen anyone else report it, and Chrome is pretty popular.
It hasnt happened for a long time now, but thank you for coming back and checking, I will let you know if it happens again. I dont know what fixed it.