whosit reports: /mesecons_whitelist_add'ed map ... #6503
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#6503
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?
whosit reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Adding
(128,0,72)
causes all a line of mapblocks from(128,0,72)
to(119,0,72)
show up as whitelisted:I don't know if it's only HUD issue, or those blocks actually work as whitelisted.
huh. the current edition of mesecons_debug was my work, but i didn't touch the whitelist logic, because i never use that.
We're probably not using the right one: The one flux made.
This is the chain:
https://github.com/minetest-monitoring/mesecons_debug
(head: d8f8104198c86240de188a786d638cd9c8f33171)
mirrored to
https://gitea.your-land.de/your-land-mirror/mesecons_debug
(head: d8f8104198c86240de188a786d638cd9c8f33171)
forked to
https://gitea.your-land.de/your-land/mesecons_debug
(head: d8f8104198c86240de188a786d638cd9c8f33171)
But this is on the server:
28c1813d36
There are many fixes by flux in that branch, but ultimately its not
https://github.com/fluxionary/minetest-mesecons_debug
This repo was forked from our upstream, but I haven't compared yet.
Should we switch to this repo? What is the agreed upon upstream? Neither of them is in contentDB
most of the changes in that fork are what i'd call "cleanup". it's not logical changes, just organization and code formatting and developer tools. honestly i forgot i hadn't tried to contribute that upstream, i was waiting to actually propose significant behavioral changes first. 90+% of the changes are things like the following, generated just by running
stylua
on the files.