Mayhem Industries Encounter System Framework
Изображение 1 из 3. Материалы автора из Steam Workshop.
О материале
«Mayhem Industries Encounter System Framework» — материал мастерской Space Engineers. Моды, чертежи кораблей, скрипты и миры для Space Engineers. Для установки откройте оригинал в Steam Workshop, проверьте требования автора и подпишитесь. Совместимость с версией игры редакцией не проверена.
Описание автора
MIGN Encounter System
A standalone encounter framework for Space Engineers.
MIGN Encounter System handles encounter discovery, spawning, movement behaviors, hostile targeting, faction ownership, reinforcement triggers, announcements, GPS markers, cleanup and saved encounter state. Community content packs supply the ships and encounter definitions.
How to use
- Subscribe to MIGN Encounter System.
- Subscribe to one or more compatible MIGN encounter packs.
- Enable the framework and your selected packs in your world's Mods list.
- Load the world. The server discovers and validates enabled encounters automatically.
This framework contains no encounter ships. It needs an enabled content pack to spawn anything. The creator template's examples are disabled until configured.
Features
Spacecraft, planetary aircraft, surface buildings, defended outposts, salvage wrecks and conventional wheeled vehicles. Multi-prefab encounters, weighted selection, player limits, cooldowns and concurrency caps. Pack defaults, encounter settings, individual grid settings and server overrides. Attack, Patrol, Guard, Flee and Passive behavior. Capture protection, configurable retirement, detached salvage preservation, optional Scrap Beacon protection, persistent cooldowns and once-per-instance triggers. Admin commands and isolated pack validation errors.
Every spawn is anchored to a living player. Creators choose minimum/maximum spawn distances, a nearby encounter cap and counting radius. Optional exploration distance controls repeat automatic spawns of a site type. Server owners can override these settings. Caps include pending encounters and apply to affected nearby players; fleets and wheel subgrids count as one encounter group. A cap limits admission rather than guaranteeing an immediate number of spawns.
Ships use Space Engineers' Remote Control autopilot and their own configured weapons. Mobile ships need power, gyros, appropriate thrust and a functional Remote Control. This framework does not supply ammunition, fuel or a custom weapons driver.
Buildings use sampled terrain placement and configurable foundation depth/slope limits. Wheeled vehicles need a functional controller, attached suspensions and power; the framework supplies steering, propulsion, braking and local terrain/obstacle detours. Ground driving requires vehicle-specific testing and is not a global road planner. Scrap Beacon protection is optional and does not alter vanilla trash-removal rules.
Server administrators
Enter /mign help as an Admin or Owner. Useful commands include /mign status, /mign list, /mign active, /mign errors, /mign pause and /mign reload.
The server creates MIGN-ServerConfig.xml inside this world's mod-scoped Storage folder. Override global settings, individual encounters or specific grids there. Existing encounters keep their saved settings; reload affects future spawns. Restart after changing prefab definitions or the world's loaded mod list.
Creators
Use the separate MIGN Encounter Creator Template to build a data-only content pack. Supply Data/Prefabs/*.sbc and MIGNEncounters/EncounterPack.xml at your mod root. Do not copy framework scripts into your pack. Add MIGN Encounter System as a Required Item when publishing.
Compatibility
No MES, RivalAI or WeaponCore dependency. Packs can require other block mods; check each pack's description. Dedicated-server encounter logic runs on the server. Existing factions retain their relations. Newly created encounter factions can explicitly initialize hostile relations with FactionHostile.
Version 1.4.1 / pack schema 1. Includes the optional Rich HUD weight editor, explicit prefab block requirements and paginated encounter listings. Source compilation against the installed game, policy/serialization tests, manifest checks and prefab preservation checks passed. Gameplay, GUI and multiplayer still require in-game acceptance on the chosen world.
Threat levels, factions and ship names
Planetary encounters stay random within configured player distances and nearby caps. Automatic space encounters use a player threat tier from nearby owned/controlled grids and working weapons. Creators rate encounters from 1 to 5; matching randomly selects the player's tier or lower tiers, never above it. Server owners can tune score thresholds and the lower-tier chance, or disable matching.
Set FactionTag, FactionName and CreateFaction to create a named NPC faction; FactionHostile controls initial relations. Set GridName for an optional main-grid name. By default beacons, radio antennas and GPS show the actual ship/grid name. See THREAT-FACTIONS-NAMES.md in the documentation. Admins can inspect their score with /mign threat.
Как установить и запустить
Откройте оригинальную страницу в Steam Workshop, проверьте версию игры, зависимости и порядок загрузки в описании автора. Нажмите «Подписаться» и дождитесь загрузки Steam. Включите материал в меню модификаций или контента игры, если это требуется. Совместимость и запуск редакцией не проверены.