Open GoogleCodeExporter opened 9 years ago
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
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
Original comment by ian320
on 13 Mar 2009 at 7:01
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
[deleted comment]
[deleted comment]
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
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
Original issue reported on code.google.com by
ghorre
on 19 May 2008 at 11:52