flux reports: my party name doesn't re-appea ... #1249
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#1249
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?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
update: the party name did reappear after a while, but it should be back immediately, so that is still a bug.
@AliasAlreadyTaken the correct way to fix this, and several other name-related issues, is with a name monoid, which other mods would then depend upon and use if it's available. The name monoid in more_monoids which i wrote for blocky, is not flexible enough for our use cases - which include totally disappearing the tag, layout, and color - so i'll start work on something new.
@AliasAlreadyTaken
I've got a working version of the name monoid now, with minimal changes to invisibility (the API redo for that has consequences to several more mods, and can be addressed later).
https://gitea.your-land.de/flux/name_monoid
However, this will require adding the mod to yourland-mods, and pushing changes to the following mods:
All of the changes are minor, and don't have a hard dependency on the name_monoid, so they could be pushed now without breaking anything. How would you prefer I proceed with this?
I pushed the updates to mobs_balrog and yl_nether_mobs, as that was clearly just buggy behavior, and created three PRs for the other mods:
Maybe you should publish your name_monoid, it might be useful for a lot of others who deal with the same problem. We simply can't be the only ones having to deal with mods competing over the player name.
https://github.com/fluxionary/minetest-name_monoid
this is live, i believe.