OTClient OTClient Redemption unresponsive upon trying to enter game server

[Kaeyon]

Hey all, so I've been working with Canary, MyAAC, and Mehah's OtClient all using protocol 1340. I've followed the instructions at OpenTibiaBR 100% completely (twice actually) in getting the database, server, and myaac set up in Docker.

All of that is golden. Everything loads fine with no errors. The MyAAC page loads perfectly, admin panel, etc. Everything.

I've successfully compiled Mehah's OTClient no problem. I loaded the assets from a 1340 client into data/things as instructed. I am receiving absolutely no errors from the client side as shown below:

I can log in with the @GOD account and characters populate no problem. However, my issue begins when I click "OK" to log in. The entire client becomes immediately unresponsive. No crashes, no error logs. I can't "Cancel" the connection or even click "X" to close the client. The background is frozen as well. Completely frozen and the only way I can close the client is go into the Task Manager to do so.



There are no activity logs within the docker server container. Only from the myaac container showing the successful account login.


I've tried changing IPs around the different config files from localhost to my internal IP, to my external IP, to everything in between and I just can't seem to get this final step fixed.

Are there any other recommendations that I can try?

Really appreciate the help in advance!

 

[Error 502]

1) Are you using the main repo of OTC?
2) are you 100% sure that you are using canary in 13.40? (currently main repo canary is 14.12)
3) did you make any modifications OTC/canary?
4) can you enter the server with cipsoft 13.40 client?

My theory is that you are trying to use canary main repo 14.12, in that version they changed the header protocol (or you forced it by setting "13.40" in definition.hpp)

Info	Canary	OTC
13.40	Release Canary - Version 3.2.0 · opentibiabr/canary (https://github.com/opentibiabr/canary/releases/tag/v3.2.0)	Main repo OTC
14.05	Release Canary - Version 3.2.1 · opentibiabr/canary (https://github.com/opentibiabr/canary/releases/tag/v3.2.1)	feat: version 14 by murilo09 · Pull Request #1173 · mehah/otclient (https://github.com/mehah/otclient/pull/1173)
14.12	Main repo Canary	feat: version 14 by murilo09 · Pull Request #1173 · mehah/otclient (https://github.com/mehah/otclient/pull/1173)

 

[Kaeyon]

1) Are you using the main repo of OTC?
2) are you 100% sure that you are using canary in 13.40? (currently main repo canary is 14.12)
3) did you make any modifications OTC/canary?
4) can you enter the server with cipsoft 13.40 client?

My theory is that you are trying to use canary main repo 14.12, in that version they changed the header protocol (or you forced it by setting "13.40" in definition.hpp)

Info	Canary	OTC
13.40	Release Canary - Version 3.2.0 · opentibiabr/canary (https://github.com/opentibiabr/canary/releases/tag/v3.2.0)	Main repo OTC
14.05	Release Canary - Version 3.2.1 · opentibiabr/canary (https://github.com/opentibiabr/canary/releases/tag/v3.2.1)	feat: version 14 by murilo09 · Pull Request #1173 · mehah/otclient (https://github.com/mehah/otclient/pull/1173)
14.12	Main repo Canary	feat: version 14 by murilo09 · Pull Request #1173 · mehah/otclient (https://github.com/mehah/otclient/pull/1173)

Thanks for the response. But yeah I just pulled the latest repo for both Canary and otclient. I would personally like to use client 14 just for a few more features, etc. However, the only reason I chose 1340 was because I was getting the following error previously. I just redownloaded a version 14 client and threw them into the assets and changed my protocols around and I'm still receiving this stating client version 14 is not supported

I've made no modifications to client or server. These are both 100% freshly compiled from both main branches

EDIT - I see where you showcased 13.40 as the main repo for OTC. That's most likely where the issue lies then. I didn't realize this as I just assumed it was updated with the latest repo. So I'm guess I can just perform a pull request and recompile this down?