flux reports: discussion: should machines li ... #5022
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#5022
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:
yes, that would mean less motivation to stay afk near them
What machines could be done that way? Pipeworks?
Also, wouldn't that cause lag on the block loading when a lot of machines are in there?
Probably way less lag then when players actually afk there for hours. All the block needs to do is calculate what would have happened in the meantime
Even if, afk-ing near a machine causes low, but constant lag. So far, mesecons are not among the main lag sources. Having it all run once the block is loaded might cause a lag spike, which may be way less on average, but can be felt the moment it happens.
Crafting some items in bulk seemed to cause lag spikes, will this catch-up be affected by it?
this would be applicable only to isolated machines (furnace, autocrafter, ...) doing something internally (where you can easily calculate and do the work done in given time). not for stuff sent via pipes where approximating work done would be difficult
the only "machines" this change would apply to would be the autocrafter and the workbench, so we only need to worry about crafting.
we're using https://github.com/minetest/minetest/pull/13234, so it won't take much time to just calculate a crafting result repeatedly until we're done done.
if furnaces don't cause a lag spike, and craft all doesn't cause a lag spike, i wouldn't expect autocrafters to cause a lag spike even if dozens of them were all loaded at once. if we're worried, we can throttle the feature using action_queues.
can I humbly suggest the throttle be there before. Xhoas.
hate throttling in general, but automation alwys prone to breakage.