My OTC project

[Itutorial]

I am going to work on OTC. Anyone that can help me by listing known client bugs, and missing features, ect. would be great. I am not working on UI or anything similar to that. Strictly improvements on how the client works (player side) and code that causes bad performance or bugs in the client. Once some progress has been made on fixing the already existing structure I will work on more user-friendly methods of adding systems to the client and modifying the UI, ect.

 

[nugo]

Work with @Mehah on this

GitHub - mehah/otclient: An alternative tibia client for otserv written in C++20 and Lua, made with a modular system that uses lua scripts for ingame interface and functionality, making otclient flexible and easy to customize

An alternative tibia client for otserv written in C++20 and Lua, made with a modular system that uses lua scripts for ingame interface and functionality, making otclient flexible and easy to custom...

github.com

OTClient 1.0

Hey guys, Well, I always wanted to help the community, but I had to choose, life and personal projects or the community, I ended up choosing my life, but things changed with the arrival of COVID and now I have time, so I will be making some corrections and improvements in customer performance...

otland.net

 

[Avandia]

Do it with @Mehah, Create goals maybe someone donate for something.

 

[Itutorial]

I will look at it. I mainly wanted to create my own so I can keep everything clean and know what needs to be done and has been done.

 

[Sopago]

Has anyone used Mehahs OTC? how is it compared to kondrahs? From his thread i can see he made some nice progress, i guess its better to join forces and work on something together right?

 

[Silba]

I will look at it. I mainly wanted to create my own so I can keep everything clean and know what needs to be done and has been done.

The last thing we need is 100 different versions of otc, however i can only applaud your efforts regardless, we all need a proper working otc. good luck with it

 

[Peonso]

I think going through both Moving towards OTC (https://otland.net/threads/moving-towards-otc.238754/) and OTClient Graphics Discussion (Anyone out there more knowledgeable than me?) (https://otland.net/threads/otclient-graphics-discussion-anyone-out-there-more-knowledgeable-than-me.244015/) are a must to such endeavor. Also trying to comprehend what otclientv8 actually improved.

The way I see things moving OTC to protocol 12.60 is a must, so TFS is free to do the same. With that I don't mean supporting every missing feature from 10.98 to 12.60, just that it can bug free connect to a 12.60 server. Leave the custom stuff/features to the users, but by moving protocol foward we ensure the community stay united working on the same repositories, instead of spliting into tons of projects. Also I would advocate over commiting stuff to the main OTC branch.

 

[Itutorial]

Connecting to 12.60 would be low on the list of priorities. No need to bring a bunch of new bugs because we are rushing. Fixing the current bugs is the goal.

Does anyone know if meh is still active? I need to have access to modifying the project and adding the new code. I don't want to be limited to waiting on someone to get a fix put in. That's the main problem.

 

[Nekiro]

Connecting to 12.60 would be low on the list of priorities. No need to bring a bunch of new bugs because we are rushing. Fixing the current bugs is the goal.

Does anyone know if meh is still active? I need to have access to modifying the project and adding the new code. I don't want to be limited to waiting on someone to get a fix put in. That's the main problem.

This is exactly why people invented pull requests in github, to avoid pushing non tested bad code.

 

[Peonso]

Connecting to 12.60 would be low on the list of priorities. No need to bring a bunch of new bugs because we are rushing. Fixing the current bugs is the goal.

12.60 packet received, send a terminal message and do nothing else. I don't see many bugs happening.