Azelf reports: opening this aspen wood fence ... #6323
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#6323
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?
Azelf reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i haven't confirmed this, but it'd be a bug if you can open the gate but still get pinged for a protection violation.
confirmed...
the protection violation seems to be in code introduced by the leads mod. need to report it upstream but i'm about to go out the door.
huh. it's apparently not just leads itself, something deeper...
on my local YL server:
on YL main:
as i can't reproduce this locally, i can't really debug what's going on here. what version of leads is installed on the server?
I noticed that on test server I don't get protection violation when I open same gate.
Also, leads just do this:
and both on test and on main
leads.interaction_blockers
table is empty.i should have mentioned, the debug data i was dumping was for the on_rightclick callback of the fence. i have no idea how that's getting set, leads doesn't do it on its own, and the implicated function isn't publicly accesible, at least w/ the current version of leads.
that function isn't immediately relevant.
minetest.record_protection_violation
is. i've been testing things by registering an alert withminetest.register_on_protection_violation
, but the debugging data for the gate'son_rightclick
behavior is what's super sus, but unexplainable. i feel like there's some cascading sequence of integration mechanics that's causing this, but i don't see where to start looking.Also it's weird that the gate still does get open...
And just right-clicking fences also pings you...
Ok, it's just this:
3fad55a571/api.lua (L238-L248)
which is called from here:
3fad55a571/internal.lua (L43)
how it should actually handle doors though?
So, is_knottable() somehow got broken on main, but not on test?
@AliasAlreadyTaken what version of leads is installed on the server?
This one:
89322baf5c
Leads was switched out with new upstream, they finally decided to put it on git. 1.1.122 has the trashcan one, 1.1.123 (thus the testserver and every new checkout) will have the new upstream
alright, that makes sense, seems this will be fixed with 1.1.123 already then. marking as QA/OK
this is live