What Vintage KubeJS Adds to Minecraft Automation Packs
If you run Minecraft with Create and the Create: Vintage Improvements expansion, you already know how satisfying it feels to chain machines, fluids, and specialty workstations into a factory that actually looks like engineering. Vintage KubeJS is the glue mod that connects that automation layer to KubeJS, so pack makers can script and balance those processes without rebuilding a separate datapack pipeline for every small tweak. Think of it less as a content mod and more as a toolkit: it exposes Create: Vintage Improvements recipe types to your server scripts, with sensible builders for timing, heat tiers, fluids, and item quirks like springs and curving heads.
Who This Integration Is For
This stack is aimed at modpack authors and server operators who want consistent progression tuning across versions, or who need to retire default recipes when economy or progression rules change. You still get the familiar KubeJS event flow on ServerEvents.recipes, but now you can speak the same language as Vintage Improvements machines instead of fighting unsupported schemas. When you are juggling dozens of small recipe edits, assembling a playable profile quickly matters; many players find it smoother to line up compatible Forge or NeoForge builds, mods, and loaders in one place, and this mod can be easily installed via the foxygame.net launcher, a convenient, flexible, and modern Minecraft launcher where you can grab mods straight from the menu instead of hunting tabs in five different browsers.
Recipe Types You Can Script
Vintage KubeJS mirrors the mod’s workstations, so each recipe type maps to a concrete block or process you already recognize from gameplay. Supported categories include centrifugation, coiling, curving, hammering, laser cutting, polishing on the belt grinder, pressurizing, vacuumizing, vibrating, and turning on the lathe. Names in scripts follow predictable KubeJS patterns, for example vintageimprovements-style builders under event.recipes.vintageimprovements, with types such as centrifugation, coiling, curving, hammering, laser cutting, polishing, pressurizing, vacuumizing, vibrating, and turning.
Fluids, RPM, and Heat Where It Matters
Centrifugation recipes can move fluids and items through the centrifuge setup with basins, and you can express processing time and minimum RPM either positionally or with chained helpers like processing time and minimal RPM. That matters when you want honey separation, sap processing, or any multi-output chemistry moment to feel tuned instead of instantaneous.
Pressurizing and vacuumizing both lean on the compressor and basin workflow, with optional blaze burner involvement. These builders support fluid inputs and outputs, chance-based item outputs, processing time, secondary fluid routing, and the heated or superheated modifiers when your pack’s power curve should reward better burners or upgraded logistics.
Machine-Specific Knobs You Will Actually Use
- Coiling targets the spring coiling machine. You can set processing time and spring color, and still roll chance outputs when you want imperfect batches or byproducts.
- Curving uses the curving press and heads. Besides standard outputs, you can select mode, specify which head item drives the shape, and even model wear through head damage values. Head items must carry the curving heads tag expected by Vintage Improvements.
- Hammering routes through the helve hammer and anvil pairing. Blow counts and custom anvil blocks are configurable; anvil blocks you reference need the custom hammering blocks tag.
- Laser cutting lets you tune energy cost and max charge rate so high-throughput lines do not trivialize power grids.
- Polishing respects fragile items, speed limits, processing time, and multi-output tables with weighted chances.
- Turning, vibrating and other table processes expose processing time where the underlying station cares about duration rather than a single tick flip.
Custom Springs as First-Class Items
Beyond machines, Vintage KubeJS supports the spring item type from Vintage Improvements, including a stiffness setter when you define custom springs in script. That is the sort of detail pack makers notice when two springs should not behave identically in downstream recipes or quests. Pair those definitions with tags such as general spring families or small spring groups and you keep JEI, quest books, and loot tables speaking a common language.
Practical Advice Before You Ship
Treat the published examples as syntax demonstrations, not drop-in balance, because the placeholder items exist to show structure rather than to define a fair economy. Validate every tag-driven input, especially for curving heads and hammering anvils, before you rely on them in progression gates. When players complain about pacing, adjust processing time, RPM gates, or heat requirements first: those levers are exactly why scripting Vintage Improvements through KubeJS beats opaque defaults.
Closing Thoughts
Vintage KubeJS does not replace the creative identity of Create: Vintage Improvements; it hands you the steering wheel for recipes across biomes, late-game metals, and specialty processes that would otherwise be tedious to rebalance. Pair clear documentation in your quest book with sane defaults in script, test on a dedicated server instance, and your automation biome will feel intentional instead of accidental. That is the difference between a mod list and a polished Minecraft update players recommend to friends.