This very minor release just fixes some position issues in Blackout maps.

For detailed documentation, visit the Mission Control Website.

NOTE: This release is only to officially release out the two hotfix files that were in the MC discord for over half a year. If you already have those there is no need for you to download this release.

#🐛 Bug Fixes

• Blackout: Badlands Map - Phase 2 Event 2 invading lance units spawn on top of each other when Random Spawns is off
• Blackout: Badlands Map - Player spawns lance units spawn on top of each other with Random Spawns off
• Blackout: Lowlands Map - Phase 2 Event 2 invading lance units spawn on top of each other when Random Spawns is off

#🆙 Upgrade Instructions

This update is just a mod.json and two contractTypeBuild files update.

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • mod.json
• Copy and overwrite:
  • contractTypeBuilds/Blackout/story2_badlandsparched.jsonc
  • contractTypeBuilds/Blackout/story7_lowlandsspring.jsonc

NOTE: There was no dll rebuild for this release so the version on that still says v1.5.1. This is not an issue.

Hey guys!

Today I’ve released v1.4 of ConverseTek.

For those of you who don’t know what ConverseTek is, it’s the tool I developed for creating and editing BT dropship conversations (1-on-1s with the crew and conference room) and released in Summer 2018.

You can grab the new release from the Github ConverseTek v1.4 Release.

As part of this update I rewrote / ported the project to Typescript and updated a lot of the badly outdated dependencies. In the process I’ve improved lots of areas of code since I was forced to touch almost every single file. This makes the project easier to work with so it makes it easier to improve.

Before I get onto the new features and improvements I need to mention the elephant in the room / the outstanding big issue and how it’s now been fixed.

#Corrupted Conversations / Bad Data (The Ugly Big Elephant)

Ever since CT was created it had a risk of corrupting a conversation file - sometimes in obvious ways and other times in very subtle ways. Any modder who has used it would probably scream in rage any time they realised this happened (and it was particularly sneaky as it would always look fine in CT - just break in BattleTech itself). This bug was due to an original assumption I made when I originally developed the tool and one I only realised was wrong when I was stopping development on the tool. Fast forward to a year and a half after the last release and this issue is now fixed in v1.4 (it should have been fixed years ago but that's life). An important note to modders who might still have corrupted conversation files from previous CT usage - v1.4 can fix those for you if you open it up and re-save them.

It also fixes all other issues around bad conversation data, for example, old text showing up in copied / moved nodes even after the copied text was changed in CT.

With that said, onto the nice new features.

#Quicklinks / Favourites

The user experience of opening up your workspace folder that contained conversations was horrible. It started you off in your root drive view and didn’t help you save time to navigate back to your conversations. If the user’s conversations were deep in a drive then that meant a lot of clicking. Really annoying stuff.

Now you have some typical quick links that you’d expect (Desktop, My Documents, My Computer, Favourites). You can also right-click any directory and favourite it. This adds a blue favourite icon to the directory navigator that you can click to go straight to.

#Dialogue Tree Zoom

Large conversations means a ton of prompt nodes (blue) and response nodes (yellow). When it gets so large, like in vanilla conversations, it gets incredibly difficult to figure out where all the conversation nodes are that you’re trying to look at.

You now can use CTRL + mouse wheel to zoom in and out to give yourself a better feel for the conversation (or it can help people who need the text a bit bigger to read).

#Node Details Drag Expand

Actions and Conditions are vital to making good conversations, yet, the viewing area for those is too small compared to the data-dense functionality often needing to be displayed.

You can now drag and expand the node details area to give yourself a lot more space for actions / conditions / node details and writing dialogue. This often will give users the ability to view all (or most) of the actions and conditions on a node (or reduce the scrolling to a minimum).

#Delete Conversation

You can now delete conversations from within CT. Pretty simple but useful.

#Re-enabled Dragging Response Nodes to Other Nodes

In earlier releases of CT you were able to drag and drop response (yellow) nodes from their parent prompt (blue) node to anywhere else in the conversation. Due to the realisation this caused some nasty bugs the feature was limited to allowing only dragging/reordering within the same prompt node.

Since all the conversation corruption bugs are fixed I re-enabled this feature - so you can now move response nodes to other prompt nodes.

#Other fixes and changes

There are a good few other fixes and changes but I’ll leave this post here. If you’re interested in the full changelog check out the ConverseTek github release page and the github milestone for v1.4

#In Closing

Tools for the community often go overlooked but are critical for the health of mods and modpacks. This update took me a month of my free time (developing on it almost every single day when I had spare time during that month) so I honestly hope you enjoy and appreciate the new improvements. Don’t be quiet and please let me know what you think. It was a good update to work on.

Thanks guys.

This release fixes a single bug mentioned below that caused an infinite spinner when returning from a contract that didn't have MC running on it.

The full release diff can be at the v1.5.1 pull request.

#🐛 Bug Fixes

• Data Cleanup: RestoreFromCopy cleanup approach caused infinite spinner when MC was not allowed to run
  • When Mission Control wasn't running for a contract the data backup wasn't running. When the contract ended the data backup caused an infinite spinner because there was no data to restore and MC errored.

#🆙 Upgrade Instructions

This update is just a dll and mod.json update.

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json

This release introduces a lot of new features and fixes some important bugs. It adds a lot more content for the existing custom contract types, adds a dialogue system that works with the combat dialogue for much more control and allows player pilots to talk in contracts. One of the main reasons for this release is to prepare the contract type build formats for the upcoming Mission Control Designer.

All website documentation has been updated to reflect all the new additions and changes so check there for specifics.

The full release diff can be at the v1.5.0 pull request.

#❗ Custom Contract Build Format Upgrade

As the Mission Control Designer is in a functional state I've been testing the Designer saving out the existing custom contract types (Duels & Blackout). For various reasons related to the Designer the existing custom contract type build files (files that are located under MissionControl/contractTypeBuilds) require an upgrade.

The upgrade is critical and must be done. - See the below Upgrade instructions on the process

#🚀 Features

• Blackout: Added 3 more contracts
  • Absent Witness
  • Prepared Grounds (written by Vantas Strider)
  • A Minor Royal Pain
• Blackout: Added to 3 new maps
  • Tyrlon (Highlands Fall biome)
  • Central Mountain (Desert Parched biome)
  • Lost World (Jungle Tropical biome)
• Solo Duel: Added to 5 new maps
  • Big Loch (Highlands Spring biome)
  • Red City (Martian Vacuum biome)
  • Tide Bay (Jungle Tropical biome)
  • City Centre (Urban HighTech biome)
  • Taiga River (Trunda Frozen biome)
• Duo Duel: Added to 5 new maps
  • Big Loch (Highlands Spring biome)
  • Red City (Martian Vacuum biome)
  • Tide Bay (Jungle Tropical biome)
  • City Centre (Urban HighTech biome)
  • Taiga River (Trunda Frozen biome)
• Dialogue: Added a dialogue system on top of the contract dialogue system for Combat
• Dialogue: Player Pilots Can Talk in Contracts
  • Anyone interacting with contract dialogue CastDefs / selectedCastDefId can now select Player lance pilots to talk
  • Provided manual (castDef_TeamPilot_1), true random (castDef_TeamPilot_Random) and bound random selection of Player lance pilots (castDef_TeamPilot_Random_1 or castDef_TeamPilot_Random_BoredPilot)
• Dialogue: Commander can be used as a CastDef regardless of if dropped in the Player lance
  • Can be used if the Commander is on the dropship or in the Player lance
  • Can be used with castDef_Commander
• Dialogue: Dialogue can reference Commander, Speaker, Bound or Position Player Pilots
  • Some pilots can be accessed in the dialogue, e.g. ({MC.PlayerLance.TeamPilot_Random_2.UnitName}, {MC.PlayerLance.Speaker.DisplayName}, {MC.Commander.DisplayName})
• Dialogue: Conditional dialogue - the ability to show dialogue on certain conditions
  • Supports checks against Employer or Target Faction Type
  • Supports checks against Employer or Target Name and Short Name
  • Supports tag checks against all tag scopes (Pilot, Commander, Company, System) and a new custom Encounter tag scope that is fresh for every contract
  • Supports multi-conditional checks ({{condition1} AND {condition2}}, {{condition1} OR {condition2}})
  • Supports random percentage chance checks
• Dialogue: Modifications - the ability to modify the game
  • Supports adding tags to all tag scopes
  • Supports removing tags from all tag scopes
• Dialogue: Formatting - the ability to change text style
  • Supports formatting text to different cases (ToUpper, ToLower, ToUpperFirst, ToAlternating, e.g. [MC.Format.ToUpper.{TEAM_EMP.FactionDef.Name}])
  • Helps fix vanilla BT annoyance with Faction names starting lowercase so faction names can now be correctly used at the start of sentences.
• Per-Contract Override - Additional Lances - Support Enabling / Disabling UseDialogue
  • Allows modders to remove the Ally mission start dialogue for AL lances at a contract level
• Per-Contract Override - Additional Lances - Support Custom Objective Names
  • Allows modders to provide custom names for the Enemy AL lances
  • Fewer objective names can be provided than AL lances and if the names aren't enough it fallsback to the default names
• Per-Contract Override - Additional Lances - Support CastDef
  • Allows modders to provide a custom CastDef id and that Cast will speak the mission start dialogue for Ally AL lances
  • CastDef id can be a Mission Control dynamic CastDef id as mentioned in the new Dialogue features
• Per-Contract Override - Additional Lances - Support Custom Dialogue
  • Allows modders to provide custom dialogue for the Ally AL lance to speak at the mission start dialogue
• Additional Lances - Code API access
  • Allows modders to link against Mission Control and access the Additional Lances feature functionality
  • Modders can provide a lance count, list of LanceOverrides or MLanceOverrides and optional objective name overrides
  • This will override every other AL lance approach
  • Usable only for procedural contracts and not available for Flashpoints and Story contracts
  • Accessed through MissionControl.Instance.API
• Metrics
  • Added a way for other mods to access some Mission Control data
  • Accessed through MissionControl.Instance.Metrics
  • Currently supports Additional Lance counts per encounter/contract

#⚡ Improvements

• Custom Contract Types: Build File Format Updated
  • The custom contract type build file format is updated as built by the Designer
• Solo & Duo Duel: OpFor Moves To Engage Before Contact
  • Previously, the OpFor duelists would sit at their spawn point until contact was made, then they would move to engage the player
  • This led to a boring situation where the player would just jump the enemy
  • Now the OpFor moves to engage the player similar to how the player would move at the start of the contract
• Extended Boundaries - Support use of only MapId
  • Previously, you could provide only ContractTypeName or provide ContractTypeName and MapId but you couldn't only provide MapId
  • You can now provide only MapId if required
• Blackout: Fixed bad turret placement in Phase2 base in Story7 map
  • Often the turrets would destroy the buildings they were meant to protect
• Additional Lances: Follow AI is restricted to Additional Lance lances
  • Previously, the FollowAI would be injected into the Core behaviour tree and Follow orders would be sent to all lance units that had the Employer tag
  • This correctly didn't affect things like Escort units or Defend Base engineers as they didn't use the Core AI behaviour tree
  • Now, the AI Follow order is sent to any lance units that have both Employer and AdditionalLance tags - so only the AL lances
  • This change purely keeps Mission Control's Follow AI influence to where it's required
• Data Cleanup: Added new method for cleaning up data from Mission Control
  • This new method is now default
  • The old method can be turned on instead if there are some unforseen compatibility issues with other mods in the community
  • In settings.json, there is a new setting under Misc/ContractOverrideDataCleanupMethod
    • RestoreFromCopy is the default and the new cleaning method. It takes copies of LanceOverrides and ObjectiveOverrides and restores them after combat
    • ScrubData is the old method. It scans through the contract override and removes anything MC added.
• Contract Type Builder - Added DurationType property to OccupyRegion Objective

#🔧 Changes

• Contract Type Builder - Refactored SetStateResult result to SetStatusResult
• Contract Type Builder - Refactored SetStateAtRandomResult result to SetStatusAtRandomResult

#🐛 Bug Fixes

• Additional Lances: Ally units Follow AI was breaking after initial contact with enemies
  • If an initial encounter was made and at least one enemy unit was destroyed, then contact lost - then the ally AL Follow AI wasn't stripping out dead units for visible/detected enemy checks so the ally AL would always think there were enemies nearby and never return to follow mode
  • Now, dead units are not considered valid for visible/detected enemy checks
  • Now, ally AL lances will return to follow mode correctly after contact is lost
• Custom Contract Types: Metadata was using wrong heights when plots changed
  • Mission Control's custom recalculation of the metadata (based on BT's algorithm) was running before the custom contract type plots were enabled/disabled
  • This would cause the metadata heights to not always be correct in plot areas that were different to the existing vanilla metadata

#📝 Documentation / Website

• Added a Dialogue System feature page
• Added a Metrics feature page
• Updated Per-Contract Overrides feature section with new Additional Lances settings
• Added ContractOverrideDataCleanupMethod to the Settings feature page
• Added Additional Lance API section to the Additional Lances feature page
• Added information on MapId only overrides for the Extended Boundaries feature page
• Fixed incorrect information in SetTeamByLanceSpawnerResult and SetTeamByLanceSpawnerGuidResult result pages
• Refactored SetStateResult result to SetStatusResult
• Refactored SetStateAtRandomResult result to SetStatusAtRandomResult
• Fixed incorrect information in CompleteObjectiveResult result page
• Fixed incorrect information in EncounterObjectiveMatchesState conditional page
• Fixed incorrect information in ObjectiveStatuses conditional page
• Fixed issue with latest LastPass Chrome plugin with the website causing empty space to appear near the top of the page
• Added DurationType to OccupyRegion objective page

#🆙 Upgrade Instructions

This update is just a dll and mod.json update.

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json

#Copy and Overwrite Example Per-Contract Override Files

• Copy and overwrite config/Contracts to config/Contracts folder

#Copy new CastDefs

• Copy and overwrite overrides/cast folder to overrides/cast folder

#Copy new Blackout contracts

• Copy overrides/contracts/blackout/Blackout_AMinorRoyalPain.json to overrides/contracts/blackout
• Copy overrides/contracts/blackout/Blackout_AbsentWitness.json to overrides/contracts/blackout
• Copy overrides/contracts/blackout/Blackout_PreparedGrounds.json to overrides/contracts/blackout

#Add ContractOverrideDataCleanupMethod setting to the settings.json

• Edit the Misc section and add to the bottom of that section:

"ContractOverrideDataCleanupMethod": "RestoreFromCopy"
Copy

#Copy new portraits

• Copy and overwrite spirtes/Portraits folder to spirtes/Portraits

#❗ Update Custom Contract Type Build Files

There are many changes within the custom contract type build files and the EncounterLayer files that need to be addressed in this update. I'll explain the easiest method that I recommend.

#Easiest (RECOMMENDED) Method

Everyone should use this approach to upgrade the contract type and encounter layer files.

• Delete your contractTypeBuilds folder and copy in the new v1.5 release contractTypeBuilds folder
• Delete your overrides/encounterLayers folder and copy in the new v1.5 release overrides/encounterLayers folder
• (BTA modpack, and any modpack with their own custom contract types) Recreate your Hero Duels (or other custom contract types you've made)
• (Any modpacks that edited the old contract type build files) Remake the old changes to the new contract type build files

#Harder (NOT SUPPORTED) Method

If you decide to take this approach it is NOT SUPPORTED by Mission Control (and CWolf). The only reason you'd take this approach is if you made extensive changes to the previous custom contract types and you didn't want to lose these changes. NOT RECOMMENDED.

• Rename all contractTypeBuilds in your modpack to be the same as the new contractTypeBuilds
• Copy over new contractTypeBuilds files for SoloDuel, DuoDuel, Blackout into their respective sub-folders
• Rename all overrides/encounterLayers files to be the same as the new contractTypeBuilds

NOTE: For any non-MC custom contract types the names of the your own custom encounterLayers must take the same format and link to the contract type build files. The reason for this is for Designer compatibility. The format is:

• build file: [mapname]_[biome].jsonc, for example centralmountain_desertparched.jsonc and mountainhold_lunarvacuum.jsonc

• encounterLayer file: encounterLayer_[contracttype].[mapname]_[biome].json, for example encounterLayer_blackout.centralmountain_desertparched.json and encounterLayer_blackout.mountainhold_lunarvacuum.json

• Compare each and every contract type build file and apply the diff changes manually (allows you to keep your custom)

This release fixes a bug in Extended Lances and one in Additional Lances.

The full release diff can be at the v1.4.2 pull request.

#🐛 Bug Fixes

• Additional Lances: Elite lances always being used
• Extended Lances: Pilots from EL lances that are expanded are default pilots instead of LanceDef pilots if autofill is not allowed
  • This issue would only happen if the EL lance wasn't in autofill mode
  • For any additional units that get expanded from a LanceDef with a pilot would fallback to default
  • Pilots filled from the UnitSpawnPointOverrides that existed in the contract lance units would fill correctly

#🆙 Upgrade Instructions

This update is just a dll and mod.json update.

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json

This release fixes some bugs related to the newly upgraded Extended Lances.

The full release diff can be at the v1.4.1 pull request.

#🐛 Bug Fixes

• Extended Lances: Lances with 0 unit spawn points broke map loading
• Extended Lances: A team's skipped lances could sometimes skip processing for all lances in that faction

#🆙 Upgrade Instructions

This update is just a dll and mod.json update.

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json

This release introduces Extended Lances version 2, a major upgrade to Extended Lances, and some minor bugfixes.

The full release diff can be at the v1.4.0 pull request.

#❗ Extended Lances v2 Upgrade ❗

As many of the features and fixes are related to EL - I'm drawing attention to it here. Some of the below fixes and improvements for EL v2 are covered below in the main changelog too.

• Extended Lances v2 Upgrade
  • Extended Lances has been given a major upgrade. There were some fundamental issues and limitations with EL that preventing some modders achieving the results they wanted. Now EL should have fewer bugs and more flexibility.
  • Backwards compatible
  • Extensively tested

#🚀 Features

• Extended Lances: Support all other Teams
  • EL now supports TargetAlly, EmployerAlly, HostileToAll, NeutralToAll
  • This feature is on by default so modpacks might want to consider game balance
  • Support can be individually turned off in the settings.json in the EL section
  • Can be individually overridden with per-contract overrides
• Extended Lances: Provide a way to force EL to allow specific LanceOverride set ups
  • A new settings.json property called ForceLanceOverrideSizeWithTag which controls this behaviour
  • When a LanceOverride (lance in the contract json) has this tag in its lanceTagSet/tagSetSourceFile then it will force EL to spawn this exact defined lance
  • lanceTagSet/tagSetSourceFile is not used in BattleTech so it's been adopted for this feature
• Extended Lances: Provide a way to force EL to allow specific LanceDef set ups
  • A new settings.json property called ForceLanceDefSizeWithTag which controls this behaviour
  • When a LanceDef has this tag in its LanceTags/tagSetSourceFile then it will force EL to spawn this exact defined lance
  • LanceTags/tagSetSourceFile is not used in BattleTech so it's been adopted for this feature
• Extended Lances: AutofillType setting
  • When EL autofills lances it has to decide how to handle units that are defined as empty (mechDef_None, vehicleDef_None)
  • A new settings.json property called AutofillType which controls this behaviour and it has two settings:
    • RespectEmpty is the legacy and still the default behaviour. When a LanceOverride or LanceDef has empty units defined (e.g. mechDef_None, vehicleDef_None) then it will respect those and not autofill them.
    • FillEmptyis a new autofill behaviour. When a LanceOverride or LanceDef has empty units defined (e.g. mechDef_None, vehicleDef_None) then it will autofill and replace them so units will spawn in those slots.
• Extended Lances: AutofillStartingFromContractDifficulty setting
  • A new settings.json property under ExtendedLances called AutofillStartingFromContractDifficulty
  • To aid in a fairer early game, you can now control when Extended Lances autofills units in lances that are below the faction's EL LanceSize by setting a contract difficulty (real difficulty - not UI/visible difficulty) to start autofilling from
  • This does not affect LanceDefs that fill up to the faction's LanceSize themselves (e.g. modpack Clan LanceDefs up to 5 or 6 etc)
  • For those who don't want this feature - set it to 1
• Extended Lances: AutofillUnitCopyType setting
  • At times EL needs to copy units to create a varied and interesting lance when autofilling it up to the Faction Size (or any overridden size). In this case EL tries to copy a 'Tagged' lance so to use this tagged UnitSpawnPointOverride and leverage the tags to provide variation. If there are no 'Tagged' lances available to copy it will use the defined behaviour in AutofillUnitCopyType in the settings.json.
  • A new settings.json property called AutofillUnitCopyType which controls this behaviour and it has two settings:
    • FirstInLance - The legacy behaviour. It would pick the first unit (index 0) and copy it (giving it new identify/clearing custom names etc)
    • RandomInLance - The new behaviour and is now the default behaviour. It picks a random unit from the Lance to copy (giving it new identify/clearing custom names etc)

#⚡Improvements

• Extended Boundaries: Ambush Convoy - Reduce increase from 30% to 20%
  • Previously Ambush Convoy boundary increased by 30%. As players sometimes struggle to catch the convoy if the Random Spawn algorithm places them too far away the boundary increase is now reduced slightly to 20%

#🐛 Bug Fixes

• Extended Lance: LanceOverrides with fewer units than a selected LanceDef didn't populate all LanceDef units
• Extended Lances: LanceDefId being direct reference only added one extra lance instead of EL number
• Random Spawns: Blackout - Opposing Force Orientation Was Wrong
• Additional Lances: Incorrectly handling lanceExcludedTagSet
  • MC AL lances incorrectly added lanceExcludedTagSet to the lanceTagSet. This would cause incorrect lance selection behaviour for MC AL lances with tags
• Vanilla: When BT copies LanceDefs it didn't maintain the LanceTags 'tagSetSourceFile' data
  • When BT copies LanceDefs it would never maintain/preserve the tagSetSourceFile property. Since this property is never used in the game it isn't a problem, however, Since ELv2 uses it - it has been fixed

#📝 Documentation / Website

• Added ModTek v2 information in the setup page
• Added per-contract override page
• Added settings.json override with settings.modpack.json and settings.user.json in the settings page
• Added SwapPlacement type EncounterStructure subtype node information in the contract builder API nodes area
• Added CombatState type DisablePilotDeath subtype node information in the contract builder API nodes area
• Updated Extended Lances information for version 2
• Removed HBS mod loader information

#🆙 Upgrade Instructions

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json
    • config/Contracts/My_Contract_ID_Example.json
    • config/Contracts/My_FP_Contract_ID_Example.json

Add the following to your settings.json:

#Under ExtendedLances add:

"EnableForTargetAlly": true,
"EnableForEmployerAlly": true,
"EnableForHostileToAll": true,
"EnableForNeutralToAll": true,
"AutofillType": "RespectEmpty",
"AutofillUnitCopyType": "RandomInLance",
"AutofillStartingFromContractDifficulty": 3,
"ForceLanceOverrideSizeWithTag": "mc_force_extended_lance",
"ForceLanceDefSizeWithTag": "mc_force_extended_lance",
Copy

and update to have mc_no_extended_lance:

"SkipWhenExcludeTagsContain": ["mc_no_extended_lance", "no_extended_lance"],
Copy

#Under ExtendedBoundaries/Overrides add:

{
  "ContractTypeName": "AmbushConvoy",
  "IncreaseBoundarySizeByPercentage": 0.2
}
Copy

This release fixes a major bug relating to v1.3.1 breaking the MC pathfinder system.

The full release diff can be at the v1.3.2 pull request.

#Major Bug Fixes

• Random Spawns: Broken pathfinder due to optimisations

#Upgrade Instructions

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json

This release focuses on compatibility enhancements and some minor bug fixes.

The full release diff can be at the v1.3.1 pull request.

#Bug Fixes

• Duo Duel: Fixed broken player pilot death prevention system
  • Fixed FestiveCouple's player pilot death prevention system again
  • This wasn't fully fixed in v1.3.0 for FestiveCouple
• Additional Lances: Fixed Support Lance objective starting at '2' instead of '1'

#Improvements

• ModTek v2 Support: Added support for ModTek v2
• Improved Deferred Loading of Assets
  • Older system didn't care what else was loading. Now properly checks to fit itself in between other assets loading
• Improved CAC Compatibility
  • Fixed a very rare situation where loading of assets by MC could deadlock loading careers or skirmish

#Upgrade Instructions

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json
    • overrides/contracts/duoduel/DuoDuel_FestiveCouple.json

This release fixes various bugs and adds various enhancements.

The full release diff can be seen here

#Bug Fixes

• Story Support: Fixed Boundary Detection Issue
  • Improved how the boundary game object is grabbed for boundary related processing
• Duo Duel: Fixed broken player pilot death prevention system
  • Fixed YearlyTussle and FestiveCouple's player pilot death prevention system
• Additional Lances: Fixed cases where direct LanceDef references failed
  • Sometimes if a direct LanceDef was used and it was not already loaded in memory it would fail and not grab it from the file system
• Contract Types: Fixed various non-critical spelling mistakes in Blackout, Solo Duel and Duo Duel

#Improvements

• Additional Lances: Added a per-contract override to manually specify the Additional Lance(s) dropping
  • This acts as a middle ground between dynamic AL and custom contract types. You can use a per-contract override for your contract and manually specify the dropping ally and enemy Additional Lances
• Additional Lances: Support higher than difficulty 10 for config files
  • MC used to only look for AL config difficulty1.json up to difficulty10.json. Now it has unlimited search for difficulties.
• Additional Lances: Added Drop Weight Influence maximum influence caps
  • Added an absolute max value for Drop Weight Influence Enemy and Ally settings that an influence value can go to.
• Contract Type Builder: Improved 'Mount On' positioning
• Contract Type Builder: Added custom MC trigger support for Dialogues
• Contract Types: Added optimisation for contract selection related to custom contract types

#Upgrade Instructions

• If you're using MC without a modpack and none of your own changes, just delete the MC folder and move the new one into your mods folder
• If you're using MC as part of a modpack, let the modpack authors update MC for you (using the below guide)
• If you're using MC without a modpack but you've made some of your own changes to the configs, or you're a modpack author:
  • Copy into your Mods/MissionControl folder
    • MissionControl.dll
    • mod.json
    • config/Contracts/My_FP_Contract_ID_Example.json
    • contractTypeBuilds/Blackout/common.jsonc
    • contractTypeBuilds/Blackout/mountainhold_lunar.jsonc
    • contractTypeBuilds/DuoDuel/common.jsonc
    • contractTypeBuilds/SoloDuel/common.jsonc
    • overrides/contracts/duoduel/DuoDuel_FestiveCouple.json
    • overrides/contracts/duoduel/DuoDuel_YearlyTussle.json
    • Edit settings.json (and/or your settings.user.json / settings.modpack.json overrides) with the following:

#Add the following under the AdditionalLances/DropWeightInfluence block

"EnemySpawnInfluenceMax": 0.9,
"AllySpawnInfluenceMax": 0.9,
Copy

Specific for RT modpack

Since you had an early release with the Drop Weight Influence maximum - no need to change your custom config for that feature.