[OTClient] Future of OTClient

Hello,

After reading the last hot discussions on this forum about otclient some thoughts on the community openness direction and do not use buy otc I decided to open this thread to move on edubart otclient.

Can we join efforts of the community to contribute again with otclient?
I mean, maybe make a thread showing the challenges of improvements that need to be done on otclient - you know, I know that what moves we developers are the challenges - so this way we can list/update the issues and milestones (that probably changes in 3-4 years).
I am saying it because when we open the otclient repo we see a lot of issues not well documented, most of them are players that cannot setup the client and others saying about the FPS issues, the ones closed by @Iryont with no description why or if it is invalid, solved etc (it is not a criticizing you Iryont but just making a note about the closed issues that have been pointed on other thread).

It seems that it there is a lot of discussions but not a decision about what way to follow. Maybe we can get back this discussions and make some changes. It will move the wheel back again. It is a spark!

If you that are reading this solved any problem on the client and did not share it (because you do not want or even because you do not think that people would care about it in apparently abandoned project), you can just show some approaches or any contribution in a other way that not sharing your solution code. Think about it, people still uses OTClient, users find bugs and sometimes comment there... you still have the privilege to get this feedback, but when it will be gone you won't have it anymore.

Most people do not have more time to put hands on code, but can always something about a dicussion or give an advice or things like that.


Hope you understand my point of view and lets change it!

this repo need a road map, more docs... more info i think.. rules!

People are working in a client made in Unity, soon every OT will move to Unity

This sounds tasty, an OT Client made in Unity? Sign me up. I've preferred using the regular Tibia clients in my experiences as OT Client has been too convoluted, and complicated to set-up properly. Some of the bugs I've seen mentioned also turned me off as they seemed to impact gameplay (something with stacked targeting comes to mind). GoGo Unity-OT-Client

xNMExReject said:

This sounds tasty, an OT Client made in Unity?

Click to expand...

you are kinda out of luck since the project creator passed away

The Otclient's future is here:

Follow the repository: mehah/otclient (https://github.com/mehah/otclient)

if u reading and if u can, suport him...

I think perhaps in my original "do not buy/use otcv8" I sent the wrong message and I want to retificate myself:

It's not that I don't like Kondrah, or v8. Otcv8 is a pretty decent mimic of Tibia client and it can even be better in some aspects despite still lacking a few adjustments. It has good improvements in comparison to edubart original version and also compared to mehah.

For probably 98% of server owners, they don't really need the source code to anything as they won't try and change anything besides modules.


The thing is: progress is not made by users, progress is mostly made by developers. By not sharing the source, you're creating a bottleneck (and assuming the responsability) of restricting the progress.
In the ideal world, those people that fixes OTC should share they progress. New people that get into the repo or start into OTC would also develop/review/test/approve those changes and contribute.
This is the so called deployment cycle, and every aspect of it is as important as the other ones.

What we currently have today is a small group developing, other small groups (vast majority of them single person) working on other areas on top of Mehah/edubart source or even on modules and not sharing. This is extremely stupid and a waste of everyone's time.
Not only developer's time, but reviewers, testers, approvers because they will do this for each similar change across different projects (even privately forked versions).

The problem is the fact that people improve things that are commonly used by everyone in ways that sometimes aren't the best. Having feedbacks, others contributing is the only way to go ever beyond. Rotation is also key, as sometimes you'll focus on a part while others will focus in another. This keeps the progress fresh and removes the pressure of being the only maintainer.

Imagine Mehah didn't had to do several things that kondrah already did? he probably could have used this time to improve other areas and have a better project to everyone. This is the message I was trying to share.