ContentStudio

The project is designed around in-game administration. Where a feature changes shared gameplay data or server rules, the server remains authoritative; client-only presentation features stay local to the client. Configuration screens use KineticCore's UI and configuration infrastructure.

• Visual recipe creation, editing, preview and removal for supported vanilla processing types.
• Loot editing for entities, blocks and loot-table containers with weighted pools and removal rules.
• Villager profession/level trade editing and wandering-trader trade control.
• NBT-aware item tooltip rules with normal, Shift and Alt presentation modes.
• Search, filtering, item return/inspection and preview workflows through KineticCore.
• Optional JEI, EMI and REI interoperability for item/recipe discovery.

• Open the KineticCore configuration center with its configured F6 entry and select Content Studio.
• Server-owned settings are saved by the server and synchronized where the feature requires client awareness.
• Client-only presentation settings remain local.
• Individual feature areas document their own data/configuration paths below.
• Search, list selection, item/entity inspection, tooltips and return/navigation controls reuse KineticCore UI components where available.

Recipe Editor provides an in-game workflow for creating, editing, previewing and removing recipes. Server administrators and modpack authors can manage supported recipe types visually instead of maintaining every recipe by hand in JSON.

Recipe Editor uses a datapack-driven, server-applied workflow. Custom recipes and removal rules are stored in KineticCore's dedicated datapack directory and are applied through Minecraft's server datapack reload process.

Data file:

config/kineticcore/datapack/data/contentstudio/recipe_bundle.json

The file contains both:

• recipes: custom recipes created and managed by Recipe Editor.
• removals: recipe-removal rules.

Supported recipe types:

• Crafting Table
• Furnace
• Blast Furnace
• Smoker
• Smithing Table
• Stonecutter

The editor uses visual item slots for recipe inputs and outputs and provides item search, tag ingredients, NBT editing and output-count controls.

Crafting recipes can switch between shaped and shapeless modes.

Recipe inputs can use either regular items or item tags.

Tag ingredients use full IDs beginning with #, for example:

#forge:ingots/iron
#minecraft:planks

Paper is used only as the visual placeholder for tag ingredients inside the editor. The actual recipe still uses the corresponding Item Tag.

Item search supports localized names, item IDs, @modid and #tagid queries.

Input ingredients support three NBT matching modes:

• None: match the item type without validating NBT.
• Weak: the item must contain the required NBT but may contain additional NBT.
• Strong: the item's NBT must match the configured NBT exactly.

An NBT editor is available for editing the required data directly.

Recipe types that support output NBT can optionally preserve the configured NBT on the result item.

The custom-recipe management screen can:

• Browse recipes managed by Recipe Editor.
• Preview inputs and outputs.
• Edit existing recipes.
• Delete existing recipes.
• Refresh recipe records from the server.
• Display invalid recipe data for repair.

Recognizable invalid slots are shown with error placeholders so they can be replaced in the editor instead of silently hiding the broken recipe.

Unresolved configuration entries that still need to be retained are preserved where possible when other recipes are saved, reducing accidental data loss during visual editing.

The removal manager browses the server recipe catalog by output item and supports removing either individual recipes or groups of recipes.

Supported removal modes:

• RECIPE_ID: remove one exact Recipe ID.
• OUTPUT: remove recipes by output item.
• MOD: remove recipes by source mod.
• TAG: remove recipes by item tag.
• TYPE: remove recipes by recipe type.

The item list can be searched by item name, ID, mod or tag. Selecting an item displays its server recipes on the right side.

Recipe outlines show the current state:

• Yellow: selected recipe.
• Blue: hovered recipe.
• Red: disabled by a removal rule.
• Green: currently valid.

Detailed state information is shown through hover tooltips instead of permanently occupying list space.

Clicking a Recipe ID only selects the recipe. The built-in detailed preview is opened explicitly with the Preview Recipe button.

The removal-scope menu provides quick access to:

• @Mod
• #Tag
• Recipe Type

These options are used to create or adjust bulk removal rules.

Unsaved removal edits can be reverted. Saving writes the rules to recipe_bundle.json and reloads server datapacks so the changes are applied immediately.

Recipe Editor includes its own recipe preview screen for displaying the selected recipe's inputs, output and basic recipe information.

It also provides optional integration with:

• JEI
• EMI
• REI

None of these recipe viewers is required at runtime.

When only one supported viewer is available, the Recipe Viewer button opens it directly. When multiple viewers are installed, Recipe Editor provides a selector menu.

When JEI is available, Recipe Editor can precisely open the selected recipe where supported. EMI and REI are used to open recipe results for the selected item.

Without any external recipe viewer installed, Recipe Editor's built-in editing, preview and removal features remain available.

• Shaped and shapeless recipes are supported.
• Up to 9 input slots.
• Output count range: 1-64.
• Output NBT is supported.

• Requires template, base and addition inputs.
• All three inputs are required.
• Output NBT is currently not preserved.

• Single input.
• Cooking time: 200 ticks.
• Experience: 0.

• Single input.
• Cooking time: 100 ticks.
• Experience: 0.

• Single input.
• Cooking time: 100 ticks.
• Experience: 0.

• Single input.
• Configurable output count.

Creating, editing or deleting a custom recipe first writes the change to:

config/kineticcore/datapack/data/contentstudio/recipe_bundle.json

To avoid repeatedly reloading all server datapacks during a sequence of edits, custom-recipe changes are saved first and then applied with a single datapack reload after the complete recipe-editing flow is closed.

Recipe-removal rules are saved to the same data file and trigger a server datapack reload immediately when the removal changes are saved.

During server startup or datapack reload, Recipe Editor reads recipe_bundle.json and applies its custom recipes and removal rules to the final server recipe set.

Recipe Editor is a server administration feature.

Opening the editor and modifying, deleting or applying recipe data requires Minecraft permission level 2 or higher.

Recipe Editor registers a server-managed configuration page with KineticCore.

Open the Recipe Editor page from KineticCore's configuration interface to enter the recipe hub.

The current source project uses:

• ForgeGradle 6.0.24
• Official Mappings
• Forge 47.4.0+ toolchain

Default local dependency directory:

D:/IDEA_Caches/libs

For source compilation, that directory must contain KineticCore and JEI JARs recognized by localMod(). JEI is a compileOnly dependency in the source project and remains optional at runtime.

Default build output directory:

D:/NEWMODS

Generated mod filename:

contentstudio-<version>.jar

• Mod ID
• Recipe ID
• Output Item
• Item Tag
• Recipe Type
• Shapeless
• Shaped
• None
• Weak Match
• Strong Match
• All Items
• Inventory
• Equipped
• All
• Left: Clear Slot
• Weak
• Item must have all required NBTs but can have extra.
• Strong
• Item NBT must match exactly.
• No NBT data is checked for crafting.
• Enabled
• Output will have specified NBT.
• Disabled
• Output will be pure vanilla item.

Primary configuration/data paths:

• config/kineticcore/datapack/data/contentstudio/recipe_bundle.json

Loot Editor is the visual loot-table editing module for this project. It edits server-loaded loot tables for entities, blocks and containers and stores custom overrides in a dedicated configuration file.

• Entity loot-table editor.
• Block loot-table editor.
• Chest/container loot-table editor.
• Visual loot pool and entry management.
• Rolls, quantities, weights and conditional loot data.
• Runtime override application to server loot tables.
• Global chest append rules.
• Global chest item-removal rules.
• Loot-table exclusion list for global chest rules.
• Server-authoritative save and reload flow.

config/kineticcore/loot_overrides.json

• Override Mode
• Append Mode
• Match Rule
• Item ID
• NBT Only
• Fuzzy NBT
• Exact NBT
• ID Match
• Match the item ID only and ignore NBT.
• Match the same item ID only when the generated stack has any NBT.
• Match the same item ID when its NBT contains all configured NBT conditions.
• Match the same item ID only when its full NBT exactly equals the configured NBT.
• Match: %s
• NBT condition saved

Primary configuration/data paths:

• config/kineticcore/loot_overrides.json

Trade Editor is the villager behavior optimization and trade-management module for this project. It reduces unnecessary AI work in dense trading halls while providing configurable follow behavior, trade-level protection, and a visual trade editor for villagers and wandering traders.

• Configurable villager AI check interval.
• Trapped-villager detection to stop pointless pathfinding.
• Minimal merchant updates preserved during trade level-up timers.
• Item-based villager following.
• Visual follow-item editor.
• Profession- and level-based villager trade editor.
• Wandering trader support.
• Add, replace-level, replace-all, and disable-level trade modes.
• Configurable offer count per profession level.
• Enable/disable and weight controls for vanilla trades.
• Full custom-offer parameters including two inputs, output, NBT, uses, XP, multipliers, demand, special price, restock, and weight.
• Server-authoritative persistence and runtime trade-pool publication.

config/kineticcore/villager.toml

• Add
• Disabled
• Replace
• A Input 1
• B Input 2
• Reward
• Clear

Primary configuration/data paths:

• config/kineticcore/villager.toml

Tooltip Editor is the visual item-tooltip editor for this project. It provides an in-game editor for KubeJS tooltip rules so pack authors can select items, edit text, and configure display conditions without manually maintaining the whole script.

The server validates the submitted rule database and generates kubejs/client_scripts/tooltipadd.js.

• Central overview of configured items.
• Search by item ID or localized name.
• Append and overwrite modes.
• Target-line selection for overwrite rules.
• No-key, Shift, Alt, and Shift+Alt conditions.
• Multiple rules per item.
• Ctrl + left-drag rule reordering.
• Minecraft § formatting codes.
• Item-level configuration removal.
• Server-side validation of IDs, modes, line numbers, key conditions, limits, and text.
• Server-authoritative script persistence.
• Safer temporary-file replacement when writing the generated script.

kubejs/client_scripts/tooltipadd.js

The generated script also acts as the rule database that Tooltip Editor reads back into its editor.

• Overwrite
• Append
• Delete this rule

• Minecraft: 1.20.1
• Java: 17
• ForgeGradle: 6.0.24
• Gradle: the project is pinned to the 8.1.1 Wrapper; do not import it with Gradle 9 directly.
• Local development JARs are controlled by local_libs_dir and can be overridden in gradle.properties or with a project property.
• Typical build command: gradlew.bat build on Windows or ./gradlew build on Linux/macOS.
• Development and release artifacts use contentstudio as the current project identifier.