Configuration Files

Configuration Files

Configuration files are created under the instance's config directory. Bundled defaults are copied only when a file does not already exist. Updating the mod does not overwrite customized files.

File	Purpose
config/scpadditions/modules.json	Gameplay and interface module switches.
config/scpinventory/scpinventory.json	Item routing, equipment effects, Status filters, Codex documents, and SCP-173 targets.
config/scpinventory/context_interactions.json	Block and entity prompt rules.
config/scpadditions/294drinks.json	SCP-294 matching and drink definitions.
config/scpadditions/914recipes.json	SCP-914 machine settings and main recipe list.
config/scpadditions/914recipes.d/*.json	Additional SCP-914 recipe fragments.
config/scpadditions/scp914_skins/*.png	SCP-914 1:1 skin pool.

Use /scpadditions reload after external manual edits. In-game saves reload their affected systems automatically.

Module switches

modules.json independently controls:

• SCP Inventory and remembered UI state;
• contextual interactions and Creative visibility;
• custom HUD;
• custom health, stamina, and survival movement;
• blinking;
• the world-entry sound;
• SCP-173 behavior;
• reduced SCP-012 visual effects;
• optional SCP-079 and roamer debug displays.

Disabling the custom HUD does not automatically disable stamina gameplay.

Natural spawning is controlled separately by the world gamerules 173spawn and 106spawn.

Current modules.json groups include:

Group	Important fields
audio	enter_sound_enabled
accessibility	reduce_scp_012_visual_effects
debug	show_scp_079_energy_hud, show_scp_079_decision_log_hud, show_scp_spawn_timers_hud

Missing groups are normalized to safe defaults when the file is loaded.

Inventory configuration

The principal sections of scpinventory.json are:

Section	Meaning
item_rules	Generic item routing. Explicit rules override automatic classification.
item_effects	Configurable item behavior such as NO_STAMINA and PROTECTED_EYES.
hidden_status_effects	Effects hidden from the Status panel without removing gameplay behavior.
codex_documents	Item-backed documents, unique NBT IDs, images, and text.
scp_173_targets	Entity IDs or #namespace:tag observer/target entries.

Generic item types include MISCELLANEOUS, HARMFUL, CONSUMABLE, USABLE, PLACEABLE, KEY, COIN, AMMO, HEAD, ACCESSORY, ACCESSORY_HAND, CHEST, LEGS, FEET, and WEAPON.

CODEX is internal and is not accepted as a generic item-rule type. Create documents through codex_documents.

SCP-714 protection and complete Hazmat Suit sealing are intrinsic behaviors of those items and do not require a manual item_effects rule.

Eye Sore, Lubricated Eye, and Bleeding are visible in the inventory and Conditions interfaces by default. They may still be hidden from the Status panel through hidden_status_effects. SCP-1176 Honeyed is an internal marker and remains hidden independently.

Multiplayer synchronization

The server's supported gameplay configuration is authoritative. On login and after supported saves, deletions, and reloads, the host synchronizes item rules and effects, hidden Status effects, Codex definitions, contextual interactions, entity interaction rules, and SCP-173 targets to connected clients.

Clients clear the synchronized snapshot on disconnect. Their local single-player files are not permanently replaced by the previous server's settings.

Codex assets

Packaged image and text fields use resource locations supplied by a mod or resource pack.

World-scoped imports are stored in:

<world>/scp_additions/codex_assets/images
<world>/scp_additions/codex_assets/texts

The JSON stores world_image and world_text safe relative keys. Supported imported images are PNG, JPG, and JPEG up to 2.5 MB and 4096×4096 pixels. Text is UTF-8.

Context interactions

The visual K editor is safer than manual editing. Important fields include:

• type: block or entity;
• id: registry ID;
• range and priority;
• icon and useItem;
• text.action, name mode, and visibility;
• local anchor position and optional world offset;
• click face and rotation mode;
• allowed input methods.

Restoring shipped defaults

To regenerate a default file:

1. close the game/server;
2. back up the customized file and its .bak;
3. delete only the file to regenerate;
4. start the same installed mod version again.

Do not delete an entire configuration directory unless every customization in it is disposable.