GUID: themorningstar.enemytestspawner

The dropdown comes from a Harmony postfix on REPOLib.Modules.Enemies.RegisterEnemies. It binds the Enemy config entry after REPOLib finishes registering, using an AcceptableValueList<string> built from Enemies.AllEnemies and Enemies.RegisteredEnemies, which REPOConfig renders as a cycle selector. If the hook fails or the list is empty, it binds a plain text field and matches input as a substring.

The spawn path runs in Update into Spawn, reading all config live:

1. Enum.TryParse on SpawnKey, falling back to Insert on a typo.
2. Gate on SemiFunc.IsMasterClientOrSingleplayer(). Clients get a log line, not a spawn.
3. Look up the EnemySetup in EnemyDirector.instance's enemiesDifficulty1/2/3 pools by exact name, then substring. No match logs every available enemy name.
4. Spawn every prefab in setup.spawnObjects at player + forward * SpawnDistance + 0.5 up, rotated to face you. Multiplayer goes through PhotonNetwork.InstantiateRoomObject, singleplayer through a plain Instantiate.

After spawning it logs a two-pass component dump at 0.3s and 2.5s: every Enemy* and PhotonView component with its enabled and active state, plus a count of missing-script components. When a modded enemy spawns but stands still, the dump shows which AI component is disabled or missing.

It searches the difficulty pools, not the registration list. An enemy that registered but never landed in a pool is not found, and the available-enemy log line then shows what is actually spawnable. It spawns the enemy raw. The director does not know it exists, so there is no vanilla pacing around it.