This is an old revision of the document!
If you're worried about having to share the source code because EasyRPG is open-source, you've been mistaken! Software that's made with open-source compilers can be sold without having to share the source code. If that wasn't the case, that would ruin a lot of businesses. Ren'Py is an example of an open-source engine that currently has games being sold on it. Aside from the tutorial, name one game that has its source available.
The free software conditions make it so that when you modify EasyRPG– not your game– you would have to share whatever changes you made to EasyRPG, and luckily our editor doesn't hold you to that. If you have to modify EasyRPG for your game, you will need to include what you changed along with the game's package (on the web or by retail box).
This does not mean you transfer your game's copyrights to anyone else! You still hold it, because you made it. You're not obligated to release it under the same license.
Yes, but you would need to share the RTP replacement parts including their license(s).
Then you would have to release it under the same share-alike license. You can only get the full rights when your derivative is not actually a derivative. Alternatively, you can look to the public domain or Creative Commons Attribution-licensed materials. The CC BY license only requires attribution (giving credit).
The rights to your own assets. Free and open source components are not entirely yours, and any user who has used those components have not violated your rights. These components can be the EasyRPG Player, RTP replacement material or derivatives, and it's within legal bounds because it's permitted by the license. Any user that has taken what is clearly your own original materials could be infringing your rights.
That is up to their author to decide. Get in contact with them, and they can discuss custom licensing with you.
Yes. Just be sure to include any changes you've made to the source code if any.
It's considered good practice to share changes with the community, but you're not obligated to share your changes if the Player's binary doesn't change. You could link to the EasyRPG site that includes the binaries and source; it's typically found at the homepage.
We want 100% compatibility with RPG Maker 2000 and 2003 games so that when they run on the original engines, they also run here. Any game or feature in a game that does not work in EasyRPG when it does in RPG Maker should get a respective bug report or feature.
It's hard to tell; we don't know if they do, and it's difficult to account for them. We often need help from developers familiar with those hacks or their creators so that we can better focus on getting RPG Maker completely reimplemented.
Probably. EasyRPG Player uses SDL, which itself has been ported to a wide range of platforms. That is the only requirement to getting it working.
Nope. The editor can only import RPG Maker games to a new, extensible format,
This is because the old format is limited, and games can be made better this way. It also allows us to go beyond what the RPG Maker engines could do. For example, we expect to make individual files for each database entry instead of big files. This makes sharing resources easier for game developers, like so: data/actors/0001.xml (or any other extensible format, XML is just one example).
It's planned, but our main priority is compatibility. That means the editor will get a smaller focus until the player is accurate. The editor's code depends a lot on the player and it needs to be stabilized first.
When it finishes. We don't have a timeframe.
If you want the project to be completed sooner, you can contribute! After all, the people most interested in EasyRPG are the ones working to complete it.