Answer to Bug #132

Death · (#1 (**permalink**))

OK, this is the answer to bug #132.

A) Group invites can crash you if you do not see the player who is inviting you

B) Certain Quest Givers who are assigned to a faction that does not exist are near you, so you crash.

Problem A can be solved easily, but Problem B is a lot harder. It requires a teleport, or .start, which is damn near impossible.

Vix · (#2 (**permalink**))

I'm still a little confused, so you mean you have to teleport everyone?

beserkfreak · (#3 (**permalink**))

I got the 132 error from using .start. My warrior fell through the ground and I used that command. After using it im not able to leave the starting area

Death · (#4 (**permalink**))

Quote:

Originally Posted by Vix

I'm still a little confused, so you mean you have to teleport everyone?

Basically, yes.

When you login, you don't usually have enough time to type .start to travel away, and it crashes you.

Quote:

Originally Posted by beserkfreak

I got the 132 error from using .start. My warrior fell through the ground and I used that command. After using it im not able to leave the starting area

That's odd, if anyone has this error, PM me your character name with it. (No other kinds of PMs, please)

beserkfreak · (#5 (**permalink**))

Dont worry about it Death. I will just wait until there is a fix. I deleted my character to see if that was the problem and decided to redo another warrior. The strange thing is, I cannot leave the starting area with the warrior class. But if I play as any other class I can leave.