MAKE YOUR OWN SOUL

THE PACK

my_pack/
  pack.mcmeta
  pack.png
  data/<your_namespace>/soulverse/human_soul/<soul_id>.json

The data pack template is a pack to copy. The SOUL's id is <your_namespace>:<soul_id> (the file name).

pack.mcmeta

{
	"pack": {
		"description": "What the pack adds, in a line or two.",
		"min_format": 121,
		"max_format": 121
	}
}

121 is the data pack format of Minecraft 26.3 (pack_version.data_major in the game's version.json).

YOUR SOUL

The SOUL itself is one file, data/<your_namespace>/soulverse/human_soul/<soul_id>.json. It starts with its name, and each step below adds to it (or let the Data Pack Generator write yours).

ITS COLOUR AND PLACE

Colours that are too close to another SOUL are hard to tell apart on a heart, in chat and on the locator: keep yours clearly apart from the SOULs nearest it in colour, as the fourteen Additional Souls are kept apart from each other and from the original seven. Very dark colours are hard to see on dark menus: keep them above about 45% brightness.

Every SOUL, the base seven and Additional Souls alike, stands round the colour wheel, from red through orange, yellow, green, cyan, blue and purple to pink, 5 apart, so the lists and the ring in character creation run as one rainbow:

Give yours a number between the two SOULs nearest it in colour (one between Bravery's orange and Confidence's cream: 12), or 105 or more to put it after them all.

ITS QUIRKS

Give it quirks with "quirks": every player with your SOUL has them.

An id this version doesn't know is ignored. A server can switch each quirk off on the Server tab (Quirks).

A SOUND OF ITS OWN

Optional: the sound played when your SOUL is picked in character creation.

my_sound_pack/
  pack.mcmeta
  assets/mysouls/sounds.json
  assets/mysouls/sounds/soul/select_hopeful.ogg

1. In a resource pack, assets/<namespace>/sounds.json defines the event and points at an Ogg file: "soul.select.hopeful": { "sounds": ["mysouls:soul/select_hopeful"] }, the file being assets/mysouls/sounds/soul/select_hopeful.ogg (mono Ogg Vorbis, a second or less is best). The sound pack template is a pack to copy.
2. In the SOUL's JSON: "select_sound": "mysouls:soul.select.hopeful".

{
	"soul.select.hopeful": { "sounds": ["mysouls:soul/select_hopeful"] }
}

{
	"pack": {
		"description": "The sounds of My SOULs.",
		"min_format": 97,
		"max_format": 97
	}
}

The player needs the resource pack (a server can offer it with resource-pack= in server.properties). Without it the SOUL still works, just silently. The player's "SOUL sounds" setting turns these off like the others. The sounds of Additional Souls need no resource pack: they are part of the mod itself, so they are always there.

ITS PRIORITY

Optional, 0 by default: "priority" only matters when two packs have a SOUL with the same id (the same namespace and file name), and then the higher one is used. Soulverse's own are 0. With it, the file is whole.

PUT IT IN A WORLD

• In a new world: Data Packs on the Create World screen, move the pack to the right.
• In a world that exists: /datapack enable "file/my_pack" (a folder or zip in the world's datapacks/ folder).
• A dedicated server can also switch Additional Souls on in the SV menu (Server tab, Expansions) or soulverse-server.json ("datapacks": { "additional_souls": true }); it is read when the server starts, so it needs a restart.
• A server's SV menu lists the new SOULs on the Souls page; each can be set to enabled, unavailable, hidden or disabled there.
• A mod can ship the pack inside its jar (resourcepacks/<name>/ with the files above) and register it with Fabric's ResourceLoader.registerBuiltinPack(...); it is then in the datapack list, off until switched on, like Additional Souls (Soulverse.registerBuiltinPack). The menus' heart colours find SOULs in data/ and in resourcepacks/*/data/ of every mod.

GOOD TO KNOW