DragonWrangler1 reports: when I type /protect_this I ge ... #6004
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6004
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?
DragonWrangler1 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
this seems important, please poke me until this is fixed, or i negate that command.
#5129 (comment)
this seems to be related?
whosit referenced this issue2024-01-20 11:24:22 +00:00
Cause was that I changed
due to your-land/bugtracker#5129
There is some wrong calculation at work
is there a way to fix it???? uhhh
For the records, that's how we can fix it from a running server:
//lua areas.config.self_protection_max_size={x=64,y=128,z=64}
there's two off-by-one bugs here.
one is in upstream areas - it's not accounting for the fact that the intervals include both endpoints, and so lets players protect areas that are one node too wide.
the other is in yl_areas_addon math - it creates an area that's 1 node too wide if the max size of the dimension is even, but two nodes too wide if it's odd.
upstream PR: https://github.com/minetest-mods/areas/pull/70
yl_areas_addon fix:
301061e19c
note: the fix to yl_areas_addon will resolve the problem, we don't actually need to wait for the areas fix to be accepted. we should also keep the max area size at (65, 129, 65) after this, because many such areas already exist.
noting that the problem originated with #5129
Fixed? Dragonwrangler and myself don't have any more issues on main server
It's fixed on the main by just running a command and won't be kept after a restart. A assume this is still open to make sure it's properly works after server restart too.
the upstream PR got merged
QA
Works :)
fixed