SideOp Companion is a UI-driven program, designed to help automate the process of creating custom sideops for Metal Gear Solid V: The Phantom Pain with the goal of improving their accessibility.

Custom Sideops are playable, user-created side-missions which can be added to the game through TinManTex's Infinite Heaven mod. Creating custom sideops manually can be difficult, even for experienced MGSV modders. Without an acute understanding of the game's files, formats and limitations, the user can often find themselves lost and confused.

SOC, or SideOp Companion, is my attempt to automate the process of creating custom sideops. The program alleviates a great deal of the difficult, tedious work involved in creating a custom sideop. Even with minimal understanding of modding, users can create and test their own custom sideops with relative ease. SOC can even create sideops with greater detail than those found in the base game, without even touching the game files. It is perhaps possible that SOC will make Custom Sideops the simplest and most accessible form of MGSV modding.

Upon opening SOC.exe, the user is met with the Setup Page. This page prompts the user to fill in a number of forms which are required for a custom sideop.

• .FPK Filename: This is what the sideop will be named in the gamefiles. The user should think of a name which will be unique to the sideop.

  • Examples: MorbidQuest00, MorbidQuest01, ih_sheep_quest, ih_pilot_quest, Example_QuestName

• Quest Number: This quest number is how Infinite Heaven adds new sideops to the game. The quest number can range between 30103 and 39009. Users should check which quest numbers have already been taken by other mod authors by opening the MGS_TPP directory with Infinite Heaven installed, then navigating to \mod\modules\InfQuest.lua. The user can pick any quest number they wish for testing purposes, but prior to publishing custom sideops to nexusmods, users should contact Tinmantex to reserve their quest numbers, which will then be recorded in InfQuest.lua.

  • If the user is unsure of what to write to Tinmantex, simply tell him: "I am making a custom sideop(s), and I wish to reserve <X Amount Of> Quest Numbers." He can tell you which numbers to use.

• Quest Map: The Area of Operations for the sideop. The user can choose to create a sideop for Afghanistan, Central Africa or even Mother Base (with limitations).

• Quest Area: Quest Areas are fractions of the map where a single sideop is available. The user should choose the appropriate area that the sideop will be located within.

  • Read 'SOC QuickMenu Guide' for information about how to get the correct area name.

• Quest CP: This is the name of the enemy Command Post for the sideop. Each enemy encampment in MGSV has a CP which determines the alert status of the encampment's soldiers. SOC will draw enemy-related information from the selected CP, such as route names and pre-existing soldiers in the encampment.

  • Some CP names are rather self-explanitory (ex: afgh_powerPlant_cp refers to the Serak Powerplant in Afghanistan). Other CP names are more confusing (ex: mafr_pfCamp_cp refers to Nova Braga Airport in Central Africa).
  • Read 'SOC QuickMenu Guide' for how to find an encampment's CP name.

• Map Coordinates: X Y Z: These are the ingame coordinates for the center of the side-mission circle that appears on the iDroid. The circle is aesthetic, and does not affect the actual gameplay aside from the pop-up UI which notifies the player upon entering the circle.

  • Read 'SOC QuickMenu Guide' for how to get in-game coordinates.

• Radius: This determines the size of the side-mission circle that appears on the iDroid. The radius of a sideop is likewise aesthetic.

• Route File: As of SOC 0.6.0, the user can now specify a route file (.frt extension) to be utilized for the sideop. Route Files allow the user to assign routes which aren't normally used in freeroam.

  • The user can add new routes to the Route File list by going to the SOC directory and then navigating to SOCassets\RouteAssets. Any .frt file placed into the RouteAssets directory will appear on the Route File list.
  • Creating new, custom route files is possible, albiet difficult and not user-friendly. Until custom route creation is more accessible, the user should search the vanilla game files to find routes which will suit their sideops. Read 'Enemy Routes Guide' to learn how to find route files within the game archives.
  • Sai/youarebritish nearly single-handedly reversed the route file format, which deserves a great deal of praise. SOC would not be able to handle route files without his work.

• Quest Category: Categories are only used for selecting which sideops will appear in an Area of Operations. The user can choose whichever category that they feel will fit the sideop best.

  • The sideop does not need to match the category perfectly (ex: using ELIMINATE_HEAVY_INFANTRY for a sideop that involves assassinating a VIP, or using ELIMINATE_PUPPETS for a sideop that involves rescuing zombies).

• Quest Rank: this is essentially the GMP reward for completing the mission. The user can choose any rank between 300,000 GMP (S rank) and 30,000 GMP (I rank), as they please.

• Quest Title: This is the sideop's name that shows up on the iDroid in-game.

  • The title itself is aesthetic. The flavor text has no affect on the gameplay.

• Quest Description: Like with the Quest Title, the Quest Description will appear on the iDroid menu in-game, when you select the sideop on the side-missions list.

  • The description is likewise flavor text, with no bearing on the gameplay.

• Progress Notification: This determines the notification text which pops up when the player completes a task for the sideop (ex: Prisoner Extracted [1/3]).

  • Users can create Custom Notifications by clicking on the 'Custom...' button. For information on creating a Custom Notification, read 'Custom Notifications Guide'.

• Locational Data textboxes: These textboxes will read sets of coordinates (x, y, z and y-axis rotation) and create a 'box' on the Details Page for the specified coordinate.

  • Read 'SOC QuickMenu Guide' for how to get in-game coordinates.
  • The user does not need to fill out every Locational Data textbox, only the textboxes for the objects they wish to use in the sideop.
  • There is no enforced limit on how many coordinate sets can be used in a sideop, although the user should still consider the game limitations when setting coordinates (ex: only 3 heavy vehicles can be reliably spawned into a quest). Additionally, the extra resources used in sideops can strain the game's allocation and cause crashes (ex: spawning 40 prisoners in a sideop). Certain Infinite Heaven features, such as helicopters and walker gears in free roam, may already be using additional resources. As such, a player may encounter game crashes if they have such features enabled when they enter a quest area. The user should be considerate of these limitations when creating their custom sideops.
  • While the textboxes prompt the user to input {pos={X, Y, Z},rotY=Y-Axis Rotation,}, SOC will accept any 4 numbers as a coordinate set (ex: {pos={1, 2, 3},rotY=4,} and 1 2 3 4 are both valid inputs). If there are less than 4 numbers in a set, the coordinate is auto-filled with 0.00 as the remaining numbers.

Once the user has filled out the required Setup information, and input their desired Locational Data, they can click the "Next >>" button in the bottom-right corner to build the Details Page. The user can return to the Setup Page at any time, without losing any changes.

After clicking "Next >>" button on the Setup Page, SOC will display the Details Page. The Details Page reads the CP Name and Locational Data textboxes from the Setup Page and lists it as editable boxes. Boxes can be added and removed by returning to the Setup Page and editing the setup information.

• Target Objective Types: If the boxes of a detail column can be used as sideop targets, a combo box will be displayed at the top of the panel, known as the column's Objective Type. This combo box will allow the user to determine how the player must handle targets of that detail column. Unlike the vanilla game, these objective types can vary from column to column, to improve sideop variety (Ex: Rescue the prisoner and assassinate the colonel).
  • ELIMINATE: The player must either extract or kill the targets (Ex: Eliminate the Heavy Infantry is an elimination-type sideop).
  • RECOVERED: The player is required to extract the target. If the target dies, the mission is cancelled (Ex: Prisoner Extraction is a recovered-type sideop).
  • KILLREQUIRED: The target must be killed. If the target is extracted, the mission is cancelled. This is a new Objective Type, not found in the vanilla game.

There are several different types of detail boxes:

• New Enemies: These boxes list new enemies (8 total) which can be spawned into the encampment for a Sideop. These boxes will only appear on the Details Page if you have selected a CP Name on the Setup Page.

  • Soldier SubType: Determines the appearance of the sideop's enemies.
    • In Afghanistan, the user can choose between SOVIET_A and SOVIET_B. SOVIET_A are Soviet soldiers who wear mostly green and tan uniforms, whereas SOVIET_B wears black and blue uniforms.
    • In Africa, the user can choose between the different Private Forces soldiers, PF_A, PF_B and PF_C. PF_A are CFA Soldiers, PF_B are ZRS Soldiers and PF_C are Rogue Coyote soldiers.
  • Spawn: Determines whether the new soldier will be added to the sideop.
  • Is Target: Determines whether the soldier will be a target objective for the sideop.
  • Balaclava: Determines whether the soldier will wear a balaclava (limit 8 per sideop).
  • Is Zombie: Determines whether the soldier is a parasite-zombie.
  • Sneak Route: Determines the route of the soldier when the CP is not aware of the player's presence.
  • Caution Route: Determines the route of the soldier when the encampment is on alert.
    • note The listed routes have undescriptive names (ex: rt_powerPlant_d_0000). Unfortunately, the user cannot yet preview the routes without checking them in-game. For more information on routes, read 'Enemy Routes Guide'.
    • Multiple soldiers can share the same route. They will patrol together during the sideop.
    • If the user has specified a route file on the Setup Page, the file's route names will appear on the Caution and Sneak route lists. Route names are hashed, and without a route name dictionary, would appear as a string of numbers (Ex: 2036843189). A dictionary is provided within the SOCassets, but not every route name has been unhashed. This means that the route lists may contain a sum of unhashed route names, depending on the selected route file. Nonetheless, soldiers can still be assigned to "number routes" without issues.
  • Gear | Tactics: Determines what equipment the soldier will wear, as well as their combat preparedness (ex: enemies with MG will have machine guns equiped, and enemies with FULTON_SPECIAL will shoot at fulton balloons).
  • Heavy Armor: Determines whether the soldier is wearing riot gear (limit 8 per sideop).
    • Riot Gear soldiers cannot also wear balaclavas or different Body appearances.
  • Body: Determines the appearance of the soldier.
    • Body names marked with 'unq' are unique outfits, such as the soldiers with berets or special uniforms. Check out Infinite Heaven's appearance notes on the body names by opening the MGS_TPP directory with Infinite Heaven installed, then navigating to \mod\modules\InfBodyInfo.lua.
  • Staff Type: Determines the Mother Base team that the soldier will be best suited for.
  • Skill: Determines the soldier's unique skill.

• Existing Enemies: Enemies that are already patrolling the encampments can be retooled for sideops, in the same ways that New Enemies can be spawned.

  • Customize: Customizing an existing soldier will allow the user to retool the selected soldier for the sideop. The soldier will otherwise follow their normal routes with their default attributes.

• Enemy Helicopter: A helicopter can be reserved to a sideop as of SOC 0.6.0. Like enemy soldiers, a helicopter can be assigned a route, which it will follow while the player is within the sideop active area.

  • Spawn: Determines whether the helicopter will appear during the sideop.
  • Is Target: Determines whether the helicopter will be a target objective for the sideop.
    • Due to the nature of enemy helicopters, there is only one target objective type available: KILLREQUIRED.
  • Class: Determines the color and health of the spawned vehicle.
  • Route: Determines the route which the helicopter will patrol during the sideop.
    • Helicopter routes are relatively rare in MGSV:TPP. By default, SOC has a small selection of helicopter routes for large enemy outposts. These routes were originally used as outpost assault routes (Red LZs), but are repurposed for enemy helicopters.
    • The helicopter panel will not appear if SOC does not contain a route for the selected CP and the player has not selected a route file for the sideop.
    • If a route file is selected on the Setup Page, that file's route names will be available to choose from for the Helicopter route. Note that helicopters can technically use soldier routes, but it is highly recommended that the user chooses helicopter-specific routes (so the helicopter will not tread through the ground during its patrol). For more information on routes, read 'Enemy Routes Guide'.

• Walker Gears: As of SOC 0.6.0, customized Walker Gears can be spawned into sideops (with certain limitations).

  • Coordinates: Determines the X, Y, Z coordinates of the Walker Gear.
    • When placing a walker gear, the user should be certain that they are well-within the boundaries of the Quest Area. Walker Gears were not originally designed for Sideops, and because of this, Walker Gears could not be auto-fultoned when the player reaches the Quest Area boundary, which causes loading issues. To combat this, Walker Gears are now scripted to teleport back to the Quest Area boundary if the player attempts to ride the Walker out of the sideop.
    • Note: Quest-specific Walker Gears are not designed to work alongside Infinite Heaven's "Walker Gears in Free Roam" option. It is recommended that players turn off the Infinite Heaven feature before playing a sideop which uses Walker Gears.
  • Rotation: Determines the direction that the Walker Gear will be facing. The rotation is in degrees.
  • Is Target: Determines whether the Walker Gear is a target objective.
  • Enemy Pilot: Assigns one of the 8 New Enemies to ride the Walker Gear.
    • Note: The assigned pilot must be spawned in order for them to ride the Walker Gear.
    • Warning: Walker Gears, like helicopters, use rare and specific routes. If the soldier riding the walker gear is assigned to a non-walker-gear route, they will likely dismount from the Walker Gear as soon as they reach their second route node. It is recommended that walker gears are not assigned pilots, unless the user is certain that the route is designed for Walker Gears. For more information on routes, read 'Enemy Routes Guide'.
  • Paint Type: Assigns the Walker Gear a faction-specific paint job. Purely aesthetic.
  • Weapon: Determines the primary weapon for the Walker Gear. The user can choose between the gattling gun or the homing rocket launcher.

• Prisoners: Prisoner boxes are added by inputting coordinate sets into the Prisoner Locations textbox on the Setup Page. A hostage will be placed at every coordinate set in the textbox.

  • Body: Determines the body type and gender for all prisoners.
  • Interrogate For Whereabouts: Determines whether the player can interrogate an enemy soldier for the whereabouts of the prisoner(s).
  • Coordinates: Determines the X, Y, Z coordinates of the prisoner.
  • Rotation: Determines the direction that the prisoner will be facing. The rotation is in degrees.
  • Is Target: Determines whether the prisoner is a target objective.
  • Untied: Determines whether the prisoner is untied and sitting upright.
  • Injured: Restricts the player from fultoning the prisoner.
  • Scared: Determines how the prisoner will act. ALWAYS scared prisoners will always be shaking and snivelling after being untied, whereas NEVER scared prisoners will remain sitting upright even during gunfights.
  • Language: Determines the language that the hostage will speak.
    • Female prisoners can only speak english, however Male prisoners can speak english, russian, pashto, kikongo and afrikaans.
  • Staff Type: Determines the Mother Base team that the prisoner will be best suited for.
  • Skill: Determines the prisoner's unique skill.

• Heavy Vehicles: The user can spawn heavy vehicles by inputting coordinate sets into the Vehicle Locations textbox on the Setup Page. Unfortunately, spawned vehicles cannot be entered by the player or enemy soldiers. Note:

  • Coordinates: Determines the X, Y, Z coordinates of the vehicle.
  • Rotation: Determines the direction that the vehicle will be facing. The rotation is in degrees.
  • Is Target: Determines whether the vehicle is a target objective.
  • Vehicle: Determines what type of vehicle will spawn.
  • Class: Determines the color and health of the spawned vehicle.

• Animals: Animal boxes are added by inputting coordinate sets into the Animal Cluster Locations textbox on the Setup Page. A cluster of animals will be placed at every coordinate set in the textbox.

  • Coordinates: Determines the X, Y, Z coordinates of the animal cluster.
  • Rotation: Determines the direction that the animal cluster will be facing. The rotation is in degrees.
  • Animal: Determines the type of animal cluster that will spawn at the coordinates.
  • Count: Determines the number of animals which will spawn at the coordinates.
  • Is Target: Determines whether one of the animals in the cluster is a target objective.
  • Type ID: Gives the animal cluster a specified type ID, to avoid conflicting with existing animals near the sideop.
    • Generally, the user should use TppNubian/TppJackal type IDs in Afghanistan, and TppGoat/TppWolf IDs in Africa to avoid conflicting with the preexisting animals and their animal IDs. A conflict will result in missing animals and game crashes, so it is very important to assign the proper animal ID. The user should be certain of any animals that spawn within the quest area and spawn animals accordingly.

• Dormant Items: Dormant Items are items like guns, ammunition and innactive support weapons which the player can pick up and use during gameplay. The user can spawn dormant items by inputting coordinate sets into the Item Locations textbox on the Setup Page.

  • Coordinates: Determines the X, Y, Z coordinates of the item.
  • Rotation: Determines 3D space rotation of the item. The rotation is in Quaternion format.
  • Is Target: Determines whether the user must collect this item in order to complete the sideop.
    • Note: Only works with weapons. Support weapons can theoretically be picked up automatically if the player already has that support weapon equipped. Due to game limitations, this does not count as a pick up.
    • Note: Due to the nature of dormant items, there is only one target objective type available: RECOVERED.
  • Item: Determines what item will spawn at the coordinates.
    • Items with _WP_ in their name are guns, _SWP_ are support weapons, _IT_ are items, _AB_ are ammo boxes.
    • While most of the items on the list should work properly, some items may be bugged due to game limitations.
    • The items have undescriptive names. The user can check Tex's notes on the item names by opening the MGS_TPP directory with Infinite Heaven installed, then navigating to \mod\modules\InfEquip.lua.
  • Count: Determines the number of uses for items/support weapons. Guns are unaffected by the Count.
  • Boxed: Determines whether the item is contained in a weapon crate, similar to the Honey Bee mission.

• Active Items: Active Items, unlike dormant items, are already placed and armed prior to the player picking them up. Traps such as Directional Mines, Shock Decoys and Sleep Mines are Active Items. The player will earn heroism for disarming an Active Item. The user can spawn active items by inputting coordinate sets into the Active Item Locations textbox on the Setup Page. (Note: Active Items cannot be placed in a sideop if dormant items exist, and vice versa.)

  • Is Target: Determines whether the user must retrieve or destroy the item in order to complete the sideop.
    • Note: Active Items have all 3 Target Objective Types to choose from. RECOVERED requires the user to pick up the active item without triggering/destroying it. KILLREQUIRED requires the user to trigger/destroy the active item, and cancels the sideop if the item is picked up. ELIMINATE allows the player to pick up or trigger/destroy the item in order to complete the sideop.
  • Coordinates: Determines the X, Y, Z coordinates of the active item.
  • Rotation: Determines 3D space rotation of the item. The rotation is in Quaternion format.
  • Active Item: Determines what active item will spawn at the coordinates.

• Static Models: Static models can be placed and used for both aesthetic and gameplay purposes, such as a wrecked helicopter or a barbed fence. The user can spawn models by inputting coordinate sets into the Static Model Locations textbox on the Setup Page.

  • Coordinates: Determines the X, Y, Z coordinates of the model.
  • Rotation: Determines 3D space rotation of the model. The rotation is in Quaternion format.
  • Model: Determines what model will spawn at the coordinates.
    • a number of preset models are included with SOC by default. The user can add new models to the Model list by going to the SOC directory and navigating to assets\ModelAssets, where they can add .fmdl and .geom files from the game. The .geom file is not required, but recommended.
    • a number of models will spawn above or below the origin of their coordinate. The user will need to compensate by manually adjusting the Y coordinate.

When the user has input all of their desired changes to the Details Page, they can click the "Build" button in the bottom right to build the sideop, or "<< Back" to review the Setup Page before continuing.

Once the Setup and Details Pages are completed and the user is ready to test the sideop in-game. It is recommended that the user save the sideop to an Xml file prior to closing SOC.

1. Click the "Build" button on the Details Page to create a "Sideop_Build" folder which contains the mod files, ready to be packed for Makebite.
2. Open Makebite, and click the ellipses button in the top-right corner.
3. Navigate to the Sideop_Build folder and select it, then Click "Select Folder".

• If the folder was selected properly, a number of filepaths should appear in the Makebite Mod Files. The filepaths should begin with /Assets/ (except one, which begins with /GameDir/).

4. Fill out the Makebite Mod Information.
5. Click the "Do it (build archive)" button in the bottom-right corner and name the file.

• This will build the .MGSV file, which can be installed via SnakeBite.

6. Install the sideop .mgsv file, as well as Infinite Heaven if it isn't already installed.
7. Start the game and open the Infinite Heaven ACC Main menu.
8. In the ACC menu, open "10:Side ops menu" and in that menu, find "2:Open Specific Sideop".

• By default, the number begins with 0. The user can loop to the last Sideop on the list by dropping below 0.

9. Select the new sideop.

• Without any other sideops installed, the new sideop should be #162 or #161.

The user can now test the sideop and make adjustments as necessary by loading the sideop's xml file back into SOC.

SOC can save sideops to an xml file, and also load the sideop xml file at any point during the sideop's creation process.

• To save a sideop, click the "Save To Xml..." button at the bottom-left corner of the application. Name the Xml and click Save.
• To load a sideop, click the "Load From Xml.." button at the Bottom-left corner. Select the Xml and click Open.
  • Six example sideops are included by defaul with SOC. The user can load these examples from the Example Sideops folder, inside Helpful User Resources. Each example can be built and tested ingame, to help the user better understand SOC and it's capabilities.

In the SOC directory, a folder named "Helpful User Resources" contains a .mgsv file named "SOC QuickMenu For Infinite Heaven.mgsv". This QuickMenu preset is immensely useful for gathering in-game information for custom sideops. The user must have Infinite Heaven r223+ installed in order to utilize the QuickMenu.

SOC QuickMenu maps a number of useful hotkey functions to the keyboard/gamepad, so the user does not need to navigate the Infinite Heaven menu to get sideop information.

The hotkeys are mapped as followed:

• While holding down the [Call] button:
  • Press the [Action] Button to toggle Free Cam.
    • Free Cam can be nice for getting into tight or precise places where the player normally could not. The Free Cam speed can be controlled by holding down the [Action] button and moving forward/backward. The camera can be moved up and down with the [Camera Zoom] and [Sprint] buttons, respectively.
  • Press the [Crouch] Button to write the player's position to ih_log.txt. If Free Cam is active, the Free Cam position will be written to ih_log.txt instead.
    • This will write the player's current coordinate set to Infinite Heaven's ih_log, located in \MGS_TPP\mod\ih_log.txt. These coordinates are the key to placing prisoners, items, static models and other side op objects. Once written to ih_log, these coordinates can be easily copy/pasted into SOC's Locational Data textboxes.
    • Additionally, the Quest Area of the player's position will be written to ih_log.txt.
    • Certain areas of the map are not covered by the Quest Areas. In that event, this hotkey will notify the user if the coordinates are not suitable for a sideop. (Free Cam cannot notify the user of sideop suitability.)
    • When gathering coordinate sets with the Free Cam, note that the camera must be as close as possible to the surface of the ground/object. Otherwise, the sideop object may noticably float above the surface in-game.
  • Press the [Reload] or [Dive] Buttons to warp the player to the most-recent iDroid marker. If Free Cam is active, the player will warp to the Free Cam position.
    • Useful for jumping between locations in the encampment. Warping can also teleport the player to distant encampments (occasionally results in falling through the map, but mostly reliable).
  • Press the [Up] Button to mark all soldiers AND set all soldiers to Friendly.
    • Particularly useful for observing soldier routes and gathering locational information in an outpost.
  • If a marker is placed on an enemy, press [Down] to show the enemy name and the closest CP name.
    • This hotkey is useful for finding the correct CP Name for the Setup Page, as well as recording the soldier routes.
  • Press the [Left] Button to toggle the enemy phase between Sneak and Caution.
    • This will help the user observe and test the _d_ and _c_ routes of the outpost's soldiers.
  • Press the [Right] Button to speed up the world timescale for a moment. During this time, soldiers will move very quickly along their routes.
    • When determining which routes to use, watching how and where the soldier patrols move is vital. Speeding up the world timescale will allow the user to learn about patrols much faster than watching in real-time.

When choosing a sideop's progress notification, the user can choose from 9 default notifications. Additionally, the user can create new notifications by clicking the "Custom..." button beside the Progress Notification form. Custom notifications are saved to UpdateNotifsList.txt within SOC's assets folder.

• Upon clicking "Custom...", the user is prompted to input a Unique LangId and an In-game Notification.
  • The Unique LangId is a unique Id referenced by the game files, so the user should choose an appropriate name (ex: example_notif, quest_extract_vip, assassinate_notification)
  • The In-game Notification is the text that the player see in-game, upon completing a sideop task. The user can write any notification that will fit their sideop the best (ex: Example Sideop Notification, VIP Extracted, Commander Eliminated)

Sai/youarebritish has reverse-engineered the route format, which is a great leap forward for modding MGSV:TPP. Creating new route files and previewing existing routes is technically possible, however rather inaccessible for average users. Until route files can be made user friendly, routes will need to be previewed in-game. NexusMods user laranjinho has made an effort to overlay some route names onto in-game screenshots, found here: https://drive.google.com/drive/folders/1Hrz-aIrqfMX3pn8Uf-1wYXcXbu68Kc0G?usp=sharing These images can be very useful and viewing them is highly recommended. For a given route name (ex: rt_powerPlant_d_0000):

• Routes with _d_ in their names are the encampment's daytime routes. These routes are typically more patrol-oriented, so the user is more likely to find patrol routes by assigning soldiers to _d_ routes.
• Routes with _n_ in their names are the encampment's nighttime routes. Nighttime routes tend to be more stationary than their daytime counterparts, with occasional patrol routes.
• Routes with _snp_ in their names are sniper routes, and typically rare. Soldiers assigned to sniper routes will stand in place as they sweep the landscape with their gun at the ready. Assigning soldiers with the 'SNIPER' gear is recommended for these routes, but not required.
• Routes with _c_ in their name are the encampment's caution routes. Soldiers with these routes will walk cautiously with their guns at the ready.
  • _c_ routes can be used as a soldier's Sneak Route, although the soldier will still patrol as if they are on alert. _d_ and _n_ routes can be used as a soldier's Caution Route, but the soldier will still act alert as they patrol.
• Routes with _h_ in their name are hold routes. Soldiers with hold routes will stand in place, alert as they wait for the player.
• Routes with _r_ in their name are rain routes. A soldier assigned to a rain route will stand under shelter (ex: a tent or roof). Soldiers with rain routes are almost always completely stationary.
• Routes with _s_ in their name are sleep routes. Soldiers assigned to a sleep route as their Sneak Route will lay in bed sleeping until disturbed by the player.
  • If the soldier has a sleep route assigned as their Caution Route, they will stand over their bed and hold their gun at the ready (similar to _h_ routes).
• Routes with _a_ in their names are alert routes. These routes are particularly rare, because soldiers use cover-based mechanics by default, without the need of alert-specific routes.
• Helicopters use specific routes, which patrol through the sky. These routes do not seem to follow a naming scheme like the soldier routes, but the route names will often refer to a 'heli' (Ex: enemyHeli01_Search, rt_heli_quest_0001). Additionally, all player landing zones can be considered helicopter routes. These routes will have the 'lz' prefix. A few missions contain helicopter routes, such as Where Do The Bees Sleep, Hellbound, and The War Economy. A number of sideops also utilize helicopter routes.
• Walker Gears use specific routes, which can be assigned to their riders, in order to patrol an area on a Walker Gear. These routes are significantly more rare than other route types, and typically have "_walkerGear" or "_wkr" in their names. Only specific main missions have walker gear routes, such as Hellbound, The War Economy and Skull Face.

As of SOC 0.6.0, an additional route file can be assigned to a sideop. Until custom routes can be made easily accessible, users should seek out existing .frt files within the game's archives. To unpack the game archives, the user must drag the .dat file onto GzsTool.exe. For gathering route files, the user should unpack chunk2.dat (Afghanistan's game files), chunk4.dat (Central Africa's files) and chunk1.dat (contains additional sideop files). Main missions and vanilla sideops are a good source of useable routes; within the unpacked chunk folders, these files can be found in \Assets\tpp\pack\mission2\story and \Assets\tpp\pack\mission2\quest, respectively. The route files are packed into .fpk files, which can also be unpacked with GzsTool. Refer to this list of mission codes when searching for a specific route file. For example, if the user wanted to utilize the Smasei Fort routes from the mission "Where Do The Bees Sleep," they would open chunk2_dat (The Afghanistan archive), and then navigate to \Assets\tpp\pack\mission2\story (The files for the main missions). Once there, the user should use the MissionCodes list to determine the specific mission's code. For "Where Do The Bees Sleep, the code is 10040, so the user should open the s10040 folder. For this mission, there is only one fpk: s10040_area.fpk. unpack this fpk file with GzsTool, and then browse the directory, searching for the *.frt file extension. Copy s10040_area.frt from s10040_area_fpk\Assets\tpp\pack\mission2\story\s10040 to SOC's SOCassets\RouteAssets\ directory. SOC will then list s10040_area as a selectable route file.

A few outpost routes have been roughly documented in Afghanistan_CP_Reference.lua and CentralAfrica_CP_Reference.lua in the Helpful User Resources folder, but the user will need to learn the routes in-game if they wish to have precise patrols for their sideops (although sideops with randomly assigned routes work well enough). These are some tips for gathering route information:

• Build a sideop with each soldier assigned to a unique route, the QuickMenu [Down] hotkey will notify the user of the soldier's name. The user can then match the route by the name of the soldier, and take note of how they patrol.
• Use the QuickMenu [Up] hotkey to mark all enemies and set them to Friendly. The user will be able to survey routes easier without interference or having to hunt down every soldier.
• Using the QuickMenu [Right] hotkey will speed up the world timescale, causing soldiers to move along their routes at high speeds. This hotkey will allow the user to quickly learn about where the soldier routes travel.
• Using the QuickMenu [Left] hotkey will toggle the soldiers between their _d_ routes and their _c_ routes. This will allow users to document the soldier's _c_ routes more easily.