Sokomine reports: This block is protected! Your ... #3882
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3882
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?
Sokomine reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Sokomine reports that this was a
bees:hive_wild
. i can't see any code in the bees mod that invokes custom protection violations, and i can't trigger this behavior locally (though the hive i'm testing with is still alive). i am noticing that trying to dig a single node of protected dirt with an empty hand is dealing me 3 damage, which is not right.i'm pretty sure this doesn't have anything to do w/ the hive itself, and moreso that the anti-cheat system isn't behaving sanely for some reason. i'll poke at this more tomorrow.
probably the anti-cheat system needs to take into account actual digging speed when levying punishments, not anticipated digging speed. also, lag. currently it seems to punish slow tools more than fast tools, though we also need to avoid punishing people w/ fast tools when there's actual server lag.
i figured out a big part of the issue - the protection violation wasn't taking into account the capabilities of the player's "hand" (default dig parameters) when breaking nodes, leading to punching leaves w/ an empty hand quickly creating big penalties.
this should be fixed w/
7d06dd39d7
this is live