JeCel reports: Sometimes when loading the fur ... #1983
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/petz
3. source/testserver
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/QA main
4. step/QA NOK
4. step/QA OK
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
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1983
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
JeCel reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I think that mostly (or only?) happens when the furnace has been active for a while, without you being close to it. Usually when you then get to the furnace the server still has to register, that all the nodes you put in a while ago, should be smelted now, usually resulting in a load noise (all the noises of the single smelted nodes combined). And when loading the furnace in that little period of time, it smelts that stack, too, by an instant.
This is the intended behavior, and was supposed to be for a while, but pipeworks was breaking the feature from minetest_game. Unless you really think this is a problem, I'd vote to close this as "not a bug".
See #50
But why would that behaviour be intended?
furnaces catching up with the melting job after being reloaded is intended behavior but you shouldnt be able to quickly add another stack that also gets melted instantly.
does that happen?
the furnaces are supposed to "catch up", so that leaving the area doesn't stop them from working. this is like crops will grow instantly if you haven't been around them in a while.
Yes, that I know, but that's not what I meant. What I tried to explain is what Bla said. It already happened two times to me.
Alright, then that's an upstream bug....
upstream issue:
https://github.com/minetest/minetest_game/issues/2996