• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

OTClient 1.0 (Release)

Hello, Im goint to start working with OTClient from mehah, and i can see some examples for map and outfit shaders, but not for items. Is it possible with thue current status or more source changes are needed?
 
nemk said:
is your otcleint compatibile with 12.64 tibia engine please help
Click to expand...
I have TFS 1.4 for tibia client 10.98 with custom sprites from 12+ and I use this OTclient. But with OTServ BR and OTG premium I guess this release not working.
 
pink_panther said:
Work properly on 7.x?

Really wish there was just 1 distribution for Otclient.

otv8 can suck my fart hole.
Click to expand...

I've been using it on 8.6, and some tips I can throw to make it work well is to disable action bars, and set FPS limit to 50 since it takes 50ms to go to another tile on old protocols. You can add nice customizations, and I think this client can work well with any version by adjusting some files.
 
After some drama in the repo's issues I've gotta be honest and say that I highly and wholeheartedly recommend against using otclient1.0 or even supporting otclient1.0 financially, partially because of poor design choices, partially because of the owner himself.

Mehah invited me to try it out by linking it to me in my thread a long time ago, it was riddled with bugs including (D)DoSing vanilla TFS 1.3 (with over 100pps packet flood) just from stepping diagonally once at the time, and instead of wanting to fix this issue he blamed TFS for not having proper diagonal step rules, I don't know if he actually fixed this issue later or not, but it sounded like he wasn't interested in ever fixing this issue (and is a design flaw of his as he has hardcoded rules into the client instead of the client being lenient and adaptive like the original otclient).

This is a pattern I've seen again and again, he overestimates his own capacity and blames everything/everyone else if he doesn't know how to fix it (or even sometimes doesn't understand the issue, but pretends he does and even pretends it's already fixed when it isn't, he also asked for money in a git issue to fix certain issues).

I didn't want to say anything negative earlier because I don't like to judge prematurely, and I don't like being negative unnecessarily, but I've gotta be honest and say that otclient1.0 is a very unstable version of otclient, mainly (if not only) targeting the newest prototocol which mehah admitted himself in a github issue, it doesn't really seek to have compatibility with older versions, and I think it's riddled with poor design issues which results in serious long-term bugs/stability issues for anyone using this client.

I honestly recommend OpenTibiaUnity over this one even though OTU was always in beta or whatever, because at least it has some interesting features such as being web and android compliant, and I've experienced less bugs with OTU than I have with otclient1.0.

Just my 5 cents, good luck.
 
Last edited:
Source said:
After some drama in the repo's issues I've gotta be honest and say that I highly and wholeheartedly recommend against using otclient1.0 or even supporting otclient1.0 financially, partially because of poor design choices, partially because of the owner himself.

Mehah invited me to try it out by linking it to me in my thread a long time ago, it was riddled with bugs including (D)DoSing vanilla TFS 1.3 (with over 100pps packet flood) just from stepping diagonally once at the time, and instead of wanting to fix this issue he blamed TFS for not having proper diagonal step rules, I don't know if he actually fixed this issue later or not, but it sounded like he wasn't interested in ever fixing this issue (and is a design flaw of his as he has hardcoded rules into the client instead of the client being lenient and adaptive like the original otclient).

This is a pattern I've seen again and again, he overestimates his own capacity and blames everything/everyone else if he doesn't know how to fix it (or even sometimes doesn't understand the issue, but pretends he does and even pretends it's already fixed when it isn't, he also asked for money in a git issue to fix certain issues).

I didn't want to say anything negative earlier because I don't like to judge prematurely, and I don't like being negative unnecessarily, but I've gotta be honest and say that otclient1.0 is a very unstable version of otclient, mainly (if not only) targeting the newest prototocol which mehah admitted himself in a github issue, it doesn't really seek to have compatibility with older versions, and I think it's riddled with poor design issues which results in serious long-term bugs/stability issues for anyone using this client.

I honestly recommend OpenTibiaUnity over this one even though OTU was always in beta or whatever, because at least it has some interesting features such as being web and android compliant, and I've experienced less bugs with OTU than I have with otclient1.0.

Just my 5 cents, good luck.
Click to expand...

wtf, you're a crybaby, I'm not in the project just to correct, I'm refactoring, but anyway, I won't waste my time with crybaby.
 
guys, let's keep this thread clean the purpose is to share the release of OTC 1.0. That discussion on github was simply unfortunate.
The beautiful thing about OTC 1.0 is that it is totally free. Mehah has been working on this over a year now and as a open source it brings a lot of opportunities for everyone in the community to study its code and contribute or simply learn how Mehah worked on it. Nobody has been asked to donate or pay anything, nor they should, but of course donations and an active and helpful community help to keep contributors engaged.
At the same time, Mehah has no obligation to keep working on this forever nor to do anything (especially custom things for specific distros people want to use with his version of the client)

Perhaps the confusion all started when @Source didn't understood what Mehah was saying, you see, Mehah doesn't speak a good english and he rely on google translate most of the time so that's why his sentences are short and sometimes with multiple interpretations. He said, including in the github and the threads he posted here that the logic of diagonal moving was not standard and he would try to understand why this was causing conflicts with OTC but he would advise for you to try and move to a standard solution that would work better (and it would also be faster for both). He said if this was not an easy task, he could do as a freelance to try and fix it especifically for your case probably involving fixes on both ends (server and client).

Now, I think this is a huge opportunity for us to try and understand how badly designed our sources are, because @Source is saying the client is the problem but in my personal opinion the source itself should be able to better handle multiple requests without having to kick the player for packet flooding. Why it simply doesnt cap the requests and limit the read for this particular player?

Moving back to @Source comments, perhaps he has a bad understanding that the project is a final product. It not only isn't but it also SHOULDN'T.
It's been developed, revamped, rewritten and optimized. Those things take time and builds can break, and that is completely fine!
We are not doing anything here for work, we don't have environments and production and pre-production environments, it's the job of the person running a server to actually worry about this, not the devs!

At the end, he realized that for his custom purpose the otc1.0 wasn't the best fit, even though he said in the github that he fixed the error in less than 30 minutes and wouldn't share the solution...

If you want to revive OTUnity and use it, go ahead. If you want to stick to otc1.0, go ahead! If you want to create your own version and call it OTC 15.2, go ahead! It's an open source community, and that is the beauty of it
 
Sorry for interrupting guys, but I think a big thing just dropped into mehah otc pull requests (for people interested though).

github.com

Protobuf support by nekiro · Pull Request #213 · mehah/otclient

This is protobuf support for newest protocols. Drop your content of assets directory just like you would do with normal .dat/.spr files and watch the magic happen. Additionally to it being able to ...
github.com github.com
 
Nekiro said:
Sorry for interrupting guys, but I think a big thing just dropped into mehah otc pull requests (for people interested though).

github.com

Protobuf support by nekiro · Pull Request #213 · mehah/otclient

This is protobuf support for newest protocols. Drop your content of assets directory just like you would do with normal .dat/.spr files and watch the magic happen. Additionally to it being able to ...
github.com github.com
Click to expand...
What does this mean to people who aren't advanced developers?
 
Happy Feliz GIF


OTClient with protocol 12 native assets support!
With this PR, mehah/otclient can be fully used with TFS 1.5 protocol 12 master branch! :D
 

Similar threads

Adorius Black
OTClient Mehah 3.0.2 - StoneDrake UI
Replies
13
Views
2K
Error 502
Error 502
Brunds
[OTC Mehah] Fix problems in increasing the map view
Replies
5
Views
2K
Sanjao
Sanjao
Back
Top