Runes of Magic US / AU

This has to be the longest running bug in-game that hasn't been fixed because we all just put up with it.

Seriously, there is no way that logging back outside is on purpose.

Unless of course, RW HQ is full of griefers: "What can we do to make playing the game more unpleasant?"

I've noticed that there seems to be a time-limit involved here - if you can log back in quickly enough, you can sometimes land inside the instance.

Something else I've noticed that seems to incrase the chance of loggin back inside the instance, is your channel selection. If you were playing on channel 3, try loggin back in on channel 3 - even though there's no channels inside the instances. I have noticed that this seems to increase my chance at logging in inside the instance. Again, speed also seems to be a factor.

None of that is guaranteed to work, but is just a couple of observations in my almost-8-years of playing RoM.

And the fix is probably to change somewhere in the code wrong "if (numPlayersInInstance >= 12)" to correct "if (numPlayersInInstance > 12)"...

If RW can't find this condition I can send my 10 years old nephew for a couple of hours to help them find this spot in the code

Maybe it would just be easier to fix the constant crashes that happen in the instances. But we know that will never happen.

Can we get clarification on this?

Is it a bug? Is it intended? And if it is intended... WHY??? Specially with the bad d/c's and game crashes this game has.


After a bit of brainstorming I believe I found what could be the issue.

Full instance (12/12). If someone logged off/crashed/whatever and someone else came in to fill that 12th spot, then the d/c person re-logged then that would be the issue? My belief is, this logging back outside is a really lazy way to tackle the above scenario.

Anyways... clarification please. Crashing because the game's coding is garbage and having to run back is a pain... *remembers Hall of Earth* *shivers*

Quoted from "Magío"

Full instance (12/12). If someone logged off/crashed/whatever and someone else came in to fill that 12th spot, then the d/c person re-logged then that would be the issue?

Yes, this was our theory above.

Quoted from "Magío"

My belief is, this logging back outside is a really lazy way to tackle the above scenario.

I don't agree, it is a perfectly valid choice of how to handle this situation.

It's just that without seeing the code you can almost certainly guess what the bug is. Instead of correct(which for HM would keep you in the instance if you are the 10th, 11th, 12th, but kick you out if you are the 13th, 14th etc.) they have almost certainly something likewhich behaves the same if you are 10th, 11th (keep) or 13th, 15th (kick out), but ... wrongly kicks you out to resp if you are the 12th (which is a legit. situation and you should be allowed to log in in the instance just as you are allowed when you are the 11th member of the pt inside the instance).

Just one character difference (">" vs ">=") but so annoying result.

Quoted from "Inferiority"

if you can log back in quickly enough, you can sometimes land inside the instance

Yep, this observation makes it a tad more complex. Still: kicking out "over load" ppl to resp upon logging in is such a well defined piece of logic that it has to take just a couple of minutes to find the code responsible for it. And - almost certainly the bug is just a typo ">" vs ">=" (or "<=" vs "<").

Quoted from "Magío"

Crashing [...] and having to run back is a pain...

Could not agree more.

Yep, we lost hope: you cannot fix the fact that the game crashes. Fine. Could you please, please, please at least make a tiny effort to make crashing less annoying? Esp. in this kind of situation which is so well defined and the fix almost has to be super simple...