flux reports: i wish there was a deployer va ... #2714
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2714
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?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i'd suggest just overriding the existing deployer, but i feel people would complain
What's the benefit?
Wouldn't people simply send new items to the deployer via tube?
I would complain and I like the idea at the same time lol
complain because I use the deployers "big" inv in builds sometimes instead of adding a chest and more mesecons.
like because it would also be handy if it sometimes had less slots.
@flux would it be possible to add a option to the deployer that limits available/used slots?
yeah i think something like that is the best option.
i'm making an automated tomato farm, for the purpose of producing tomatoes. if i need to store 9 stacks (or even just a single stack) of tomatoes in each machine, i'm wasting a huge quantity of tomatoes. i only need to store 1 tomato in each machine; when a tomato plant matures, it gets picked, and then a new one is planted, and then the deployer receives another tomato from the tube.
As written elsewhere you can fill the slots with non-deployable items (traditionally a stick).
most non-deployable items won't go into the deployer, to prevent crashes due to pipeworks being designed terribly, which upstream refuses to fix.
closing as a dupe of #2751