Aero reports: "/mods" command gives a link t ... #1747
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1747
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Aero reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i'd love it if
/mods
brought up a UI like/help
does, w/ info from the mod.conf files. might do this and PR upstream.I tried adding a "information" value to each of the yl_ mods and suggest using the template for all new mods, but we can hardly press this standard on others.
Template: https://gitea.your-land.de/your-land/yl_template
exhibit A: https://github.com/minetest/minetest/pull/12843
exhibit B: https://content.minetest.net/packages/rheo/modinfo/
however, mine doesn't allow you to follow links... can that even be done?
copying the URL can now be done (it is not automated link tho)
de9f73fab5
then again, there's work to be done in order to get URLs for most mods.
Content DB has a query-able API https://content.minetest.net/help/api/
And there's https://gitea.your-land.de/whosit/version_command
Until we can force everyone to comply with our standards, /mods still points to a wall of text.
Let's override /mods to point to either point to the URL https://your-land.de/additional/yl_mods.txt directly or to the faq entry "mods"
oh, i didn't even realize it had an API, it'd be really cool to use that, though it might need some manual hinting when there's multiple forks.
i'm not in favor of a solution that requires maintaining a separate file, unless that file is automatically generated. otherwise, that falls out of date quickly and is less than useful.
if i RFC some sort of additional standards for
mod.conf
files, and people react to it favorably, i'd bet we could convince a lot of major mod makers to use it, particularly if i supply the PRs.Plus it won't work for mods that are not on CDB. Like most yl mods are, like some adopted mods, forks and ... a modname is not a good unique key.
It needs to be generated after every serverstart, because that' when the technical decision is made which mods are in and which ones are out. We cannot simply iterate over the mods that exist on the server: Whatever core.get_modnames tells us. Then we need to find them on file, read their git repo and mod.conf
That's nothing a mod itself can solve. mods aren't allowed to read or even write the mod folder :D (We could disable modsecurity for this mod, but that's a bug nono, a mod should never demand that)
Adding it in a structured way to some file of the mod, be it mod.conf or any other in a machine readable way would be very much preferred.
For now I'd favour an in-mod information block like so:
https://gitea.your-land.de/your-land/yl_template/src/branch/master/init.lua#L16
Looking at minetest-modinfo, the only reason this mod requires modsecurity is access to mod.conf?
Apparently there is a function Settings() that allows readaccess to mod.conf and depends.txt:
from the documentation (because i forgot why myself):
related, somewhat: https://github.com/minetest/minetest/issues/12857
i suppose if access to the insecure environment is enough of a sticking point, i could make it optional and just not gather info from modpack.conf. it looks like the only thing i'm actually extracting from that file is the description, anyway.
Allowing insecure environment is one of the few things YL can't do.
Is that info from the modpack vital information? Can you read the mod.conf files from inside the modpacks? If so, I'd say ignore modpacks altogether and only display single mods.
Maybe we need to do that in two passes. One step in python or bash that would create a readable JSON file in the worldfolder and then some mod that would read out this JSON and display ingame.
oh, i'm also using the insecure environment to deduce which mods belong to which modpack, so they can be grouped together. but that also doesn't actually require an insecure environment - i can just use file paths to figure things out. that's not a quick fix though.
why not? i'd hoped to eventually create a custom API for interacting w/ sqlite and postgres databases, which would require additional compiled modules and access to the insecure environment.
removed the insecure environment:
4cc83cb5c0
QA
bones: Still mentions AGPL and the description reads "DEATH DOES NOT STAIN". Looking at upstream bones, there's LGPL mentioned. What's going on? Oh, the upstream has a LOT more commits than yl_stable!
castle_gates: apparently it has a linebreak in the description?
castle_masonry: apparently it also has a linebreak in the description?
cottages: The derscription is so long it runs out of the line. Maybe in such a case a tooltip might help?
mailbox was done by MisterE, but somehow mentions ME as author??
mesecons_debug notes as license: ????
worldedit: has a table reference as version
YL itself is the worst offender. Sometimes the author is Alias, sometimes it is AliasAlreadyTaken. Teh version is usually 0.0.1
yl_unified_trash has still the yl_template stuff in it
yl_xmas: description is "Some" ??
Everyone uses a different versioning scheme
Maybe we should push for the git repo URL noted in mod.conf as well: That was the initial use case
We can't do "what branch and commit are we on" in this, without shell access, right?
Even though a couple of things were found, I'd like to OK this :D
simply reading
.git/FETCH_HEAD
could workmy fork does? where? i can't find any mentions w/ grep.
No, it does not anymore, but that's how I found yl_stable bones mod was behind/out of sync.
this is live!