Forums » Bugs
Training sector glitch
If you start an Itani character and complete Training I, Training II.
Then begin Training III... but abort it.
Begin the optional Orun Collector killing mission (then kill four Orun Collectors) it will not let you back onto the station, though it will let you onto the capship floating nearby.
There is a solution to this: ram yourself into an asteroid and die. Then you will spawn at the station orbiting Itan. However this solution is not obvious to a new player. One such player gave up tonight because of this glitch.
I have reproduced this two times.
Then begin Training III... but abort it.
Begin the optional Orun Collector killing mission (then kill four Orun Collectors) it will not let you back onto the station, though it will let you onto the capship floating nearby.
There is a solution to this: ram yourself into an asteroid and die. Then you will spawn at the station orbiting Itan. However this solution is not obvious to a new player. One such player gave up tonight because of this glitch.
I have reproduced this two times.
P.S. You can complete the bot killing missions just fine if you never abort Training III...
I don't know if there are other ways to trigger this?
I don't know if there are other ways to trigger this?
The thing is, once you start Training III it locks you out of the station so newbs don't get confused. Aborting it should unlock the station, but it doesn't.
Still happening, still affecting honest newbs.
IN ADDITION:
Newbs in every training sector are now invulnerable!
They cannot kill themselves when this glitch happens! Either through /explode or by ramming an asteroid! That means their characters cannot do anything ever.
Firemage restarted the sector, but no dice.
Newbs in every training sector are now invulnerable!
They cannot kill themselves when this glitch happens! Either through /explode or by ramming an asteroid! That means their characters cannot do anything ever.
Firemage restarted the sector, but no dice.
Thanks. We're looking into it and will have a fix as soon as possible.
hm, suggesting a "solution" was a bit presumptuous of me
This should be fixed now, for new characters. For existing characters with the problem, we're going to check the database and fix people directly.