DragonWrangler1 reports: something strange going on wit ... #5775
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#5775
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?
DragonWrangler1 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
here are the pictures
probably https://github.com/minetest/minetest/pull/13929
see https://github.com/minetest/minetest/issues/14133
so abriglass might need to be changed when mt 5.9.0 is released
it needs to be changed now, because some of us use dev clients
oh, this probably was fixed upstream, but we can't update abriglass cuz reasons #4520 (comment) #4520 (comment)
we may need to hard-fork abriglass
not sure if
67600d90ea
was out when these
commitscomments were written...At least they implemented (I did not test this) something to prevent inventory items from becoming unknown.
I'm not in favour of hard forks, I'd rather find a way to either convince upstream their way doesn't work OR find a way to make it possible. We're most likely not the only ones having that issue right now.
We're probably among the few who care so much about unknown nodes though, others apparently accept them as an inevitable part of MT?
there's apparently been some more work done on making abriglass compatible with old installations, we should try updating it on the test server again.
Cc https://github.com/Archtec-io/bugtracker/issues/137