BattleMaster Community

BattleMaster => Helpline => Topic started by: roland.walters@abbott.com on September 24, 2012, 06:44:29 PM

Title: Released to Limbo
Post by: roland.walters@abbott.com on September 24, 2012, 06:44:29 PM
My adventurer character has had a very bad experience.  His realm was destroyed and before he could adopt a new country, he was arrested.  Ok, getting arrested is no big deal.  Happens all the time.  But when he paid his fine, he was released to no where, literally.  When I try to do anything that needs a location to function, like travel, I get a message saying "not possible from this location".  Is there any way to get out of this limbo or is the character screwed?

Roland
Title: Re: Released to Limbo
Post by: Anaris on September 24, 2012, 06:45:39 PM
I believe there's a general issue with rogue characters who were released from prison.

Does this sound like your issue? http://bugs.battlemaster.org/view.php?id=7364
Title: Re: Released to Limbo
Post by: Vellos on September 24, 2012, 08:13:52 PM
My adventurer character has had a very bad experience.  His realm was destroyed and before he could adopt a new country, he was arrested.  Ok, getting arrested is no big deal.  Happens all the time.  But when he paid his fine, he was released to no where, literally.  When I try to do anything that needs a location to function, like travel, I get a message saying "not possible from this location".  Is there any way to get out of this limbo or is the character screwed?

Roland

Now I want to try this.
Title: Re: Released to Limbo
Post by: roland.walters@abbott.com on September 24, 2012, 08:23:25 PM
The bug report describes the situation that Damian, my adventurer character in Dwilight, is in.  Since a bug report has been filed, I won't duplicate if with another one.

Roland
Title: Re: Released to Limbo
Post by: Tom on September 24, 2012, 08:30:47 PM
Theoretically, you should be given the option to "start a new life", including teleport to the realm you choose. But apparently that is broken right now. We're working on it. The more details you can add to the bug report linked above, the easier it is for us to find and fix the issue.