Why does Castle Rubble nodes reign like sand ... #4769
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#4769
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?
or grevel, while all slabs and cuts of it rule like stone?
Castle rubble and gravel are falling nodes. If they can be cut in the saw, then this is a either a bug or an exception. No crumbly and no falling block should be saw-able. We did that to gravel, to allow nice pathways. If the full block falls, the results of the saw should as well.
gravel is not saw-able is it? see #1351
i double checked, and the "falling_node" group is inherited by micronodes in my moreblocks fork.
So which way will Castle Rubble go? Sandy, stony or both, like at the moment? I'd like to know this before I use it to build something bigger.
Has there already been a decision?