Inkorporated
Custom tattoo framework. Mods ship tattoo packs (a PNG folder + manifest, or via the API) and Inkorporated adds them to the tattoo shop - rendered, saved and co-op-synced like vanilla.
About this mod Author’s original text
Inkorporated - Custom Tattoos for Schedule I
🛟 Need help or found a bug? Get support at support.doodesch.de/inkorporated.
The tattoo framework for Schedule I. Mods add their own PNG tattoos to the in-game tattoo shop -
via a drop-in pack folder or an API - and the game treats them like vanilla: they render on the
avatar, persist in saves and sync in co-op. On its own this mod adds no tattoos; it's the dependency
tattoo packs are built on.
What it does
- Adds custom tattoos to the tattoo shop under their placement category (Chest, Left/Right Arm, Face).
- Real avatar layers via the game's own pipeline - they render, save and sync in multiplayer like
built-in tattoos (everyone needs the same mod + pack to see them; others just don't render them).
- Tattoo packs are plain folders of PNGs + a tiny manifest.json - no code required. Code mods can also
register tattoos through the API.
Requirements
- Schedule I (IL2CPP) with MelonLoader 0.7.3+.
- S1API (pulled in as a dependency).
Using it
Install Inkorporated plus any tattoo pack that depends on it; the new tattoos show up in the tattoo shop.
Packs live in UserData/Inkorporated/Packs//.
Want a quick look at the format (and a few free tattoos)? Set LoadExamplePack to true (in the Mod
Manager & Phone App UI or UserData/MelonPreferences.cfg under Inkorporated_01_Main) and restart - a
bundled example pack with a working folder/manifest template is dropped into Packs/Examples to copy.
Making a pack
A manifest.json lists tattoos with a placement (chest | leftarm | rightarm | face), an optional
price, and a transparent PNG. The design's opaque pixels must sit at the correct UV region of that body
part (a tattoo is a full skin-texture layer, not a centered sticker - so you can do anything from a small
mark to a full sleeve). See the example pack and the full guide on
GitHub.
Settings
LoadExamplePack (default false) - drop the bundled example pack on disk as a template. Editable in UserData/MelonPreferences.cfg.
License
MIT. See the included LICENSE.md.
Install & use Install: follow the bundled instructions
- Unzip the archive from playbuff and read the bundled readme / instructions first.
- Most mods rely on the game's mod loader — the usual route is a community mod manager (such as r2modman): pick this game, install, and it handles the loader and dependencies.
- For a manual install, put the mod files into the matching Mod / plugins folder inside the game directory.
- Launch the game to confirm it loaded; mods with listed dependencies need those installed as well.
Install locations vary a lot between mods — the bundled readme is the most reliable guide.
Install these first, or the mod will not work: