sherkhan30452 reports: Can enter plot's private areas ... #3143
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#3143
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?
sherkhan30452 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
However when I tried to do it in some random player's plot, even though entered succesfully, it teleported me outside while turning me around. Plase ask mr_block (player) to do it at my plot for better demo.
Here is the conversation(screenshot attachment) that I had with mr_block that he did it.
Protection, door or node glitching is a known issue, so you don't need to /bug it. If you want to report a player for using a known glitch then please use /report PlayerName
is this just about someone glitching through a wall in a protected area, or is this an exploit on
/area_ban
?i should have read the discussion in that image first, clearly about the normal glitching.
i'm not sure whether we have an open bug about this, but it is technically a bug. it may eventually be fix-able mostly w/ SSCSM, but hacked clients will still always be possible.
per Jammy, this is apparently still an issue. most recent attempt to fix this was #1966.