it's because you didn't see the discussion in a issue of the repository of him calling everyone a monkey.
I never called you or anyone else there anything until a random BR appeared days later and called me a "random nobody clown animal/monkey that should go back in his cage" who was mindlessly trying to defend your behavior without any arguments or observations and just blindly taking sides.
Since all he was doing was hurl insults and spam thumb down emotes everywhere, yeah I hurled some insults back.
You can find his comment
here showing clearly who started with the insults.
And yeah I had been rude to you before that (in the last git issue only), because you were being rude, dismissive, lying to my face which wasted my time and broke my patience, but I hadn't called you anything, and in fact have still not called you anything except for a liar, which you are.
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.
That's not quite true, he said he would
not fix light issues for free in the git issue I made.
I didn't actually mind and had already prepared to donate $50 to him for a fix, but if you look carefully mehah didn't seem to even understand the issue even though he hardheadedly thought he did, and was even convinced and told me that he has already fixed it and spent all his time trying to convince me that it was already fixed instead of trying to understand the issue, or if he really is convinced it's fixed, to demonstrate that in a proper way because it's a relatively complicated issue to understand (medium hard, so I expected more of him, but it's still an issue above most newbies' heads).
Here's him asking for money for light fixes:
You can even see him trying to fix the issue after all of this drama yesterday
when he wrote this.
But in actual fact he didn't fix the issue, this isn't the solution.
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)
The movement (D)DoS bug wasn't anything custom, I used the clean downgraded 1.3 TFS to version 7.72 by Nekiro, nothing modified.
It sounds like you agree with me that he's not interested in working with any other protocol version than the newest version?
I think he should make that clearer if that's the case.
And btw, if he isn't gonna "work on" (
JUST NOT BREAK) older protocol versions, maybe he shouldn't post in my thread about 7.72/8.6 Tibia in the first place telling me
I will have his support?
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).
Well, I wasn't using anything custom, and I didn't want his help because I didn't want to use his client to begin with,
he asked me to use his client so I felt invited to help him out with posting bugs,
I only posted issues because I wanted to help him with fixing his client even though it doesn't benefit me, but all these issues proved to me is that he isn't interested in fixing most things he himself breaks, and he's in my opinion very unprofessional, and I'm talking about attitude here even more than technical skill, but I also don't think the client is reliable because of his changes.
I believe you've made some great contributions to the client, such as optimizing a lot of lua code (even though I think it's less readable now, I believe you that these changes probably optimized the client), so far from what I've seen from mehah himself I can't say the same about him, I'm not gonna lie, but like I said best luck with the project, and I mean that, even after all of the toxic messages and manipulation in github trying to act like the victim and vilification of me for being honest and losing my "nice mask" for once.
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?
Thank you, that was my only point about that issue.
... Actually, your language is a bit confusing here. When you say "the source" are you referring to me or mehah's otclient sources?
If you're talking about me you should just say source or
@Source, not "the source", unless you think of me as royalty, in which case I appreciate it.
It doesn't matter whether you kick a player at 100+pps or not, it's still a (D)DoS attack, the server isn't designed to receive 100+
data packets from a single client every single second, I'm not talking about other network packets here such as SYN, SYN+ACK, ACK etc packets, I'm talking about PSH/data packets only here, that's a (D)DoS attack.
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!
I'm not sure what you're saying here. It's not mehah or other developers problems if the client is broken and other people use it?
Well, if the client is broken you probably shouldn't advertise it and pretend you're a hero for having started the project and pretend there's no issues.
It's not about the product being final, I just think mehah both acted very unprofessionally and has poorly designed the client so that it's likely to break very easily compared with original otclient, I think users of this client should be aware of that, that's all.
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...
No custom purpose, lol, just not newest protocol, I used clean downgraded TFS 1.3 by Nekiro.
And yes I wouldn't release light issue for free,
just like he told me that he won't release the fix for free either.
Why are you trying to be two-faced about this? Just admit it and accept it that there's nothing wrong with not releasing a fix to somebody who themselves want money to fix it.
Read the bottom of his comment here
now... if I stop to try to replicate the lighting system like ciptsoft, unfortunately it won't be free.
If he had acted professionally, not been rude, not tried to explain away issues, not blamed vanilla TFS 1.3 for being the issue instead of his client, and not wasted my time with this light issue by lying to my face over and over,
I might have released the fix for free EVEN THOUGH mehah wouldn't, he said it himself HE wants money for it.
But after I created this issue 195 and saw how mehah and some supporter of the project behaved,
I'm completely uninterested in supporting this project in any way in the future, including fixing light issues.
It's also very ironic to me how you talk about voluntary this, voluntary that, free choice, but you're trying to imply that I am obliged to release a light issue fix for free
when even Mehah himself said he won't?
Do you have double standards for everything or just me?
Also if you take a look at edubart's otclient I have committed issues for free, and if I didn't have a problem with Diath gatekeeping the repository, I would post more commits there for free, I already tried to add two commits to edubart's otclient that was rejected, 1)
Nekiro's fix to make OTC compatible out of the box and 2)
Add encryption that I paid a freelancer to make, released for free (first free and open source public release of encryption for OTClient ever).
But Diath rejected both commits on very weak grounds (
he thinks cryptography is "anti-open-source", so I guess he prefers criminals to steal and reuse people's artwork etc, so I've stopped trying to contribute to that repo.
Bottom line is do whatever you want, just don't lie and manipulate and blame everyone else when you have an issue and try to make yourself a hero for releasing something public, that's really poor leadership and sportsmanship, just do whatever makes you happy and be honest about the fact that the projects you work on makes you happy, you're not Gandhi for releasing an open source project, especially when it's barely functional and you don't even make it clear for example that you
will not make fixes for (or
you are happy to break compatibility with) all other protocols than the latest Tibia protocol. That's just dishonest in my opinion. Gratz on the v12+ though and good luck.
Cheers.
. On the other side, we have you. You, who is just everywhere praising himself with your nonsense and imaginary contributions and great benchmarking skills.
.
