 dbzer0 | If you use the CGF you need to release the resulting code as well. However AGPL allows for variables, so you can keep your assets and variables secret. This is why the card data is set up to be imported as json from anywhere.
What happens if I need to interact from GDScript with 3rd party code written in C++ (like the in-app-purchase or in-game-advertising libraries in a mobile game). Would I be allowed to interact with compiled C++ code (which may be using a different license) from GDScript code covered by AGPL?
We have an exception in the license for Steamworks and similar services, but any other library you use should likewise have its code public. It doesn't have to be AGPL, but compatible with it (such as MIT or Apache)
have another question which is also related to the use of C++ code: as far as I know, the Godot game engine is released under the MIT license and CFG is obviously using Godot. Does it means I also need to release the Godot source code with the AGPL license together with the CFG source code? Am I allowed to change the Godot license from MIT to AGPL?
You don't need to change the license of Godot as MIT is compatible with AGPL. You don't need to redistribute the source of Godot as it's freely available online. | 12:01:24 |
AI Scribbles - robertcs
V
fanofdc1952
pawkygame
sliter
matrix-t2bot
nobsevilgenius
innuendo.one
hyperagon
discoking1
jakeukalane
Daigo-X
bwesh
rockbandit (artbot dev)
cozmyc
deanwinchester1971
Stable Horde Bot
zelda_fan