debian44 reports: You can put an electrumese axe ... #710
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#710
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?
debian44 reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Cannot reproduce
I cannot reproduce this either, but I can get one in there if i use an injector.
cf. #1701
What do we do? There's no group "building blocks", for which this mechanic was intended. We could
The "fix" that I'm planning to do here, is to keep it from being put into the node breaker and similar machines via tubes. I hate working on pipeworks, and I haven't heard of anyone exploiting this recently, but I do want to get to it eventually.
fixed in
a34317f3bd
andef4b09fc5b
i'm not sure this was signed off on anywhere, but i implemented a whitelist of tool/craftitems that can be put into the breaker/deployer, and added most of the "normal" tools. it was too time-consuming to try to test every item and blacklist it if there was a crash. if players feel that something is missing, they can of course request that it be added back, after we test it.
it's also possible that some "node" type has insane left/right click behavior defined that will still cause a crash, but i think this'll catch most of it.
this is live