NeoOrigins Admin Config Reference

Server-operator policy knobs live in the TOML file config/neoorigins/admin.toml: the command-power blacklist, command access, per-power dimension restrictions, unique-origin layers, the global taming/scare entity blacklist, compat origin filtering and debug flags.

This is a COMMON config, not a server config: it loads early enough to be readable during the boot-time datapack reload, it is not synced to clients, and there is no per-world <world>/serverconfig/ override (unlike content.toml). Every rule here is enforced server-side.

The file is created with defaults on first launch. Edit it while the game/server is closed.

Config split (2.2.2). admin.toml is one of four config files. Its siblings are content.toml (SERVER: synced, per-world overridable), gameplay.toml (COMMON: gameplay tuning) and power_overrides.toml (COMMON: per-power stat overrides). This doc covers admin.toml only.

Minecraft 26.3. NeoForge 26.3 calls COMMON configs LOCAL. Nothing else changes for admin.toml: it still has no per-world override. Only content.toml’s per-world copy moves, to <world>/syncedconfig/; see CONTENT_CONFIG.md.

Debug flags

These live at the top of the file, outside any section (they migrate 1:1 from the legacy neoorigins-common.toml, where they were also top-level).

Option	Type	Default	Description
debug_power_loading	bool	false	Log per-namespace power counts, and the origin ids loaded per namespace, after each data reload. Useful for addon and datapack authors debugging load issues.
debug_compat_actions	bool	false	Send in-game chat feedback when a compat power action resolves to no-op (unsupported action type). Useful for pack authors debugging why their imported powers aren’t working.
debug_hud	bool	false	Diagnostic logging for the ability HUD cluster and flight-ability syncing: logs hover-state changes on the cooldown cluster (client) and every server-side grant/clear/accept of flight abilities. One line per state change, not per tick. Leave off in normal play.

[dimension_restrictions]: per-power dimension deny lists

Powers listed here are suppressed while the player is in the specified dimension(s).

Behaviour	Detail
Key	rules, a list of strings. Default [].
Format	"<power_id> = <dimension1>, <dimension2>, ..."
Example	"neoorigins:elytrian_flight = minecraft:the_nether, minecraft:the_end"
Validation	Each rule must contain an =, and the power id before it must contain a :. Invalid rules are rejected by the config loader.
Reloads	The parsed rule set is cached and rebuilt whenever the loaded list’s contents change (checked on each lookup), so a config file reload takes effect without a restart.

[dimension_restrictions]
    rules = ["neoorigins:elytrian_flight = minecraft:the_nether, minecraft:the_end"]

unique_origin_layers: one player per origin

A top-level list (no section) of layer IDs in which each origin can be claimed by only one player on the server.

Behaviour	Detail
Key	unique_origin_layers, a list of layer IDs. Default [].
Scope	Per-layer: only the layer IDs listed are affected. Example: ["neoorigins:origin"].
Effect	Once a player picks an origin in a listed layer, no one else can pick that same origin there.
Release	A claim is released when its holder’s origin on that layer changes (an upgrade, /neoorigins set, or another mod through the API) or the layer is cleared, and by /neoorigins unlock, an Orb of Origin re-pick, /neoorigins reset, or an every_death random reroll.
Picker	An origin another player holds stays listed but is marked claimed, with the holder’s name. Confirm is disabled on it and the Random button skips it. The server refuses it either way.
Random assignment	random_assignment never hands out an origin someone else holds, and claims the one it hands out.
Upgrades	An origin’s upgrades entry does not switch a player to an origin another player holds; the upgrade and its announcement are skipped. An upgrade into an unclaimed origin claims it.
Bypass	Operators in creative mode (and /neoorigins set) bypass the lock and take over the claim.

[compat_filtering]: hide broken addon origins

Option	Type	Default	Range	Description
min_power_ratio	double	0.5	0.0 – 1.0	Origins from addon mods are hidden if fewer than this fraction of their powers loaded successfully. Default 0.5: origins with less than 50% of powers working are hidden. Set to 0.0 to show all origins regardless.

[commands]: command access tuning

Option	Type	Default	Description
public_origin_get	bool	true	Allow non-OP players to run /neoorigins get <player> to look up another player’s origin. Operators (permission level 2) can always run it regardless of this setting. Set to false to make origins visible only to staff.

[command_powers]: the command-power blacklist

Datapack powers can run arbitrary server commands (the command / execute_command actions, the raycast command_along_ray / command_at_hit extensions, and the command condition). Without a guard, a pack could ship /op @s and silently escalate any player to operator. This list names command roots that are refused at execution time regardless of the power’s permission level: a blocked command is refused and logged instead of run.

A command the game cannot parse is also logged, once for each combination of power, site and command text, carrying the game’s own reason for refusing it. Powers run their commands with output suppressed, so up to 2.2.29 a command with a syntax error produced no chat message and no log line: the power simply appeared to do nothing.

Behaviour	Detail
Key	command_power_blacklist, a list of command roots.
Default	op, deop, ban, ban-ip, pardon, pardon-ip, kick, whitelist, stop, save-all, save-off, save-on, setidletimeout, debug, perf, datapack, reload
Matching	Case-insensitive on the effective command root. execute ... run X is unwrapped so X is what gets checked: a blacklisted command can’t be smuggled behind an execute chain.
Format	List the root only, no slash.

[entity_exclusions]: taming and scare blacklist

Global entity exclusions for the mob-control power family: tame_mob, scare_entities and mobs_ignore_player. Entities listed here can never be tamed, scared, or made to ignore a player by any power, on top of the hardcoded boss-tier exclusion and any per-power entity_blacklist. The same check also exempts listed entities from mobs_target_player, attract_mobs and the feared_by flee sweep of entity_group.

Behaviour	Detail
Key	tame_scare_entity_blacklist, a list. Default [].
Format	Entity ids (e.g. "minecraft:elder_guardian") or entity-type tags (e.g. "#mymod:untameable").
Always excluded	The Warden, Ender Dragon and Wither are hardcoded exclusions and need not be listed.

Source of truth: config/AdminConfig.java.