Reason of incompatibility with BattlEye

[TibiaBaker]

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?

[jo3bingham]

On Windows, BattlEye performs checks on the client executable as it is being started to ensure no modifications have been made to the process memory. Since the loginWebService address and the RSA key have to be modified in order to work with the API, BattlEye would then block the client from loading. However, if you were able to bypass this restriction then you could use the API with any world on Windows. But I see that as wasted effort because you can spin up a Linux VM for free where BattlEye is less invasive, and you're able to use the API with any world.

[TibiaBaker]

So BattlEye doesn't perform VM checks on Linux?

[jo3bingham]

So BattlEye doesn't perform VM checks on Linux?

Nope.

[TibiaBaker]

That is a botter's paradise, then. While your project is obviously not about that, it could be used to make a new BlackD Proxy, I suppose.

[jo3bingham]

That is a botter's paradise, then. While your project is obviously not about that, it could be used to make a new BlackD Proxy, I suppose.

Yeah, it could definitely be used to make a proxy bot akin to BlackD Proxy. I actually made a proof-of-concept bot with it, but it was very limited (heal/mana (self/friends), attack, refill, equip, and some other minor functionality) because I have no desire to make a full-fledged bot.

Closing this issue now since your question has been answered.