flux reports: signs (e.g. signs:wooden_long_ ... #5553
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#5553
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:
I take this issue. (Alias can't assign me due to permission issues)
Never happend to me :\
hm. it's inconsistent for me, and only seems to happen on the your-land server - i can't get it to happen on a local server, even when creating artificial lag...
and it only seems to happen once for each sign, but resets when i leave the area and come back?
Does it happen on the testserver?
If so, does it happen to signs that are //saved and //loaded via WE?
test server is down, but it does happen locally when i'm running my your-land clone
if the sign is susceptible, then yes.
i figured out why i could't replicate this locally initially - it only happens when using the mt-mods fork of display_modpack, not the pyrollo fork. i've traced it to this commit:
1f8e99c9c5
the issue is that when a player is looking at a node formspec, and the node formspec is modified, what the player sees is also modified. but looking at that commit above, right-clicking the sign should only modify the formspec if it needs to have that fix applied. however, i'm having this issue multiple times on certain signs, and also for new signs that were placed well after the fix was applied. something else might be modifying the sign formspec, perhaps...
Explanation: Minetest sends the nodemeta automatically and doesn't need a server step to show up the node formspec. when the lag is high enough, the formspecs gets visibly re-setted (that removes the already written, but not send text).
Fix: Remove the
on_rightclick
callback and update all formspecs via a single run LBM.Should be fixed by https://github.com/mt-mods/display_modpack/pull/9 (already on the testserver).
The main PR is merged and introduced a regression. https://github.com/mt-mods/display_modpack/pull/10/ is required too.
QA
IMO it's fixed.
this is live