I dont think I'm willing to do that at, least not in the near future. Since this is a minigame, to mostly be installed on minigame servers, Its not terribly likely to be installed with those other mods. The name makes sense and is pretty well ingrained in the code.
While it would be pretty easy to change the modpack name to gems_mg and the gems mod inside to gems_api, it would not be easy to change the api global variable of "gems"
Any how, does this mean that I cant have it on CDB?
I solve most of my name conflict things by handling my modname (and repetitive modname-related stuff) as follows:
local ns = minetest.get_current_modname()
minetest.register_node(ns .. ":node", {
...
and so on, I find it improves readability and helps upon cases like this (on large projects like this, it would've been most useful if you had done it when you started, just in case you wanted to change your modname later on). This also allows for longer modnames without it worsening readability.
I've skimmed thru all the projects code and I don't think it would take you longer than 20 minutes to change the global variable "gems" since it's a simple "find and replace" operation, or at least it looks like it. If you are struggling with a name for it, gems_mg seems good enough for a global.
Changing the modnames to "gems_mg" and "gems_api" seems fairly easy enough.
Give it a try and if you come back finding it actually is too much effort I will make an exception and allow it to keep the name "gems", since you make a pretty solid argument, it is just a minigame that is probably going to be installed only in minigame servers.
Package doesn't have right to its name, please change its technical name
I dont think I'm willing to do that at, least not in the near future. Since this is a minigame, to mostly be installed on minigame servers, Its not terribly likely to be installed with those other mods. The name makes sense and is pretty well ingrained in the code. While it would be pretty easy to change the modpack name to gems_mg and the gems mod inside to gems_api, it would not be easy to change the api global variable of "gems" Any how, does this mean that I cant have it on CDB?
I solve most of my name conflict things by handling my modname (and repetitive modname-related stuff) as follows:
and so on, I find it improves readability and helps upon cases like this (on large projects like this, it would've been most useful if you had done it when you started, just in case you wanted to change your modname later on). This also allows for longer modnames without it worsening readability.
I've skimmed thru all the projects code and I don't think it would take you longer than 20 minutes to change the global variable "gems" since it's a simple "find and replace" operation, or at least it looks like it. If you are struggling with a name for it, gems_mg seems good enough for a global.
Changing the modnames to "gems_mg" and "gems_api" seems fairly easy enough.
Give it a try and if you come back finding it actually is too much effort I will make an exception and allow it to keep the name "gems", since you make a pretty solid argument, it is just a minigame that is probably going to be installed only in minigame servers.
ok, thank you, Ill get to it soon.