Celtic Heroes

Admin please lock this thread.

Admin please lock this thread.

why?

Admin please lock this thread.

why?

If people read before posting, there wouldn't be nearly the urge to rage lock there is.


What fixes one type of persistent logging problem after the char select screen is:
1) force close CH
2) turn off wifi (or cellular data whichever is the issue)
3) start CH and log, get the no connection warning
4) enable wifi (or cellular)
5) try to log again.

As of the update just last week it appears as you can get stuck on loading the game initially without a connection. Do the same as above but force close ch a second time between step 3 and 4. Open ch at step 5 and login.

These fixes and work arounds shouldn't even be necessary how is it with more updates comes more serious bugs.

Another thing I've noticed is that ss glitch in tower is still a thing,

Admin please lock this thread.

why?

If people read before posting, there wouldn't be nearly the urge to rage lock there is.


What fixes one type of persistent logging problem after the char select screen is:
1) force close CH
2) turn off wifi (or cellular data whichever is the issue)
3) start CH and log, get the no connection warning
4) enable wifi (or cellular)
5) try to log again.

As of the update just last week it appears as you can get stuck on loading the game initially without a connection. Do the same as above but force close ch a second time between step 3 and 4. Open ch at step 5 and login.

What Plus3 is saying has absolutely nothing to do with the OP. He is talking about a different connection issue.

Happened again in Morrigan less than an hour ago when Mordris spawned, Nobody could connect and no matter what workarounds Plus3 keeps insisting will fix it, it doesn't because the login server has issues.

Usually this is what we get:
and then Morrigan is so congested and not responding , the world login server can't even connect to it and thinks it's down.
No amount of wifi or app restart will fix that.

Admin please lock this thread.

But then plus3 would have 1 less thread to post about all his devices he has and his spare time is spent leveling up 1 trillion characters

why?

If people read before posting, there wouldn't be nearly the urge to rage lock there is.


What fixes one type of persistent logging problem after the char select screen is:
1) force close CH
2) turn off wifi (or cellular data whichever is the issue)
3) start CH and log, get the no connection warning
4) enable wifi (or cellular)
5) try to log again.

As of the update just last week it appears as you can get stuck on loading the game initially without a connection. Do the same as above but force close ch a second time between step 3 and 4. Open ch at step 5 and login.

What Plus3 is saying has absolutely nothing to do with the OP. He is talking about a different connection issue.

Happened again in Morrigan less than an hour ago when Mordris spawned, Nobody could connect and no matter what workarounds Plus3 keeps insisting will fix it, it doesn't because the login server has issues.

Usually this is what we get:

and then Morrigan is so congested and not responding , the world login server can't even connect to it and thinks it's down.

No amount of wifi or app restart will fix that.

That's exactly what I see when I get the problem. A list of the worlds where at least Taranis (not morrigan obviously) is offline even though it's obviously not.

The procedure above fixes it on all of my devices and iOS builds. Simply restarting the app does not fix it, exactly like I have said. Nor does simply turning off then on wifi as it is a bug in ch handshaking properly, not your wifi connection. It seems the login server, from testing, handles about 1 login per second and has a working stack of about 8-10 devices. You can repeatedly and reliably get this error, or an error with identical symptoms, by just simeltaneously logging 12+ devices.

In case you don't bother reading anything but this last run on sentence, in not saying best login server ever, nor is the code needing the above workaround a jewel to be immortalized in a coding history museum, but it is likely to help people having the same issue as me.

Lol I'd like to hear OTMs explanation as to why turning off your wifi or data will enable you to connect as soon as you're on the login page after you fail the first time. It absolutely makes no sense, and we have tried all sorts of voodoo hocus pocus magic trick workarounds, when not one from our clan can login for several minutes, up to 70m at one time two weeks ago, I'm pretty sure the problem is on the server side.

Also the fact that we can get in eventually without doing all those tricks means they don't really do anything until some process on the server resets or recycles due to a timeout.

It's a pretty piss poor server if users are forced to do all that just to login. It's like saying if your car won't start, just exit the car, shut the doors, remove the battery go back to your house, wait a couple minutes, then go back to your car, put the battery it in , then try again. If it still fails to start, then blame your keys, not the car.

Lol I'd like to hear OTMs explanation as to why turning off your wifi or data will enable you to connect as soon as you're on the login page after you fail the first time. It absolutely makes no sense, and we have tried all sorts of voodoo hocus pocus magic trick workarounds, when not one from our clan can login for several minutes, up to 70m at one time two weeks ago, I'm pretty sure the problem is on the server side.

Also the fact that we can get in eventually without doing all those tricks means they don't really do anything until some process on the server resets or recycles due to a timeout.

It's a pretty piss poor server if users are forced to do all that just to login. It's like saying if your car won't start, just exit the car, shut the doors, remove the battery go back to your house, wait a couple minutes, then go back to your car, put the battery it in , then try again. If it still fails to start, then blame your keys, not the car.

Yes the login server blows. lol I was trying to be civil to OTM.


My guess as to why it works is when you try to log with no connection it "forgets" or resets the error in handshaking so when you re-enable it and log again you can log successfully. The more people try to log the worse it gets, once your device is affected it will not log even if the login load subsides in my experience.

If you read anything you would realize the final step was never to turn of wifi and then log lmafo.

We never had this issue before, it all started during all that "server maintenance" resets during the week before the Dec 19 winter update.

Some network genius decided to change server settings, most likely listener instances or timeout configuration thinking it would be a good change. Obviously it's a failure and OTM should contact them and tell them to revert it back to the way it was. Or perhaps with all these "firmware upgrades" they did, some defaults changed that they're unaware of. But as long as OTM doesn't acknowledge it's an issue and doesn't take any action to investigate what the problem is, nothing is going to fix this unless half the server population stops playing, reducing congestion.