Skip to content
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

Update branding and docs to acknowledge rename of Minetest to Luanti #210

Open
3 tasks done
Lazerbeak12345 opened this issue Dec 2, 2024 · 1 comment
Open
3 tasks done
Labels
major-update Mod removal or major update requiring additional scrutiny prio-high Issue should be solved as soon as possible

Comments

@Lazerbeak12345
Copy link
Collaborator

As you are almost certianally aware by now, Minetest, the game engine, was recently renamed to Luanti. I waited to report this issue until the following conditions were met, as they have now been.

Of note is that the legacy game "Minetest Game" (provider of the default mod) did not change it's name.

It's certain that WhyNot in it's current form is a derivative of that legacy game, targeting the Luanti game engine.

Personally, I'd prefer to follow as their new landing page does and in reference to Luanti, we should refer to Luanti as "An open source voxel game engine" when relevant.

Part of this may involve renaming our organization name, as "minetest" there refers to the game engine, and it's well understood that we may be releasing Whynot for other games like Nodecore and Hades in the future.

@Lazerbeak12345 Lazerbeak12345 added the major-update Mod removal or major update requiring additional scrutiny label Dec 2, 2024
@Lazerbeak12345 Lazerbeak12345 changed the title Update branding to acknowledge rename of Minetest to Luanti Update branding and docs to acknowledge rename of Minetest to Luanti Dec 2, 2024
@Lazerbeak12345 Lazerbeak12345 added the prio-high Issue should be solved as soon as possible label Dec 2, 2024
@dacmot
Copy link
Collaborator

dacmot commented Dec 17, 2024

Yes I noticed the change. Very good points!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major-update Mod removal or major update requiring additional scrutiny prio-high Issue should be solved as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants