Nautilus Studio - Packs Editor IDE

📖 About 📖

Nautilus Studio is an in-game data and resource pack workbench. Instead of hand-writing JSON and guessing at the right fields, it opens a full editor alongside the game: pick a file, fill in a generated form, hit reload, and the change appears in the running world.

The forms are built automatically from the game's own content definitions, so it works with modded content as well as vanilla.

🖼️ Media 🖼️

!(https://raw.githubusercontent.com/MehVahdJukaar/mod_pages/master/assets/media/packs_editor.png)

📦 Features 📦

### What It Can Edit

• Worldgen: configured and placed features, carvers, biomes, noise settings, density functions, world presets
• Structures: structures, structure sets, jigsaw pools
• Loot and Predicates: loot tables, item modifiers, predicates
• Recipes and Advancements
• Enchantments
• World and Dimension: dimensions, dimension types
• Mob Variants, Decoration and Trims, Items and Sound, and more
• Anything a mod registers. [Polytone](https://modrinth.com/mod/polytone) registers its colormaps, particle effects and custom models, for example
• Any custom codec, pointed at by class name, even for content the editor has never seen
• Anything it cannot parse falls back to a live-validated raw JSON editor with syntax highlighting

### Using It

• Join a world first: the editor needs live registries to build its forms and to reload
• Open it from the Mod Menu entry on Fabric, or the config-screen button in the mods list on NeoForge
• The workbench opens in its own window beside the game
• Hit reload to push changes into the running world

> Nautilus Studio runs best on Fabric. On NeoForge the editor window can occasionally fail to open, due to Java's headless-window restrictions.

🛠️ For Mod Developers 🛠️

For most things the mod should just work. However if you want proper compat here is what you can do:

To register your codec so they appear by default in the editor you can register them like such:

```java NautilusStudioApi.register( "My Mod", // group name, shown next to "Minecraft" "Widget Layout", // this content type's label MY_CODEC, // your per-file Codec (the DIRECT_CODEC) Side. CLIENT_RESOURCES, // CLIENT_RESOURCES (assets/) or SERVER_DATA (data/) "mymod/widgets" // folder the files live in ); ```

To get nicer widgets, a color picker, a slider, a dropdown for a sum type, build your codec as a [CodecUI](https://github.com/MehVahdJukaar/codecui) `SchemaCodec` and pass that instead. It stays a real `Codec` with the same wire format. Anything CodecUI can't read falls back to a validated raw-JSON editor, so registering is always safe.

Simply add these lines (jar-in-jar, so CodecUI ships inside your mod) and replace your `Codec` calls with `SchemaCodec` calls, following the API in that class:

```gradle repositories { maven { url "https://registry.somethingcatchy.net/repository/maven-public/" } }

dependencies { // Fabric (Loom) modImplementation "net.mehvahdjukaar:codecui-fabric:1. 21. 11-0. 4. 0" include "net.mehvahdjukaar:codecui-fabric:1. 21. 11-0. 4. 0"

// NeoForge (ModDevGradle) implementation "net.mehvahdjukaar:codecui-neoforge:1. 21. 11-0. 4. 0" jarJar "net.mehvahdjukaar:codecui-neoforge:1. 21. 11-0. 4. 0" } ```

See the (https://github.com/MehVahdJukaar/codecui) for the full DSL and examples.

❓ F. A. Q. ❓

Q: Is this client-side only?

A: Yes. The editor is a client tool: it edits pack files on disk and reloads your client. You don't need it on a server.

Q: Do players need this to use my pack/mod?

A: No. Nautilus Studio is a creation tool. The packs you make with it are plain vanilla data/resource packs that wor