promotional bannermobile promotional banner

Time Bus

A block that accelerates the world-along with a series of acceleration-related items.
Back to Files

Time Bus v1.0.12

File nametimebus-1.0.12.jar
Uploader
zhen_zi233zhen_zi233
Uploaded
Aug 10, 2026
Downloads
17
Size
196.7 KB
Mod Loaders
Forge
File ID
8617340
Type
B
Beta
Supported game versions
  • 1.12.2

Curse Maven Snippet

Forge

implementation fg.deobf("curse.maven:time-bus-1638678:8617340")

Learn more about Curse Maven

What's new

v1.0.12

  • Change: Mekanism acceleration now works by re-running the machine's recipe tick multiple times per server tick instead of injecting virtual speed cards - Mek CE caches ticksRequired and only recomputes it on upgrade recalculation, so virtual speed cards had no effect while a machine was running. The new approach advances N ticks of progress per tick (per-tick energy xN, total energy per recipe unchanged) and currently covers ordinary ElectricMachine-based machines

  • Change: Mek machine GUIs now report the accelerated per-tick energy draw (base energyPerTick x speed) via Mek's own sync channel - display only, the actual power drain is untouched

  • Fix: MM restore logs no longer spam - the "restored" log now counts actual removed modifiers and is debug-level, so periodic restore calls (e.g. every 20 ticks while a bus is unpowered) stay silent unless something was really removed

  • Fix: redstone / power loss now stops MM acceleration immediately - the Time Bus used to leave its injected duration/energy modifiers on MM controllers when it went to sleep (HIGH_SIGNAL with no signal, LOW_SIGNAL with signal, a finished pulse batch, or lost power), so machines kept running accelerated even though the bus was idle. Every stop path now restores the bus's own modifiers (multi-bus stacking is unaffected - only this source's keys are removed), and restore() also clears the applied-state snapshot so re-acceleration works as soon as the redstone signal returns

  • Fix: Random Complement compatibility for the inscriber - RC's setStackInSlot redirect shrinks the same stack one more time, so the inscriber used to eat one extra input per finished recipe; with a single input left it also stopped consuming and kept producing forever. Consumption is now compensated when RC is loaded (parallel-card batches stay exact, single items are consumed and the machine stops), and behavior is unchanged without RC