search

Google-Code-Fork / tibiaapi

Automatically exported from code.google.com/p/tibiaapi
MIT License
0 stars 0 forks source link

client.getPlayer() problem #165

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Login.
2. Starts to run around, go upstairs, go downstairs.

What is the expected output? What do you see instead?

Sometimes client.GetPlayer() throws InvalidOperationException.

What version of the product are you using? On what operating system?

I'm using the TibiaAPI release available to download.

Please provide any additional information below.

I'm testing my bot on an OTserver, maybe is it the cause?

Original issue reported on code.google.com by lucas_j_...@hotmail.com on 1 Sep 2009 at 9:39

GoogleCodeExporter commented 9 years ago 
Discovered something else:

When you die, and try to call client.GetPlayer() the problem above happens too.

Original comment by lucas_j_...@hotmail.com on 1 Sep 2009 at 9:46

GoogleCodeExporter commented 9 years ago 
1-The only reason that exception could be thrown is that Status =!
Constants.LoginStatus.LoggedIn which could be caused by either wrong
Addresses.Client.Status or the address in the client's memory doesn't contain 
the
value 8 yet

2-probably, as soon as you die, the connection is closed, so you aren't "logged 
in"
anymore and the exception is thrown

Provide us with the server ip, version and an account for verifying or you could
investigate this based on what I said.

Original comment by geancarl...@gmail.com on 2 Sep 2009 at 4:02

GoogleCodeExporter commented 9 years ago 
The server is: devil-hunter.servegame.com.

I tested here, when you die, the LoggedIn status is still true.

Please, take a look.

Original comment by lucas_j_...@hotmail.com on 3 Sep 2009 at 4:55

GoogleCodeExporter commented 9 years ago 
Seems to be a problem with the OTserver saying you're still logged in even if 
you 
are not. Since TibiaAPI is aimed at the official Tibia server provided by 
Cipsoft 
this issue is obsolete. If you can confirm this issue on the real servers 
please 
feel free to make a new issue explaining this.

Original comment by joebingham07@gmail.com on 10 Nov 2009 at 6:05