-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MTG content #80
Comments
Full agree, great list :) We should be a bit careful with new PRs, but not overly so. It's easy to remove extraneous information later. |
|
I'll open a PR 👍
From the page:
Digging down to -31 km is something you only do in MTG and derived mod soups, having so many registered ores is something that only happens in MTG mod soups, so it's a MTG phenomenon. While the page pretends to be a generic Luanti page (even the Luanti renaming is applied), what it describes is only relevant in MTG. I'm not saying it's a bad page, but I think it's MTG content, so wouldn't belong here.
I agree that screenshots demonstrating the mapgens are useful. I also missed that the screenshots are already described as MTG screenshots on the page, so that should be ok, though something like "Not actually the bare minimum" would be better (and the "these are MTG screenshots" note shouldn't be in parentheses, as if it was implied anyway). What still remains is that the page was written with the "Luanti and Minetest Game are the same" mindset. An obvious example is this sentence:
which references MTG nodes without mentioning that these are from MTG, not from Luanti. This is an example of what I mean by "wildly mixes engine and MTG content". Unfortunately, this is probably the case with a lot of regular wiki content, and rewriting all those pages to untangle engine and MTG stuff won't be easy.
Yeah, but these MTG screenshots are used without mentioning that they're from MTG. This was again written with the "Luanti and Minetest Game are the same" mindset.
I agree. |
I think Calinou's law might be fitting for the "mods + games" section, maybe in an "advice" or "misc" subsection, though I do believe we should be wary about being too opinionated. That said, it does seem good to have an "official" reference to it when the community wants to discuss it, as it's possible for any MTG-like to run into this problem. |
As far as I know, there is consensus that this documentation project won't host game-specific content. See issue #64. However, some MTG content is already here. This should be fixed (removed) to avoid setting false expectations.
https://dev.luanti.org/building/: Mostly MTG-specific, probably nothing of value left otherwise (discussed on https://irc.minetest.net/minetest-docs/2024-12-15#i_6227520)
https://dev.luanti.org/calinous-law/: While ore registration is an engine thing, what this page describes is only relevant in a MTG context.
https://dev.luanti.org/mapgen/: Wildly mixes engine and MTG content. Mapgens are implemented in the engine and there is some useful generic information on that page, but the screenshots are MTG and the described nodes are MTG. This page doesn't have to be deleted, can probably be made more game-agnostic and it'll be fine. However, this page might be more useful if left in its MTG context since it seems it's mainly targeted at players, so removing it here might be better (not sure).
https://dev.luanti.org/mapgen/features/: Wild mix again. Explains some engine features, but only in the context of MTG. Might be better off if left in MTG documentation and removed here.
all the "Map-Database" pages: These are just lists of MTG world seeds, obvious removal candidates.
Hands
Hearts
Getting started
Groups
Creating texture packs
Many of these pages have both engine and MTG content, so they can't just be deleted. Instead, they need careful rewriting to remove MTG content, and also to remove the assumption that Luanti and MTG are the same thing.
The MTG content should probably stay on the old regular wiki for now, until someone figures out what to do with it? See also discussion in #12
This would also mean being careful with PRs so that we don't introduce new game-specific content in the future, especially when importing content from the regular wiki.
The text was updated successfully, but these errors were encountered: