I’m sorry for adding the map_editor example. The reason why I addded it is because if one day I want to create a map editor for a friends game that is already working and published, seems like I can’t do it without making him pay royalties.
Anyhow, taking out the map editor out of the ecuation, will I need to pay royalties for the game if I distribute the chat app along with it and the chat app is free? it will not be used to create any content for the game, but you will be able to talk to people that are already in game, and it may use some textures from the game to make the UI feel in sync with the game.
Thanks very much. Just to be clear, if I make that map_editor (in this case, for my game), and do not distribute that software (I only use it myself to create maps for the game), then I have to pay royalties because part of the game (the maps) would have been created in part by UE, correct?
In a sense, it feels correct, and it a sense, it feels wrong, depending on what exactly the map editor is doing.
For example, if the map editor is simply using UE as a UI toolkit, and the maps generated are created using custom algorithms, then it doesn’t feel right.
This is like saying, I use UE to create the walls of my store, and then I need to pay royalties for the clothes I make/sell.
The question though, is if part of the setup is not free. Then things get complicated because arguably the game is being distributed and used a promotional tool for the paid-for app.
Just to be clear, if I make that map_editor (in this case, for my game), and do not distribute that software (I only use it myself to create maps for the game), then I have to pay royalties because part of the game (the maps) would have been created in part by UE, correct?
That’s correct. It’s our hope that you have sufficient reason to just use UE4 across the board to make the game as good as it can be. At any rate though, since our monetization model is royalties, we try to be careful to not create loopholes whereby a game (or other software) can contain very material value created by UE4 but without a royalty obligation.
These are hard to answer in the abstract - where the true answer will depend on the actual facts and circumstances (which we don’t have here). If a chat app is standalone and free, but built in UE4, there is no royalty. If a chat app is standalone and not free (and built in UE4), there is a royalty on the chat app revenue. If the chat app is not standalone but rather integrated into a larger product, that makes the larger product a Product under the EULA.
Yes, that’s the goal. However, I have just started learning to use this UE game engine 5 days ago, and it’s too soon to fully use it because the game may end up with too many bugs due to my lack of knowledge. I just wanted to figure out a way to start using UE for free and get good at it (the chat seems to be the way), and then when I’m good at it, I would use it for the game as well. Anyways, thanks very much for your help, you are a life saver!
It’s not clear from your question how the UE4 content interacts with the non-UE4 content. It sounds like you’re having people create maps in UE4 to be used in a non-UE4 game, but that resulting product is still a Product as defined by the EULA because UE4 was used (in part) to make it. So a royalty would still be owed.
Also be aware that something called Map Editor sounds like something that would qualify as a Engine Tool as that term is defined by the EULA. In which case, special distribution restrictions would apply.
