Sokomine reports: furnaces, when their output sl ... #5053
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#5053
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?
Sokomine reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i'm not sure whether or not this is intended
is this not intended? i remember having these issues occur i think on other servers and just figured it was normal
I'm relying on this behaviour for decoration. I hope it's intended.
Doesn't sound like it's intended. What is it used for? Having a permanently "burning" furnace without fuel consumption or item cooking?
When the output slots of furnace [1] are filled, current fuel state is saved and the furnace stops producing (since there is nowhere to put the result). In this state the node also displays it's "cooking" decoration (i.e. flame) without any cost, since the fuel state is saved.
[1]: it seems any cooking provider behaves like that - at least yl_fireplace:fireplace is also affected
having the option to have a furnace appear to be "on" seems like a reasonable decoration option. there doesn't seem to be a way to cheat this to gain resources or something. i vote to close this as "won't fix".
I don't like it because it is certainly not intended. The preferred way would be to make a decor always on furnace, much like the pebble solution on the fireplace. That would keep things consistent.
Would that make any difference or gain us a lot? No. Would it existing break builds? Yes. Would it surprise people? Old ones yes, new ones no.
So I'm ok with closing as wontfix.