[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [conquest] client lockup



On Sun, 18 Dec 2005, Almighty Tallest Cataboligne wrote:


I have a problem where the client freezes, then after
you kill the client and return to the game, the game
says you are already flying another ship. The only way
to fix it is to use Conqoper and "k"ill the player.
This sux because it locks out the player until I get
online to fix them. Shouldn't the server detect that
the player is gone and kill the ship or something?


Normally you can leave a ship vacant in the game and then return to it.

There is an issue that can stop this up.

You get a different slot when you recconnect.
Connect and DONT enter the game.  Then look at the '\' list in conqoper.
You will have a new slot.  When you hit 'e' on your client to enter it
switches
you to the vacant slot.  Sometimes it doesnt want to switch over and just
tells you that you are already flying a ship in the game.  I have gotten
same
ship re-entry when this condition has occured, but I'm not really sure how
I cleared it up.

Yes, you get a temp slot on login. A real slot when entering for battle. This is normal. I have not seen the above mentioned problem before.



Also...you may have multiple set. If you have the multiple flag set for your user it will always give you a new ship up to your multiple limit. I've never tested to see if it allows a re-entry once this limit is set.


Don't mess with multiples... No need :) Theyt do not work properly anyway and should be removed.



-- Jon Trulson mailto:jon@xxxxxxxxxxx ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962 PGP keys at http://radscan.com/~jon/PGPKeys.txt #include <std/disclaimer.h> "I am Nomad." -Nomad