Kiyoko reports: game thinks im digging a block ... #2700
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2700
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?
Kiyoko reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
my suspicion is this was lag (possibly connection lag), anticheat, and possibly "interacting while dead".
The problem was that Kiyoko helped install a coral digging machine in an area she then most likely coowned. The dig in her name worked.
As soon as she was not entrusted to the area anymore, the machine then dug in her name a position she wasn't allowed to. Causing the effects of yl_areas_addon: Damage and turning.
i'm wondering whether to consider this a bug in pipeworks, or a bug in the protection violation detector.
depends if "mesemaker as a service" builds should be prevented, if yes I would say its pipeworks that should check the protection
decided it's a pipeworks bug. the wielder machines should check that they can modify the node in front of the machine before attempting to do anything.
Usecase that supports the current behaviour: Evil A places a nodebreaker at the border of B's territory and gnaws on the border.
Usecase that says the current behaviour is a bug: Nice mesemaker A installs a machine including a nodebreaker on the territory of non-memsemaker B, then is removed from the area.
I don't think we can have one without the other, unless we make crazy exceptions. I wonder why this worked in the past? Did the nodebreakers get "owners" lately?
check both positions
nodebreaker = only run if owner is in the protection
infront of nodebreaker = only dig if in protection
upstream PR: https://github.com/mt-mods/pipeworks/pull/42
Merged less than 5 minutes after you sent the PR :D Thankyou wsor!
We'll also update
yeah, while i'm not a huge fan of some of mt-mods "solutions", they are at least really prompt about dealing w/ PRs and well described bug reports.
note: further upstream drama
How is this situation solved in the other technic mods?
pipeworks isn't a technic mod? technic machines don't try to fake being a player, so far as i know?
This is exactly why players shouldn't bulid machines for other players and each player should have to earn their own mese privs!
In the case of someone having control over a significant build (like Hulda's) that would otherwise have been deleted entirely - it's a bit more complex - but I suppose the bitter pill to swallow is that the people interested in seeing it could come and study it and then a master mese maker could dismantle whatever runs it so that a non-mese priv player can't cause these sorts of issues.
Not to hyjack the wrong issue here but maybe Hulda's area could be preserved by someone else (not me!) and just leave me on the list as an administrator for access only. This is the second time now that a major area has been left to me... ofc I want to look after it if I can, but there's got to be a smarter way to do it.
this is live