DuckShell NPCs

DuckShell is not only a spawn utility. It is the system that makes NPC presence feel planned. Shell types define identity, patrols control movement, spawners decide when and where encounters appear, and the AI layer keeps those parts reacting like they belong to the same world.

That gives server owners a lot more freedom. You can build combat-heavy events, passive world atmosphere, guarded compounds, or live patrol routes without replacing the platform every time the design gets more ambitious.

DuckShell gives you a readable first-boot surface: config.yml for global rules, patrols.yml for routes, and spawners.yml for how encounters actually enter the world.

plugins/
  DuckShell/
    config.yml
    patrols.yml
    spawners.yml

The best first milestone is small. Spawn one shell type, bind it to one patrol or fixed point, and prove one spawner before you try to build a whole compound. Once that simple loop is healthy, the rest of the encounter stack becomes much easier to trust.

spawners:
  southern_proxy:
    shell_type: fcore_southern_proxy_passive
    patrol: perimeter_loop
    respawn_seconds: 45

Shell types define identity and AI overrides. Patrols define movement. Spawners decide when those shells appear and how the world stays populated. The AI Director sits above that structure to keep the broader runtime manageable.

That split is what allows the plugin to scale. A shell definition can be reused by several spawners. A patrol route can support different shell types. An operator can tune global combat rules without reauthoring every NPC one by one.

The live feature surface spans shell types, patrol editing, spawner workflows, Duck Shot combat behavior, presentation layers, nameplates, dialogue, hints, cover logic, no-line-of-sight behavior, and operator-facing debug routes.

That makes DuckShell useful for more than one server genre. A combat-heavy server can build squads and defended spaces. A worldbuilding server can use shell types, dialogue, and presentation without touching the more aggressive combat lanes.

The plugin keeps global rules in the AI Director and file map while preserving room for per-shell overrides. That is a healthier model for live servers than forcing every behavior change through every NPC template individually.

It also helps when troubleshooting. You can inspect patrols, spawners, AI behavior, and combat bridges as separate lanes, which makes it much easier to find the real problem when an encounter feels wrong.

A strong gallery should show one active encounter, one operator or patrol surface, and one finished in-world scene where the NPCs feel like part of the environment rather than a test spawn.

That mix shows buyers exactly why the plugin matters: it looks good in the world and it gives admins enough control to keep it healthy.