• 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!

Found this recently hope you enjoy :) OTCv8 + Sources

Although I get your point, leaked source files do still have MIT License on them, even if it was hereby granted that buyers should not resale or share the sources after payment, the copyright that is stated in the files states that they can be shared, sold, and whatever, but this is OpenTibia we're talking about, almost nobody here cares about laws or copyrights even.

I am not a lawyer but each leaked source file has edubart copyright on them and MIT license, not a different copyright notice, legally speaking buyers could share the files and not be sued because of this tiny detail.
Right... Its still based on Edubarts files so ye... That makes my post invalid.
 
guys let's be adults about this and pay 5k € for use this client with free license
 
Just like 2020 leak, this will become outdated and open source mehah client will be more popular (for developers). It is a shame OTLand mods don't remove this thread though. Big insult to kondrah imo.
 
Last edited:
Tibia gets hacked (social engineering) - Everyone laughs and says nice.
Someone releases source files they paid for legally - Outraged community
Did you expect Cipsoft to create account here and do the same?...
 
You mean cry? No, they probably wouldn't.
I wasn't going to comment here, but I can't help but laugh at all those saying this is unfair with people who were putting their work on v8. It's incredibly inaccurate to think Kondra, Oen or any other developer had "their" work leaked for free. It was always free, they just made some minor changes on top of edubart code and leached money out of desesperate ot admins.
The guys didn't even had the trouble to change the license... so as Kondra used to say about original otclient "MIT license allows me to do that".

By the way, just a refresher on the original author point of view:
 
threat.png

If it turns out there is malicious code in this leak, did OTLand staff fail to act by not deleting the thread?
 
If it turns out there is malicious code in this leak, did OTLand staff fail to act by not deleting the thread?
No because it's inside github and no one needs to download anything there as you can just take the code and recompile yourself.
Now, assuming this is not a false positive, let me revert back the question to you and assume it's not the leak that has a virus, but the otclient itself. Did otland staff failed to not delete closed source content from the community in first place in your opinion?
1) How otland have kept this topic in the forum? I mean, I'm not even talking about a guy literally trying to scam people for money in a project that still has the sames bugs that regular otclient, I'm talking about a program that we have no way of knowing if it's malicious or not nor which data it collects from you. It may as well be collecting all the passwords that are inserted and trying to hack accounts from your server. Who knows? Even if someone here appears and says "hey, I bought the source and don't have any malicious code" it could just be a different build.
I've raised this years ago, now that this has leaked suddently people care? :rolleyes: Too opportunistic if I may say.
 
I wasn't going to comment here, but I can't help but laugh at all those saying this is unfair with people who were putting their work on v8. It's incredibly inaccurate to think Kondra, Oen or any other developer had "their" work leaked for free. It was always free, they just made some minor changes on top of edubart code and leached money out of desesperate ot admins.
The guys didn't even had the trouble to change the license... so as Kondra used to say about original otclient "MIT license allows me to do that".

By the way, just a refresher on the original author point of view:
You can't change the license, otclient came with the license that says you need to keep the license. As kondra was doing nothing wrong, because MIT license was designed to allow people to do what kondra did (what a déjà vu), anyone with a copy was in the right to republish it, as stated in the license. The license is really small, all people here should read it.

Recapping:

Selling otclient for any amount of money is ok, as stated in otclient license.

Publishing any fork of otclient, also ok, as stated in otclient license.

Changing otclient license, not ok, as stated in otclient license.

Code:
OTClient is made available under the MIT License

Copyright (c) 2010-2020 OTClient <https://github.com/edubart/otclient>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
 
[...]
Changing otclient license, not ok, as stated in otclient license.

Code:
[...]

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

[...]

How about sublicense? It sound like change license in some cases.
 
How about sublicense? It sound like change license in some cases.
AFAIK you could use a different license only for the code you developed that do not depend on the already licensed one. Otherwise, if you would like to change the license, you have to ask every otclient contributor for permission 🙈
 
As a community, we should behave responsibly and don't use these sources from leak if their authors don't wish to do so.

This seems valid for me. Why I would spend my time working on something that doesn't have any support? I mean, if I have some issue or don't know how to do something, opening a support thread actually will be a headache because of the discussion or, there will be will to help?
 
AFAIK you could use a different license only for the code you developed that do not depend on the already licensed one. Otherwise, if you would like to change the license, you have to ask every otclient contributor for permission 🙈


Sublicense the code: This means you can incorporate the original code into a modification with a stricter license.
 
when will it be merged into official otland otclient? or mehah perhaps (his otclient is quite good in my opinion and quite similar)
we need to revive and MAKE OPEN SOURCE OTCLIENT COMMUNITY GREAT AGAIN and keep it ALIVE by CONTRIBUTING FREQUENTLY
LETS MAKE A PROJECT TOGETHER WHICH WILL BE 2200 FUTURE MUSEUM WORTHY
 
Back
Top