SE Frameworks — building on top of MES, WeaponCore, Mod Adjuster, and friends
Each framework has its own conventions, SBC extensions, and load-order requirements. Load only the reference for the framework in play.
Pick the framework
| Framework | Purpose | Reference |
|---|---|---|
| Mod Adjuster | Non-destructive balance patches against any mod or vanilla; runs as a session component that applies XML patches | references/mod-adjuster.md |
| MES — Modular Encounters System | NPC ship/vehicle encounter spawns | references/mes.md |
| AI Enabled | NPC characters, creatures, crew | references/ai-enabled.md |
| WeaponCore | Custom weapons with WC-specific SBC | references/weaponcore.md |
| Animation Engine | Custom block animations, triggers, subparts | references/animation-engine.md |
| Scope Framework | Weapon scope / iron-sights for handheld weapons | references/scope-framework.md |
| Tank Tracks | Tracked vehicle movement | references/tank-tracks.md |
| Vanilla+ Framework | Advanced projectile / turret behaviors on vanilla weapons (server-side); Workshop listing is unlisted | references/vanilla-plus.md |
Cross-cutting notes
- Framework Workshop IDs live in the mod catalogue (../se-core/MOD_CATALOGUE.template.md). If the user's Workshop dir is mounted, reference by ID.
- Load order matters. Framework mods usually have a required load position relative to their child mods; each reference doc calls this out.
- Child mod pattern. Most of these frameworks have a "child mod" convention — a small mod that adds definitions the framework consumes.
references/*.mdcovers the child-mod structure per framework. - Mod Adjuster xsi:type — Mod Adjuster patches use the stripped type name (no
MyObjectBuilder_prefix), unlike vanilla SBC. Easy trap.