mrminer reports: indestructable wall ... #4670
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4670
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?
mrminer reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
this is the bottom of the world. here, there is
i'm not sure which of these this is about, or whether it's about something else entirely. if it's (1), this is technically a dupe of #4621. if (2), #3938. if (3), #982.
The void is loadable. the server just doesn't tell the client about it.
The real "unloadable" area starts at -32000.
(After all, the falling sand is an entity, how could it fall into a permanently unloaded area?)
i suppose i meant "unloadable by the client". i'm not sure what you mean by "the real unloadable area starts at -32000", you can get the server to read and write mapblocks far beyond that limit (beyond the 16 bit limit, even).
also, you failed to clarify what this issue is about? should i just close it as a dupe?