Troubleshooting.md

Here are some of the most common reasons you may not see encounters when you expect to, or why some encounters might not work properly:

• Planetary Installations Spawn Too High / Too Low From The Ground: This issue occurs when you're on a planet that is too far from the game world center (0,0,0). The effects don't usually become noticeable until after about 7500km-10000km. The reason this happens is because the vector calculations the game uses with voxels start to become less accurate at longer distances (this is a limitation of the game engine). A common cause of this issue is using worlds generated using the SEWorldGenPlugin, which can place planets at extreme distances from the center of the game world.

• Ships Falling or Not Behaving Properly While Using Infestation Enabled or Crew Enabled mods: These mods add NPC characters to seats, or add spiders that infest ships. However, they can also interfere with the regular operation of NPC Ship behaviors because they will sometimes (intentionally) break the Remote Control block that controls all the custom behavior so alternative behavior can be used (eg infestation). Please refer to the settings on those individual mods to address this.

• NPC Turrets Not Shooting: This is more common on servers, but can also happen in single player as well. There is a known bug affecting turrets and their ability to acquire a target. MES doesn't manage how NPC turrets work, it only puts ammo in the block and lets the vanilla logic do the rest. As a result, I cannot fix anything related to this on my end. One possible workaround is to use WeaponCore and its Vanilla Weapons Replacement mod, since it uses its own, not broken, targeting logic.

• Dedicated Server and Selective Physics Updates: If you decide to use the Selective Physics Updates option introduced in game version 1.196, you must use a SyncDistance no lower than 10000. If the SyncDistance is lower, then the Modular Encounters Systems will be disabled. The reason for this harsh requirement is because most NPC grids operate outside of the default SyncDistance of 3000, and this server option stops their movement (physics) unless a player is within the SyncDistance range. There is no reasonable way to work around this other than increasing the SyncDistance.

• Reset Configurations: Sometimes I will update the default values in a SpawnType configuration file, however these changes will not automatically replace existing configurations in your existing saves. It's worth trying to reset your configuration files by either deleting them or using chat command /MES.Settings.ResetAll. If you've made changes to your configurations, you may want to backup those files before resetting them and testing with the fresh copies.

• NPCs Are Spawning With No Ownership: This is almost always the result of the NPC Faction being tampered with in some way. This can happen if an admin removes the founder from an NPC faction, if a player joins the NPC faction using admin controls, or if another script/plugin makes changes to the faction by adding/removing identities from it. None of the mods I curate make these sorts of changes. Unfortunately, I don't have an easy suggestion on how to correct many of these situations, since NPC factions are only generated once per world by the game. If you know how to edit the save file and undo any breaking changes, that is often the best way to handle it - otherwise you may have to create a new save to get NPCs spawning with correct ownership again.

• Check What Can Spawn In Your Vicinity: You can use a simple chat command to see what encounters are potentially eligible to spawm near you. The command is /MES.Info.GetEligibleSpawnsAtPosition. There is also a shorthand version of this command as well: /MES.GESAP. Depending on where you are and what mods you have loaded, it could just be an issue on being in an area where those mods cannot spawn encounters.

• Too Many Spawns: If you are playing in multiplayer, you may notice an increase in spawn activity. This is because each player is tied to their own spawning events. So if a bunch of players are all in one area, then a bunch of encounters can potentailly appear pretty quickly. To mitigate this, use the config to reduce the MaxShipsPerArea property of each encounter type to something that is more managable for your play style. The config files also control the time between spawns as well.

• Planetary Spawning: Planetary Cargo Ships will typically only spawn on full sized planets that have a rich atmosphere. If you are using a custom map with modded planets or planets that are too small in size, then the atmosphere required for spawning may not be enough and any spawn attempt will fail. For Planetary Installations, planets that have a rough surface will have less success in seeing installations appear - this is because the mod tries to find relatively flat areas to spawn these installations, so jagged and mountainous areas will likely not see many/any of these spawns.

• Planetary Cargo Ships Falling Out Of The Sky: This is almost always the result of other mods that cause changes to Thurster Balance, Fuel and Hydrogen Re-Balance, and Aerodynamic/Realistic thrust. Many planetary cargo ships are not designed to use these systems and may not work properly as a result.

• Critical Error In-Game Popup: These errors are often not a result of something wrong with the mod itself, but rather a result of Steam not downloading the mod properly. This can often be corrected by unsubscribing from the mod in question, waiting a little while, restarting steam, and then re-subscribing to the mod to force a new download.

• Encounter Specific Limitations: Some mods may use additional requirements that must be met before their encounters are able to spawn. These often include conditions such as Threat Score, PCU, Faction Reputation, and other conditions. These conditions are often listed on the mod pages of those encounters, so ensure you read the mod descriptions so that you understand the required conditions for their encounters.

• Ships/Drones Not Doing Anything: This is often because the drone encounters of a mod require the In-Game Scripts World Option to be enabled. When creating a new world, this option is typically OFF by default, so ensure you double check this to ensure it's ON.

• Too Many Active Encounters: If encounters are not spawning, it may be because there are too many active encounters in the world. Try removing some grids using the Admin Tools (Alt+F10).

• Current Game Version: I will often update the Modular Encounters Systems with new features as they are released with Base Game Major Updates. As a result, the framework is only compatible with the latest version of Space Engineers. If you attempt to run it in older versions, the scripts the framework uses to operate may not compile.

• Drones Spawning From Antennas: These are not spawned through the Modular Encounters Systems, so they may have other factors that need to be considered such as the Enable Drones world option being turned on, and the Pirate PCU limit not being exceeded. Also, because these are not spawned through the Spawner mod, they will not be eligible for prefab manipulations provided by NPC Weapon Upgrades or NPC Defense Shield Provider mods.

• Torch Concealment: Concealment Plugin for Torch has been known to cause issues with NPC grids on occasion. I am not familiar with the various settings that the plugin offers (I have not administrated a server in a very long time), but I believe there are options to exclude NPC grids from concealment. I recommend using that option if you run into conflict with the Modular Encounters mods. If issues persist, you may need to disable concealment to use this mod.

• Circular Reference in Game Log: This message can appear sometimes in your game log. It's something that often appears when mods use another mod as a dependency (many encounter mods use the framework). The message is harmless and can be ignored.

• Still Seeing Spawns After Removing The Framework: If you have removed the Modular Encounters Systems mod, but have left any mods that use it as a dependency, then it is likely those mods are causing it to continue loading. You would need to remove any mod using the framework as a dependency from your mod list.

Advanced Encounters Troubleshooting

If you are still not seeing any encounters after following the above advice, then you can try some of these advanced steps:

• Checking The Spawn Record: Using the chat command /MES.IGLSD.SpawnRecord will generate a report that gets saved to your clipboard. You can paste this report into a program like Notepad and see what the result of various spawn attempts have been, and where they may be failing.

• Enabling and Checking Debugs: If the above did not provide any useful answers, you should next try to enable some of the extended monitoring. Enter the chat commands /MES.SpawnDebug.Spawning.true and /MES.SpawnDebug.SpawnGroup.true. Continue to play the game for a while (maybe about 1 hour). If you do not want to wait for encounters to spawn naturally, then you can use the /MES.Spawn.ForceSpawnTimer.Value chat command (see This Page for info on what you can replace Value with). After the game has run for some time (or you've used the ForceSpawnTimer command), use the chat command /MES.IGLSD.Spawning to generate a report that saves to your clipboard. Paste into Notepad or another app and check for messages that may indicate where the Spawning is getting stuck. Below I will cover some of the more common scenarios.

• Message: Eligible SpawnGroup Count 0: If you get this message in the Spawn Report, then it usually means that there are currently no eligible encounters for the area you're currently in. You can get more details on this by entering the chat command /MES.IGLSD.SpawnGroup, pasting the result into Notepad, and seeing the provided reason that each SpawnGroup cannot spawn. This can be tricky to read at times because it prints a large list containing every SpawnGroup and why it can/can't spawn for EVERY spawn request. It's often better to start from the bottom and work upward to get the most recent data.

• Message: SpawnGroup Path/Placement Invalid: If you get this message in the Spawn Report, then it usually means that while there are potential SpawnGroups that can spawn, they are currently unable to because of the surrounding environment. This could be due to a number of factors such as Planetary Cargo Ship encounters not having sufficient Air Density to fly (ie, atmosphere too shallow at position), terrain being too coarse / ragged for proper Planetary Installation placement, and more. Many of these reasons are covered in better detail earlier in this troubleshooting guide.