ContentDB hat unsichtbare Hürden ...

[Boot]

... zumindest für mich. Wer kann helfen?

Am 27.09.2025 habe ich dort eine Mod hochgeladen. Seitdem steht sie auf "Draft". Ok, zuerst dachte ich, die Bearbeiter dort haben einfach so viel zu tun, es dauert eben eine Weile. Dann kam ich auf den Trichter, dass auch irgend etwas nicht stimmen kann und fand immerhin alleine heraus, dass Screenshots eine Mindestgröße haben müssten, die wesentlich höher liegt, als im Modding-Handbuch beschrieben (300x200). https://rubenwardy.com/minetest_modding ... eenshotpng

Dummerweise steht davon auch nichts direkt in der ContentDB. https://content.luanti.org/policy_and_g ... creenshots

Erst mit einem Screenshot von satten 1921x1034 [!] wurde zumindest die Größe akzeptiert. Also dachte ich, jetzt steht der Veröffentlichung nichts mehr im Wege, aber nein, die Mod steht weiterhin auf "Draft".

Bildschirmfoto vom 2025-11-06 20-25-30.png (927.08 KiB) Viewed 264 times

Ich habe keine Ahnung, woran es jetzt immer noch hakt? Wer kann helfen?

[rubenwardy]

The problem is the red banner at the top:

Die Freigabe wird noch importiert, oder es liegt ein Fehler vor.

The release was rejected for the following reason:

Found depends.txt at /. Delete this file and use depends in mod.conf instead

https://content.luanti.org/threads/11705/#reply-47575

You need to resolve this by removing the depends.txt file, adding the depends to mod.conf, and then uploading a new release. Then you can select "Submit for approval"

[Linuxdirk]

The release was rejected for the following reason:

Found depends.txt at /. Delete this file and use depends in mod.conf instead

Do you think you could implement exactly that as error message? This would help people a lot more than a generic “Fix the errors” without telling people what the errors are.

[rubenwardy]

Do you think you could implement exactly that as error message? This would help people a lot more than a generic “Fix the errors” without telling people what the errors are.

It's a little bit tricky as the error messages aren't kept around associated to the release. When you first create the release, you'll see the full error message on the "Working" page. You'll also receive the full error in the "Bot messages" thread. But it's not associated to the release itself, which makes it hard to pull out the error months later and show on the homepage. I'd have to rework the tasks/release feature and allow showing the error on the release itself. Created this issue: https://github.com/luanti-org/contentdb/issues/616

[Boot]

Thank you for your answers.

[Boot]

The release was rejected for the following reason:

Found depends.txt at /. Delete this file and use depends in mod.conf instead

https://content.luanti.org/threads/11705/#reply-47575

You need to resolve this by removing the depends.txt file, adding the depends to mod.conf, and then uploading a new release. Then you can select "Submit for approval"

Thank you for your answer. This depends.txt was deleted on the 27th of September. Look: https://gitea.your-land.de/Boot/Boots_P ... ranch/main

[rubenwardy]

Thank you for your answer. This depends.txt was deleted on the 27th of September. Look: https://gitea.your-land.de/Boot/Boots_P ... ranch/main

You need to make a new release on ContentDB. You've removed depends.txt in Git but not on ContentDB. Whenever you change Git, you need to update it on ContentDB too (there are tools that let CDB do this automatically once you're approved)

[rubenwardy]

Do you think you could implement exactly that as error message? This would help people a lot more than a generic “Fix the errors” without telling people what the errors are.

Releases now have states, which means ContentDB now knows that the release creation failed and so shows this instead. More work would be needed to actually show the error here, I'm leaving that for now. It's not high priority as the user will see the error anyway as part of making the release