jo3bingham / tibiaapi Goto Github PK

I've just started checking out this API, so I'm not too sure on how to proceed with this error.
I ran the 'Record' app, then started the client (loginWebService modified to http://127.0.0.1:7171/).
I get my character list without issues, however when I try to connect to the game world with a character the following error pops up in the console:

ERROR System.Exception: [Connection.BeginReceiveClientCallback] RSA decryption failed.
   at OXGaming.TibiaAPI.Network.Connection.BeginReceiveClientCallback(IAsyncResult ar) in /home/dev/Documents/TibiaAPI/TibiaAPI/Network/Connection.cs:line 804
ERROR Data: 9D 00 00 00 00 00 0A 07 00 E7 04 E7 04 00 00 0B 00 31 32 2E 35 35 2E 31 30 34 35 34 DA 67 01 13 40 1E E1 B8 5F EB 1F DF 26 2B E2 B7 14 A6 7C EA 0E CA E7 2F B0 75 91 83 EA 26 C2 E0 07 F4 F5 19 DA 17 80 A7 2A 2D 4C 75 45 95 91 EB 3D EC 6E 11 76 EE 20 46 D8 44 32 CF D8 78 53 BC D4 1C FC FA AD FD DB 53 C5 7F 08 1F F1 B8 1C DA 0D 15 19 8E C3 A0 D9 5D 9C 0D E5 26 D9 71 BB CF 33 D4 01 B1 89 88 ED BA 8D E2 E3 50 35 CF 92 50 FD A5 35 18 A2 4D 1D C1 3C B3 D0 1F 2D 4B F7 EB E2 43 A8

I'm logging in to official Tibia servers using the official and latest client. Perhaps something changed in the latest version regarding the encryption of packets? RSA key changed?
Thank you beforehand.

I've created a json file following documentation since the target hasn't.

so, debugging the code i reached out that even my package.json is not empty, it returns false. follow image to help bellow.

print screen

Currently, the Extract app has the ability to export creatures, but the format is a custom one: CreatureName Position

There should be a new export parameter (--spawns?) that exports creatures in the spawns XML format used by RME and Open-Tibia servers.

[Edited]
In version 1240.100.30 we have 13 new bytes before RSA Key.

We need a version check to change the buffer position from 18 to 31 in Connection.cs
(already check it, and it's working)

After a new client update i getting RSA Decryption Failed using Public OTServ RSA
with error data:

9D 00 00 00 00 00 0A 05 00 D8 04 D8 04 00 00 0B 00 31 6C 6A FA 79 FA 39 E9 B9 6E 7F D4 B0 08 E7 73 CB D9 F4 28 07 65 00 0A B2 94 CF 7E 71 92 CF 81 4D C7 D5 DC 45 F6 E9 02 C0 1F 1E E1 3F 3C 94 AF 29 5B 84 04 4C 91 90 50 A8 61 D4 DE C6 5B B4 5F D7 1B 2F 7C 8C B4 C0 33 3F 28 CC E4 81 85 E3 7D 65 1B 74 3F E8 64 63 D6 80 32 7F C5 A4 01 7E 77 99 98 B4 9E 45 AE 42 B2 2C 84 8E B7 AD 14 02 86 82 21 69 A6 F7 4C 61 1E AC C6 1B B5 D7 6B 50 3D 20 05 37 C3 0D 60 54 3D 42 C1 E6 7B 9A 2F

If I'm trying to use a client version that doesn't have the package.json file, is there any way I can register it so I can record a session?

The Record and Extract apps allow the user to specify a Tibia directory for loading assets (.dat). This is useful when connecting to Open-Tibia servers and when extracting from recordings of client versions older than the most recent (the ClientData directory is an example of how this can be used). Currently, the Extract app will attempt to find the target client version in the ClientData directory even if a Tibia directory was specified by the user, and logs a confusing message. The fix should be to ignore the ClientData directory if a Tibia directory is specified by the user.

The Extract app will load ItemsIgnore.xml and ItemsReplace.xml when the --map parameter is used, and will fail if they don't exist. The app should ignore this failure and continue extracting the map.

Hello,

I'm new to all the new Open Tibia stuff, because I'm returning after years of absence. Please forgive me if this is a silly question to ask, but since it's hard to find good information on the topic, I'll try.

Because of BattlEye, Windows support is limited to official servers not protected by BattlEye (Zuna and Zunera).

What is the reason of incompatibility with BattlEye? Is this just because BattlEye would detect modifications of the client, or maybe it additionally encrypts traffic sent by Tibia client?

The Extract app assumes that the user has an items.otb where the server IDs match the official client IDs, but this is not always the case. By default, servers based on TFS have different server/client IDs. The Extract app needs to be able to load an items.otb file, if specified by the user, and use those IDs instead.