Is OK when i modified the code, then publish into play store?

[muslimmuda15]

I need update this code, so the scenario and action can synchronize to server, but i need push into playstore because the the game is block my accessibility

[Nain57]

You definitely can't. Simply because I flag any clone app on the PlayStore for duplicative content (already 5 accounts closed, one with 50+ apps).

Legally, the only way to publish an app based from Klick'r is:

• Respect the LGPL V3 license, meaning you code have to be entirely open source.
• Rework entirely the UX/UI to avoid duplicative content flag. And not just a theme change, a complete overhaul.

Klick'r is an open source project, if you think you have a feature that might be interesting for users, you should open a feature request ticket to explain it to the community, and if it is a good idea and the community likes it, then you should open a PR request with your changes

[Nain57]

I have checked your repository https://github.com/muslimmuda15/Smart-AutoClicker and I see the licence file have been removed. Klick'r is licenced as LGPL-V3, and removing the licencing is a clear public violation of the LGPL-V3 licence.

@muslimmuda15 I give one week to reinstate the licensing on any of your forks of Klick'r, after that, I will take legal actions.

Reminder of LGPL-V3:

• Forking a public repo is allowed, but the LGPL (like GPL) is a copyright license that grants recipients rights only under the terms of that license. You cannot take code that someone else copyrighted and re-license it on your own terms without their permission. Removing the LICENSE/headers and publishing the code with a more restrictive (or no) license would be a copyright violation.

• If you distribute binaries or modified source, LGPLv3 requires you to keep the license and copyright notices, and to provide the source (or an offer for the source) as required by the license. You may also need to provide means for users to relink with modified versions of the library (the “lesser” copyleft obligations).

• If the project has many contributors, you cannot relicense their contributions without each contributor’s consent. The original authors can relicense future work they control, but they cannot retroactively revoke the license from copies already released under LGPLv3.

[muslimmuda15]

noted