AliasAlreadyTaken reports: Decide on replacement for cave ... #4365
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4365
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?
AliasAlreadyTaken reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Are there plans to remove "outdated" mods from CDB ever?
The question arose when looking at caverealms and I wondered whether there are lifecycles of mods. For context, there are "caverealms" (https://github.com/HeroOfTheWinds/minetest-caverealms last commit 6 years ago, some open issues and PRs) and "caverealms lite" (https://github.com/Ezhh/caverealms_lite, last commit 4 years ago, some open issues), neither of which seems maintained anymore but appear not to cause crashes in a 5.7.0 client. There is a maintained fork https://github.com/minetest-mirrors/caverealms_lite which is not in content DB.
which is our current upstream? why do we need to get rid of it? the minetest-mirror repo is a mirror of https://notabug.org/Tenplus1/caverealms_lite? why not keep using that?
oh here's our current upstream: https://github.com/Ezhh/caverealms_lite
TenPlus1's seems to be nearly identical to what we're using, i haven't tested it or done a thorough review of the diff, but the biggest changes i see are:
Ofc as soon as I said taht, more caverealms forks come up.
There's also:
asuna caverealms is here: https://github.com/EmptyStar/asuna/tree/main/mods/caverealms. it seems to be a fork of some version of caverealms_lite
Other option is that WE maintain a public fork and include bugfixes and eventually features from all others where license permits.
i'd love to do a deep dive on mapgen mods at some point, but that's over a year off on my priorities table