this post was submitted on 10 May 2024
1 points (100.0% liked)
Godot
5884 readers
1 users here now
Welcome to the programming.dev Godot community!
This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.
Make sure to follow the Godot CoC while chatting
We have a matrix room that can be used for chatting with other members of the community here
Links
Other Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Rules
- Posts need to be in english
- Posts with explicit content must be tagged with nsfw
- We do not condone harassment inside the community as well as trolling or equivalent behaviour
- Do not post illegal materials or post things encouraging actions such as pirating games
We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent
Wormhole
Credits
- The icon is a modified version of the official godot engine logo (changing the colors to a gradient and black background)
- The banner is from Godot Design
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can tell you that I wouldn’t invest my time in developing a game if there’s no chance of selling it in the first place due to the license requirements of a third party package.
Well AGPL doesn't prevent selling, but most people think it will steal their sales, which I don't think it's true.
agpl does not "steal" sales, but i have to give my users the source code under a gpl compatible license, that includes that they redistirbute the code however they see fit.
that scares many people, but i guess they forget that your game is more than code and the license does not cover assets
Correct. Plus I think most people want to support indies, and those who would download forks, would just pirate anyway. Such fears are overblown I think which is why it was AGPL from the start. If I was still actively developing it I would keep it like this, but if MIT helps it get more traction, it might be worth it.
I don't think end users are the problem.
Anyone looking to make an easy buck can steal your source, flip some assets and sell it as their own.
That is a big vulnerability. Especially to indie Devs who potentially work on razor thin margins already.
@Lmaydev @db0 the source is typically the least important part of any game. Games with any amount of success get copied overnight by game farms; no need for coffee access.
Even more: if I need to copy a game, observing it is enough, I don't need to deal with the certainly messy original code that I don't understand well. Rewriting from scratch will certainly be faster than deciphering a 3rd party codebase.
The hard part is almost never the code, it's design, gameplay, graphics, theming...
Game design and gameplay is part of the source. All the balancing etc. to make it a fun experience. Most of the numbers don’t show up in the UI, so they'd either have reverse engineer it or reconstruct it somehow through months of game testing.
@Lmaydev @db0
For games where the code _is_ the difficult part (Dwarf Fortress, etc), its probably so complicated that having the code helps nothing, unless you want an exact copy (at which point, just pirate the game).
The number of applications or games where having access to the code helps even somewhat to do anything is vanishingly small.
While that's true, a lot of those places do the same thing already, even without available source. Copycat apps are a thing already, but with AGPL3, they would also have to share their source at least.