I've including code from a previous version of MTG alongside a snippet of modern MTG code, do I need to specify copyright dates on a file-by-file basis?
Oh, yeah, I was thinking I could work on both simultaneously. I was thinking of renaming this package, but I don't know what to call it. I think I will draft this one until I rename it, just so that there is no confusion.
This game is a result of adding game-changing mods to minetest_game. This makes it automatically better than minetest_game, but that's not the best part. The idea behind this game, as I see it, is to combine mods that go well together to create a world that is more responsive than a typical minetest world. This game achieves this goal well, and it was fun to play.
What changes, exactly, are needed for me to release this? I'm still interested in having this up on CDB (but if it doesn't fit the guidelines, period, then that's fine with me).
Kimapr, your problem is that your minetest configuration has disabled biome generation, I think. That happens after games are installed, occasionally. I would recommend seeing if you can search up mg_flags in your in-menu settings; the biomes flag might be disabled, causing the biome generation to not happen.
The game is licensed under LGPL. Even my Github repo detects the copyright in the license.txt, so I think that means that my code is properly copyrighted, right?
My plan is to use the license as outlined at opensource.org, using the Minetest Game license file as an example. I will include this license.txt with my game in the root directory. Is this what I should do, or should I license differently?
I've including code from a previous version of MTG alongside a snippet of modern MTG code, do I need to specify copyright dates on a file-by-file basis?
Yay! Thanks!
Oh, yeah, I was thinking I could work on both simultaneously. I was thinking of renaming this package, but I don't know what to call it. I think I will draft this one until I rename it, just so that there is no confusion.
This game is a result of adding game-changing mods to minetest_game. This makes it automatically better than minetest_game, but that's not the best part. The idea behind this game, as I see it, is to combine mods that go well together to create a world that is more responsive than a typical minetest world. This game achieves this goal well, and it was fun to play.
Reply to wsor: I privated the repo, didn't think it had to be public.
Reply to Warr: Okay, I'll recontinue the mod.
This mod is complete, so it should be fine to release, right?
What changes, exactly, are needed for me to release this? I'm still interested in having this up on CDB (but if it doesn't fit the guidelines, period, then that's fine with me).
It is no longer WIP, correct.
Oh, shoot, sorry! I'll remove them from the files.
Thanks for letting me know! I forgot to disable that before release...
Kimapr, your problem is that your minetest configuration has disabled biome generation, I think. That happens after games are installed, occasionally. I would recommend seeing if you can search up mg_flags in your in-menu settings; the biomes flag might be disabled, causing the biome generation to not happen.
I'm so sorry, I didn't notice it was still set to MIT license! I set it to LGPL-2.1 only, so it should be fine now.
The game is licensed under LGPL. Even my Github repo detects the copyright in the license.txt, so I think that means that my code is properly copyrighted, right?
My plan is to use the license as outlined at opensource.org, using the Minetest Game license file as an example. I will include this license.txt with my game in the root directory. Is this what I should do, or should I license differently?
Is the solution then to use an LGPL license? I'm pretty new to copyright so you might need to give me a few pointers.
I gave it an MIT license, which is compatible.