-
Notifications
You must be signed in to change notification settings - Fork 0
SCP 914
SCP-914 processes items, entities, and players inside a configurable intake area relative to its winding key.
Explicit JSON recipes are authoritative. When an explicit recipe matches the selected setting and intake, it always wins.
Only when no explicit recipe matches may SCP-914 infer a conservative transformation from registered crafting recipes and material relationships. This provides broad vanilla and modded integration without making configured recipes unreliable.
Once a valid cycle starts, the complete detected item intake is consumed, even when only part of it was needed for the selected result.
If the machine is wound without a valid intake, it waits for up to 40 ticks (two seconds). A solo player can enter during that window. If nothing valid enters, the attempt is abandoned.
- Rough — destructive disassembly or severe player outcome.
- Coarse — partial component recovery or destructive player outcome.
- 1:1 — equivalent-category transformations; players receive a random configured skin.
- Fine — constructive crafting/refinement; players receive temporary enhancement followed by collapse.
- Very Fine — stronger refinement and stronger temporary player enhancement followed by delayed collapse.
-
setting:rough,coarse,1_to_1,fine, orvery_fine; -
item_inputsand counts; -
entity_inputs, counts, and optionalconsume; -
item_outputs; -
weighted_item_outputs, selecting one result by relative weight; -
entity_outputs; -
chancefrom 0.0 to 1.0; -
copy_input_nbt.
Fragment files in 914recipes.d append recipes after the main file in filename order. Repeating an ID does not override an earlier recipe.
The fallback resolver may:
- select crafting recipes that consume available materials;
- infer equipment disassembly by material tier;
- avoid extreme 1:1 quality jumps;
- use Fine behavior as a fallback for Very Fine where appropriate.
The resolver never overrides an explicit configured match.
Entity inputs and outputs remain explicit because they cannot be derived reliably from crafting recipes. The in-game list renders lightweight cached previews for visible entity rows and uses a generic fallback when a safe preview cannot be created.
The current default pool contains five numbered skins:
skin1.png
skin2.png
skin3.png
skin4.png
skin5.png
Additional 64×64 or legacy 64×32 Minecraft skin PNGs may be placed in:
config/scpadditions/scp914_skins
The server synchronizes only the selected filename, not PNG bytes. Every multiplayer client that renders the skin must have a PNG with the same filename and Kleiders Custom Renderer API installed.
The SCP-914 Assembly Kit places the complete machine structure and refuses placement when the required volume is blocked.