Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backward Tibia client compatibility #35

Open
GoogleCodeExporter opened this issue Mar 15, 2015 · 8 comments
Open

Backward Tibia client compatibility #35

GoogleCodeExporter opened this issue Mar 15, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

It would be nice if having Tibia 8.10 (newest) I could use TibiaAPI with
Tibia 8.00 or older as well.

Original issue reported on code.google.com by ghorre on 19 May 2008 at 11:52

@GoogleCodeExporter
Copy link
Author

We actually have Util/Version.cs, which allows you to change all the memory 
addresses
to a specific version. The list, however, is not complete, and the feature has 
not
been extensively tested.

You can test it out, and tell us your results here.

Original comment by ian320 on 21 May 2008 at 5:05

  • Changed state: Accepted
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Might want to consider the possibility of allowing TibiaAPI users to load the 
addresses and constants off files, 
XML I suggest.

Also, some code might work for a certain version of Tibia but not for another, 
so keeping a record of what 
version of Tibia we are dealing with is a good thing. When loading the 
Tibia.exe, checking the file version could 
be a way to determine if that Tibia client is supported.

Original comment by cameri2...@gmail.com on 8 Jun 2008 at 4:15

@GoogleCodeExporter
Copy link
Author

Original comment by ian320 on 13 Mar 2009 at 7:01

  • Changed title: Backward Tibia client compatibility

@GoogleCodeExporter
Copy link
Author

You can always download the source code from a deprecated version of TibiaAPI 
that
was meant for an older version of Tibia.

Original comment by ing.cabr...@gmail.com on 24 Apr 2009 at 11:21

@GoogleCodeExporter
Copy link
Author

[deleted comment]

1 similar comment
@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I may add compatibility for 7.6, 7.92, and any other popular OT version. Also, 
I 
will be adding checks for each supported protocol. (ie. 8.53 added WarIcon to 
the 
TileAddThing packet. Since this doesn't exist in earlier versions a simple if 
statement will decide whether or not to get this byte of information from the 
packet 
buffer.)

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

@GoogleCodeExporter
Copy link
Author

Great idea Joe. One concern I have is that if any item data has changed,
compatibility will be much harder (for instance, if item xxx has an extra byte 
in
7.6, but not in 8.5, or vv)

Original comment by ian320 on 10 Nov 2009 at 2:39

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant