Skip to main content

Crafting CPU priority

Mod version shipped with FlammiCraft: 1.48.0

Overview · Deutsch

Crafting CPUs carry a priority for the crafting job they are currently running. This feature is integrated from the AE2 Crafting Priority mod; the standalone mod must not be loaded additionally.

What the priority does

Several running jobs can compete for the same machines behind a Pattern Provider. When a machine frees up, the priority decides which waiting job uses it next. The default is 0; higher values win. A job at priority 100 gets the next free machine before a simultaneously waiting job at priority 10. The set priority also influences which Crafting CPU accepts a new job when several are eligible.

  • Running jobs and machine occupations are never interrupted; only the next use of a freed machine is ordered.
  • Jobs with equal priorities follow AE2's usual iteration order; the sorting only takes effect between different values.
  • The ordering stays best-effort: depending on network load and machine offers, a lower-priority job can finish before a higher one.
  • The difference only becomes visible when jobs actually contend for the same machines.

Setting the priority

  1. During the crafting request: hold ALT while confirming the amount (the Next button or Enter). The flow then becomes amount → priority → CPU selection and start, and the priority screen opens with AE2's number field, the hint "Higher value runs first" and the Next and Cancel buttons. Next applies the entered value; leaving it unchanged keeps priority 0 as before, and Cancel returns to the amount screen. The CPU preselection and the start-immediately choice are preserved; long and exact amounts also run through the priority step. Without ALT the request goes straight to the CPU selection as in AE2, the job starts at priority 0 and Back there returns to the amount screen. ALT can be combined with Shift (start immediately).
  2. On the Crafting CPU screen: the priority icon button next to Suspend and Cancel in the toolbar opens AE2's regular priority editor for that CPU.
  3. In a terminal's Crafting Status tab: select the CPU on the left; the same button opens the priority editor. The back button returns to the Crafting Status tab instead of the machine view.

CPUs with a running job show their value behind their name in the Crafting Status CPU list, for example "CPU #1@100". CPUs without a job keep AE2's usual display.

A priority set through the priority editor (items 2 and 3) stays on that CPU, also across save/reload and the cluster's form/reform cycles, until its job ends; then it resets to 0 automatically. A job submitted through the priority step overwrites the stored value.

Behavior and limits

The automatic reset to 0 applies on job completion, cancellation and failure, as well as on malformed job data found when the world loads. While the job runs, the value is retained.

Editing a crafting CPU priority requires the AE2 CRAFT permission, just like starting a job or opening the related screens. Without a security terminal the check passes. A denied value is ignored: the screen accepts the input while the server keeps its stored value, and a job starting anew remains at 0.

Request paths without the amount screen or without ALT skip the priority step and submit with the CPU's current priority, usually 0: recipe transfer from crafting terminals and jobs of the ME Requester.

Compatibility and old worlds

The standalone AE2 Crafting Priority mod is declared incompatible and does not load beside this integration. Worlds that previously used it load without errors; the priority values it left behind use a different storage format and remain unused. Without the standalone mod, AE2 behaves unchanged there again. Supporting mods such as ExtendedAE, MEGA Cells, Applied Mekanistics or NeoECOAE need no adjustments.

Nothing has been validated automatically. The menu transitions, screens and job submission are reviewed at source level against AE2 Reforged 19.55.0; in-game acceptance (priority order under contention, saving and reloading, security permissions) remains pending. A local build does not prove the installed pack version.