"You can now submit this package for approval if you're ready.
Please make sure that this package has the right to the names titanium, silver, lapis." what should I do now?
The code and media for your package needs to be under an open license. I can see that you have a license file for your package (MIT), but you include the lapis mod which contains CC BY-SA 3.0 licensed assets. So you would most likely want to go with MIT for the code license, CC BY-SA 3.0 for the media license.
what should I do now?
I assume lapis is identical so that's fine, but are titanium and silver the same or compatible with the conflicting mod?
Gemstone has a media license (CC-BY-3.0), quartz too (MIT). Everything on ContentDB needs to be under a free license. What license you want your media to be under is up to you, as long as it is compatible with the licenses of the textures you've modified, it is referenced in the license file and the media license is reflected here on ContentDB. Look at how Minetest Game does it, for instance.
as you know I had a secound mod too, but I deleted it to a´make a new one with the right license. But know it says this all the time:
Oops! Something went wrong
We seem to be having technical difficulties.
Please try again in a while, and report the issue if it persists.
(but I cant report this issue because I dont have twitter.)
Probably because you're trying to make a new package with the same technical name. You're able to edit the license of an existing package, what was the name of it so I can restore it? (you have 3 deleted packages under your account, can't remember which one was your second one)
Please specify a proper license. Also, are the conflicting ore mods compatible with eachother?
How can I specify a license?
"You can now submit this package for approval if you're ready. Please make sure that this package has the right to the names titanium, silver, lapis." what should I do now?
The code and media for your package needs to be under an open license. I can see that you have a license file for your package (MIT), but you include the lapis mod which contains CC BY-SA 3.0 licensed assets. So you would most likely want to go with MIT for the code license, CC BY-SA 3.0 for the media license.
I assume
lapisis identical so that's fine, but aretitaniumandsilverthe same or compatible with the conflicting mod?Please don't mark the package as ready for review until you've actually fixed the licensing.
is the license now ok?
You need to specify the media license in the license file too. Also please update the ContentDB license metadata to reflect the licenses.
but I dont know how to do this
what schould I type there?
but why do I even need a media license, because other mods dont have a media license too.
(for example: gemstone, quarz)
Gemstone has a media license (CC-BY-3.0), quartz too (MIT). Everything on ContentDB needs to be under a free license. What license you want your media to be under is up to you, as long as it is compatible with the licenses of the textures you've modified, it is referenced in the license file and the media license is reflected here on ContentDB. Look at how Minetest Game does it, for instance.
I hope the license is correct now
Uh, you have two different license files now.
which one should I delete? or should I combine them?
For simplicity's sake just pick one and update the ContentDB licensing to reflect it, because I assume you do not intend on dual-licensing the mod.
as you know I had a secound mod too, but I deleted it to a´make a new one with the right license. But know it says this all the time: Oops! Something went wrong We seem to be having technical difficulties. Please try again in a while, and report the issue if it persists. (but I cant report this issue because I dont have twitter.)
Probably because you're trying to make a new package with the same technical name. You're able to edit the license of an existing package, what was the name of it so I can restore it? (you have 3 deleted packages under your account, can't remember which one was your second one)
I will just include the other mod in too many ores, i think
i hope the license is now finally correct. I am very sorry for the huge effort that you had with my mod.
You still haven't changed the license metadata on ContentDB...
which one was it again? CC-By3.0 right?
no wait it was LGPL 3.0
LGPLv2.1 for code, CC-BY-SA 3.0 for media, as your license file states.