What you need

• A working SPT 4.x install.
• This mod.
• The mod turned on in its config (see below).

If you use other mods that change session end screens, the main menu, or stash UI, list them when you report a problem.

Install

1. Download the release ZIP — the filename looks like Softwyx.CareerLog-1.0.199.zip (the version number changes each release).
2. Extract it so that your game folder contains:
   • BepInEx\plugins\Softwyx.CareerLog\Softwyx.CareerLog.dll
   • BepInEx\plugins\Softwyx.CareerLog\locales\
   • BepInEx\plugins\Softwyx.CareerLog\assets\
3. Start the game.

First launch may create:

• BepInEx\config\com.softwyx.careerlog.cfg

Edit while the game is closed, or use Configuration Manager in-game.

After a raid

1. Finish a raid (extract, death, or MIA).
2. Step through RAID MAP (path + markers) then RAID DEBRIEF (loot + counters for that run).
3. Optional: enable vanilla Session statistics in config to see it after the debrief.

Main menu — RECORDS

1. Click RECORDS on the main menu.
2. Use Summary, Financial, and Raid history tabs.
3. Pick a raid for detail and MAP.
4. Filter PMC, Scav, or Combined as needed.

Data saves when the raid ends through the normal session flow. Force-quits may skip that raid.

Settings (overview)

Open Configuration Manager or edit com.softwyx.careerlog.cfg while the game is closed.

More details can be found here.

Delete the config with the game closed to restore defaults.

What you can expect to see

Previews: HERE (17MB)

Known issues / quirks

1. Map missing for a location — Some maps may show a message that the image is unavailable; movement and markers may still be saved.
2. Scav runs — Scav raids are recorded and tagged; they are stored under your PMC profile id (for convenience).
3. Bring-in gear vs looted gear — Loot stats and markers try to ignore gear you brought into the raid; edge cases (stacks, containers, quest items) may still look odd in rare situations.
4. Other session-end or menu UI mods — Best-effort compatibility. If something breaks, test with only Career Log + SPT essentials.

How to report a bug or ask for help

1. Mod version — LogOutput.log, line with Career Log / [CLG] and version.
2. Game / SPT — Version numbers if you know them.
3. What happened — One sentence.
4. Steps — Map, side, outcome, buttons clicked.
5. Other mods — Especially UI, session end, economy, maps.
6. Logs — BepInEx\LogOutput.log (game closed).

If the mod you are using is not signed by me then it isn’t from me and I can’t help you with it.

Use the download site’s issue tracker or comments. Do not email about mods.

This document will use Mcs as the abbreviation for Miyako Carry Service; you will be referred to as McsLeadPlayer, and the AI teammates generated by Mcs will be referred to as McsBotPlayer.

Supports full customization of McsBotPlayer equipment through Mcs Inventory Mode, supports generating any type of AI as a McsBotPlayer, even AI types provided by other mods, supports McsBotPlayers picking up specified loot, supports commanding McsBotPlayers through the command system, compatible with SAIN, compatible with Fika.

In Fika multiplayer, each player can have their own McsBotPlayer squad.

Allows any type of AI to become your teammate, even Bosses

You can even generate AI types provided by third-party mods such as Black Division Home, UNTAR Go Home!, RUAF Come Home!, as long as your configuration file is correct.

Installation

1. Place the folder located in the downloaded zip into your main SPT folder.
2. Mod will be activated by default.

How To Generate McsBotPlayer

Mcs mimics a carry service in the gaming industry. In this process, you need to select the desired service, place an order and pay, and play together with the player who comes to serve you. Therefore, Mcs provides a trader Tsukiyuki Miyako to handle all these actions

Currently Mcs does not provide indefinite service. When the service period you set expires, McsBotPlayer will automatically delete the friend.

How to Customize McsBotPlayer Equipment

1. You need to have a McsBotPlayer that has been added as a friend.
2. Open the Invite to group interface from the bottom left corner of the bottom bar.
3. Right-click on the McsBotPlayer to bring up the right-click menu, select OPEN INVENTORY.
4. At this point, you will enter Mcs Inventory Mode.
5. In Mcs Inventory Mode, you can customize the McsBotPlayer’s equipment through operations exactly the same as normal gameplay.
6. When entering Mcs Inventory Mode, the Miyako trader will provide all items for purchase at 1 ruble
7. To return to the main character, there are two ways: one is to right-click on the McsBotPlayer through the Invite to group interface again and select RETURN TO MAIN CHARACTER; the other is to directly click the green Mcs Inventory Mode button on the bottom bar, which can also return to the main character.

1. Mcs Inventory Mode modifies the McsBotPlayer‘s equipment only in PMC mode. As is well known, PMC mode and SCAV mode are two different characters. According to game settings, you cannot control the SCAV character’s equipment, so Mcs will also maintain this setting.

2. The McsBotPlayer‘s friend slot has a time limit and will automatically delete the friend when it expires. If you don’t want the carefully adjusted McsBotPlayer equipment to be deleted due to expiration, it is recommended to order a McsBotPlayer for a longer period of time.

How to Get Loot Picked Up by McsBotPlayers in Raid

When a McsBotPlayer picks up target loot, to get items from the McsBotPlayer besides looting the body after the McsBotPlayer dies, you can also use the OPEN INVENTORY command on a single McsBotPlayer through the Mcs command menu to remotely open the McsBotPlayer’s backpack while the McsBotPlayer is still alive.

According to game settings, McsBotPlayer mimics a real player, so after they pick up loot, if you don’t personally take it, everything will not belong to you after the raid ends.

If you want it, then you’ll have to take it, as you have already known.

How to Customize McsBotPlayer Types

1. Start the server once first, and spawntype.json will be generated under MiyakoCarryServiceServer/configs.
2. If you don’t understand the following content, it’s recommended not to mess around with it yourself. Incorrect modifications will cause errors. If you really want to change it, read on. You can also leave it to AI to do it. If it’s still changed incorrectly, just delete spawntype.json and restart the server, and a new file will be generated again.
3. First, you need to know the JSON format rules. It’s best to use an editor like VS Code that can check JSON format.
4. Then you need to know the WildSpawnType names of AI provided by third-party mods or built-in to the original game.
5. Take Black Division Home as an example. It provides a Black Division WildSpawnType: blackDivAssault.
6. Now you need to add another type in the correct format in spawntype.json.

{
    "WildSpawnType": "sectantOni",
    "IsBoss": true,
    "DisplayName": "Oni"
}, 
    // The above is the EFT native WildSpawnType. When adding new types later, 
    // you need to bring `,` after `}`.
{
    "WildSpawnType": "blackDivAssault", 
    // Write the WildSpawnType name here.
    "IsBoss": false, 
    // Whether to serve as a Boss type. 
    // When using the help command, a `[Boss]` prefix will be added for this type.
    "DisplayName": "Black Division Assault" 
    // Display name. When using the help command, 
    // only this name will be displayed, not the WildSpawnType name.
} 
    // The last `}` should not have `,`.

// --------------------------------------------

{
    "WildSpawnType": "xxxWildSpawnType", 
    "IsBoss": false, 
    "DisplayName": "xxxDisplayName",
    "BrainName": "xxxBrainName" 
    // If this third-party mod's WildSpawnType does not use the EFT native brain, 
    // you need to additionally fill in a BrainName. 
    // As for what this BrainName is called, 
    // you need to find it yourself from this mod.
}

7. After ensuring the JSON format is correct and the data is filled in correctly, restart the server. At this time, use the help command in the MESSENGER interface with the Miyako trader, and all types will be displayed in the list of available types.
8. If an exception occurs when generating the customized type, you will receive an error reminder in server log and it will change to generate the default pmc type McsBotPlayer. At this time, you need to check whether the customized type you filled in is incorrect.

Basic

• Enable Looting

Whether Mcs Player will attempt to loot items.

• Price Threshold

Loot below this price will be ignored.

• Loot Name Keyword

Keywords are substrings contained in an item’s full or abbreviated name. Multiple keywords can be separated using “||”, “,” or “，”.

• Loot Keyword Items

Whether McsBotPlayer will attempt to loot keyword items

• Blocked Item Types

Supports select all, deselect all: Ammo, Barter, Info, Container, Food, Backpack, Goggles, Pocket, Tactical Vest, Armor, Grenade, Headphone, Keys, Knife, Magazine, Meds, Mod, Special, Weapon, Other

When Fika is installed, adjusting settings in raid will automatically sync to the host

Command

MemberCommand

• Report Enemy Position

If McsBotPlayer is currently in combat, command McsBotPlayer to report known enemy positions.

• Regroup

If McsBotPlayer is not currently in combat, command McsBotPlayer to follow the McsLeadPlayer.

• Go To

If McsBotPlayer is not currently in combat, command McsBotPlayer to go to a specified location.

• Hold Position

If McsBotPlayer is not currently in combat, command McsBotPlayer to stay in place.

• Force Teleport

Clear McsBotPlayer’s aggro and attempt to teleport them to current location.

• Open Inventory

Remotely open McsBotPlayer’s inventory remotely, used to transfer loot they have picked up.

TeamCommand

• Team Report Enemy Position

If there are McsBotPlayers in the team currently in combat, command McsBotPlayers to report known enemy positions.

• Team Regroup

If there are McsBotPlayers in the team not currently in combat, command McsBotPlayers to follow the McsLeadPlayer.

• Team Go To

If there are McsBotPlayers in the team not currently in combat, command McsBotPlayers to go to a specified location.

• Team Hold Position

If there are McsBotPlayers in the team not currently in combat, command McsBotPlayers to stay in place.

• Team Force Teleport

Clear aggro for all team McsBotPlayers and attempt to teleport all of them to current location.

When SAIN is installed, Force Teleport will be automatically disabled.

The command system also works normally during Fika multiplayer.

Player

• Teammate Highlight

Whether to highlight all McsBotPlayer characters in raid.

• Teammate Highlight Hotkey

• Teammate Highlight Color

• Enable Mcs Subtitles

Whether to use subtitles to display McsBotPlayer reports.

• English (AI Translate)
• 简体中文
• русский язык (Contributed by NotDifficult)

EFT Native

• marksman
• assault
• bossTest
• bossBully (Mcs default support)
• followerTest
• followerBully
• bossKilla (Mcs default support)
• bossKojaniy (Mcs default support)
• followerKojaniy
• pmcBot (Mcs default support)
• cursedAssault
• bossGluhar (Mcs default support)
• followerGluharAssault
• followerGluharSecurity
• followerGluharScout
• followerGluharSnipe
• followerSanitar
• bossSanitar (Mcs default support)
• test
• assaultGroup
• sectantWarrior
• sectantPriest
• bossTagilla (Mcs default support)
• followerTagilla
• exUsec (Mcs default support)
• gifter
• bossKnight (Mcs default support)
• followerBigPipe (Mcs default support)
• followerBirdEye (Mcs default support)
• bossZryachiy (Mcs default support)
• followerZryachiy
• bossBoar (Mcs default support)
• followerBoar
• arenaFighter
• arenaFighterEvent
• bossBoarSniper
• crazyAssaultEvent
• peacefullZryachiyEvent
• sectactPriestEvent
• ravangeZryachiyEvent
• followerBoarClose1
• followerBoarClose2
• bossKolontay (Mcs default support)
• followerKolontayAssault
• followerKolontaySecurity
• shooterBTR
• bossPartisan (Mcs default support)
• spiritWinter
• spiritSpring
• peacemaker
• pmcBEAR (Mcs default support)
• pmcUSEC (Mcs default support)
• skier
• sectantPredvestnik (Mcs default support)
• sectantPrizrak (Mcs default support)
• sectantOni (Mcs default support)
• infectedAssault (Mcs default support)
• infectedPmc (Mcs default support)
• infectedCivil
• infectedLaborant
• infectedTagilla (Mcs default support)
• bossTagillaAgro (Mcs default support)
• bossKillaAgro (Mcs default support)
• tagillaHelperAgro

Black Division Home

• blackDivLead
• blackDivAssault
• blackDivBreacher
• blackDivSupport

UNTAR Go Home!

• followeruntar
• bossuntarlead
• followeruntarmarksman
• bossuntaroffice

RUAF Come Home!

• ruafRifleman
• ruafRiflemanSenior
• ruafAutorifleman
• ruafGrenadier
• ruafMarksman
• ruafMachinegunner

Every bot squad in your raid rolls a small list of goals at spawn:

• Loot a rich zone - clean out a high-value area, room by room
• Hunt for fights - anchor a known PvP hotspot, prowl for kills
• Run a quest - visit a real EFT quest trigger like a player would

How they pursue those goals depends on their SAIN personality:

• Rats / Cowards - careful, low-risk, loot a lot, extract early
• Average - balanced, will do a bit of everything
• Chads / GigaChads - aggressive, hunt PvP, skip cheap loot, push extracts
• Timmys - wander a bit, make weird picks, get to the wrong room sometimes

Squads coordinate: the leader picks the target, the rest spread to nearby loot or cover. They open locked doors (sometimes), chain-loot adjacent containers, and credit the right teammate when the corpse needs looting.

They extract when one of three things happens: they’ve looted enough money, they’ve finished all their goals, or the raid is getting late.

Each squad’s main objectives live in cells on the map (a coarse grid). Once the squad’s leader picks an anchor, the rest of the system works in two layers:

Main anchor - the squad’s current focus. One member (the leader by default) walks straight to it. For a Kills main this is a PvP hotspot; for a LootValue main it’s a specific high-value POI in the target cell; for a Quest main it’s the trigger point of a real EFT quest.

Splinter targets - while the leader handles the anchor, the other members fan out to nearby POIs inside the same cell (loose loot, corpses, containers, synthetic patrol points). Each splinter is picked around the member’s own position with a random reservoir sample, so a 4-PMC squad naturally ends up working a small area without all stacking on one spot. A splinter is kept across anchor flips if it’s still in range of the new anchor - bots don’t yo-yo between random POIs when the leader chain-loots the next container two metres away.

Own-kill credit - when a squad scores a kill, the specific member that landed it is the one routed straight to the corpse on the next dispatch, not a random teammate. The killer loots the body they dropped.

Coverage roll - on entering a high-value loot cell, each POI inside the cell rolls against the squad’s coverage value (per-personality: Cautious 85-95%, Average 65-75%, Aggressive 50-60%, GigaChad 30-45%). POIs that lose the roll are quietly skipped so the squad never vacuums the room 100%, like a real player who missed a few items.

The looting layer is custom, built straight on top of BSG’s vanilla bot pickup APIs. It handles containers, corpses and loose world items, with a focus on making the bots feel like real players rather than vacuum cleaners.

Per-bot value gate (PMCs and PlayerScavs)

• Each PMC has its own loot threshold rolled from its SAIN personality: Chad ~15k/slot, Average ~10k/slot, Cautious (Rat/Coward) ~5k/slot, GigaChad ~20k/slot, Timmy 0 (everything goes). PlayerScavs fall back to a 5k default.
• Value is judged per inventory slot (handbook price ÷ item size), so a tiny key worth 50k beats a 60k backpack that takes 15 slots.
• A Chad walking past a 5k mag won’t bother; a Rat in the same squad will happily grab it.

Bot scavs: opportunistic random pickups

• AI scavs don’t use a value threshold. They roll a per-item dice (default 30% chance to grab) - matches the vanilla feel where scavs pick up the odd item but don’t deliberately empty a corpse.
• PlayerScavs are excluded from this and use the PMC-style threshold path.

Smart squad memory

• When a Chad opens a container and rejects everything, the same POI is added to his personal skip list - he won’t be sent back. His Chad teammates also skip it (same threshold). But the squad’s Rat can still be dispatched there and clean up what the Chad refused.
• The squad’s own blacklist (a hard “we’re done here”) only triggers when items were actually taken, when the POI was empty, or on transaction failures - never on a pure value rejection.

Always-pick items

• Currency stacks, frag grenades, and dogtags bypass both the value gate and the scav random roll. A real player never walks past a dogtag.

Realistic search timing

• Containers play an open/close animation (~2.5s) with the bot kneeling in front of the lid.
• Corpses are drained on two interleaved tracks: a visible track (helmet, weapons, scabbard, etc., grabbed sequentially with ~0.8s between each) and a search track (vest, armour, backpack, pockets, one slot at a time with progressive per-item reveal: 1.5s initial + 0.4s per extra item, capped at 8s).
• Slot order is randomised so the bot doesn’t always go backpack-first, vest-second, pockets-third.
• Loose items trigger the kneel-and-grab animation per pickup.

Drain order

• Items inside grid containers (wallets, money cases, rigs, backpacks, pockets) are emptied inside-out: cash and contents first, then the empty wrapper.
• Weapon + mods chains drain root-first (the weapon itself, then any detachable mods), same for armour + plates.

Mod filtering on weapons

• Only attachments flagged as “removable in raid” (scopes, mags, grips, silencers, foregrips, mounts, charging handles, dust covers, sights, lasers, lamps) are considered. Barrels, buttstocks, handguards and receivers are dropped from the queue - nobody disassembles a rifle mid-firefight.

Corpse exclusions

• PMC corpses keep their melee weapon (Scabbard slot) on the body, same as live EFT. Scav corpses are fully lootable.
• Secured containers are never touched, on any corpse.

Chain-loot sweep

• After successfully looting a POI, the bot looks for nearby loose items or corpses within a short radius and chains to them directly - mirrors the way a player picks up adjacent items before walking away.
• Same-floor preference: a candidate two metres away on the floor above loses to one ten metres away on the same floor, so the bot doesn’t yo-yo between basement and lobby on Resort.
• Each sweep candidate gets its own coverage roll.

1. Install dependencies first:
   • BigBrain by DrakiaXYZ
   • Waypoints - Expanded Navmesh
   • SAIN
2. Extract the zip in your SPT root folder.
3. Launch the game. You’ll see ORBIT 1.0.0 in the bottom-left version label when it’s loaded.

All tuning lives in the F12 menu - open it in-game and tweak live.

Two recommended SAIN tweaks:

• Tweak SAIN personality chances (see the next tab).
• Disable SAIN’s extract layer so it doesn’t fight ORBIT’s extract logic. Open BepInEx/plugins/SAIN/Presets/<your_preset>/GlobalSettings.json and set:

"Extract": {
  "SAIN_EXTRACT_TOGGLE": false
}

ORBIT was tuned around a specific personality distribution. SAIN’s own defaults work fine, but if you want raids that match what I tested against, go into SAIN’s F12 config under Personality → Assignment and set:

Set Can be randomly assigned to True for each one.

This gives roughly a third of your PMCs interesting personalities - the distribution ORBIT was built around.

Note for Twitch Player users: Twitch Player sets several personalities chance to 0 by default, so it’s important to apply the SAIN settings as above.

ORBIT supports only one other AI mod: SAIN and is REQUIRED

Any other AI / bot-behaviour mod will either fight ORBIT for control or duplicate work it already does. Don’t install them alongside ORBIT.

QuestingBot

• QuestingBots actually simulates quests - bots plant items, hold zones for the required time, etc.
• ORBIT is simpler: bots just route to the quest trigger location, no real quest mechanics.
• Both want to assign the same bot a quest at the same time → conflict. Pick one.

Phobos

• ORBIT is built on Phobos’s foundations, same advection field, same cell dispatch logic, same squad movement model. Running both means two systems trying to move the same bots.

LootingBots

• ORBIT has its own loot pipeline driving BSG vanilla pickup APIs, with per-personality value thresholds. Running both means two systems racing to loot the same containers.

Any other “AI overhaul” mod

• If a mod replaces bot brain logic, dispatches bots somewhere, or controls looting / extracting / questing, assume it conflicts unless proven otherwise.

AI Limiter / Bot Culling mods

• Anything that deactivates, pauses, freezes, or culls bots while they’re still alive (typically to save CPU when bots are off-screen) breaks ORBIT’s core loop. ORBIT relies on every squad running their full lifecycle in the background: patrolling, looting, fighting, extracting, even when you’re nowhere near them. The moment a bot gets deactivated mid-objective, it never reaches the next waypoint, never engages, never extracts. No support planned on the ORBIT side for now, a built-in degraded-tickrate option for off-screen squads is on the roadmap as a potential future workaround.

Bots freeze / stand still / weird behaviour

• Check for AI-limiter / bot-culling mods (see Unsupported Mods).
• If you’ve extended raid duration via SVM, RaidOverhaul, Custom Raid Times etc., test with vanilla raid times. Long raids have been reported to cause odd bot behaviour.
• If you have ABPS, worth trying to delete its config file and let it regenerate from defaults. A stale ABPS config has been reported to clash.

If the above doesn’t help → 50/50 method

The 50/50 method is the canonical SPT way to pin down a mod conflict: disable half your mods, test the raid, see if the issue persists, split again, repeat until the culprit is isolated. Tedious but reliable.

If you’re going to report the issue

Quoting Shynd:

When reporting aberrant behavior to a mod dev it is best to do so with a much smaller subset of your normal mods — for ORBIT I would have just ABPS / SAIN / ORBIT — and with nothing changed in SVM or anything else. Each individual person here has a functionally unique mod pack. Let’s try to make it as similar as possible before trying to help fix issues that may only occur for you specifically.

So before pinging me: try to reproduce the issue with just ORBIT + SAIN + BigBrain + Waypoints + ABPS and default configs across the board. If the issue still reproduces there, then I have something I can actually act on.

Still stuck?

Drop by the ORBIT thread or the SPT 4.0 support channel.

Spawn / loadout mods are fine and actually recommended, they shape who spawns and what gear they bring, while ORBIT decides where they go and what they do. The two layers don’t fight each other.

• SAIN — REQUIRED. ORBIT plugs into SAIN’s personality system; without it the mod won’t load.
• APBS - progression-based bot loadouts. Recommended.
• ABPS - Configurable spawn mod. Recommended.
• Other pure spawn / loadout / loot-table mods should be safe too.

No ETA, no promises, but on the list:

Behaviour

• Members can extract alone if they personally hit their loot threshold
• Squads can decide to camp + ambush instead of always roaming
• Squad rally, when one member starts taking fire, the rest break from their current objective and bee-line to support (currently each bot reacts to combat individually via SAIN, so an isolated teammate can get gunned down while squadmates have already exited combat on their end)
• Smarter movement - checking corners, scanning the rear, less straight-line dashing
• Less static regrouping (bots are easy 1-taps while waiting for squadmates)
• Post-combat self-heal if meds are in inventory
• Squad splitting with radio comms
• New personalities
• Detect bots spawned on isolated navmesh islands (e.g. near Streets transits, Factory silo) and teleport them once to a valid spot nearby so they stay in the raid instead of standing still until raid end. TP destination must respect a safety radius from the player (and other bots) so the rescue can’t drop a bot right in front of someone
• Optional player-attraction toggle (bring it back from Phobos) - pulls bots toward the player for more action, off by default. Useful for “kill X scavs in an area” quests, viewership runs, etc.
• Crouch when looting a body in the open to minimise silhouette
• Weapon-type → behaviour archetype hint (CQB-leaning loadout pushes harder, sniper loadout stays back) driven by MOA + RPM + scope presence, biasing POI selection so a Mosin squad doesn’t get routed into Resort interiors
• Cross-raid player-movement heatmap: aggregate the player positions raid-review already logs into a per-map occurrence map, then weight squad dispatch toward those hotspots so the side routes a player habitually rats through stop being safe over time (suggested by Fiodor on Discord)
• Built-in degraded-tickrate mode for off-screen / far-from-player squads: runs the dispatch / loot / extract loops at a lower frequency to reclaim CPU on lower-end machines without flat-out deactivating bots the way external AI-limiter mods do. Goal: keep the “full lifecycle” guarantee while trying to help out low-end PCs
• Permanent door unlocks after a bot picks the lock, currently unlocks are passage-only and the door relocks behind the bot, which means a player chasing a bot through a high-value-loot door still needs their own key. Once a force-unlock roll succeeds, the door should stay open for the whole raid (or unlock the lock and leave it shut, depending on door state) so everyone benefits from that bot’s pick
• Investigate why extended raid duration breaks bot behaviour. Users running SVM / RaidOverhaul / Custom Raid Times with longer-than-vanilla raid lengths consistently report bots going inert, freezing, or behaving erratically (multiple reports). Currently in Troubleshooting as a “test with vanilla raid times first” recommendation, but the underlying cause isn’t understood. Worth tracing what state ORBIT (or a dependency) accumulates over time that fails past the vanilla window

Objectives

• “Marked-key loot rush” for high-tier squads
• “Spawn rush” for the most aggressive personalities
• “Boss hunting”
• Airdrop / helicopter crash / BTR objectives: squads slow-approach the drop zone, hold position at a nearby vantage for a few minutes (ambush window), then close in and loot. Mimics how players treat airdrops in live, nobody walks straight to the smoke.
• Multi-step objectives (activate → loot/extract):
  • Interchange Kiba (disable alarm → loot)
  • Interchange ULTRA (power on → loot)
  • Interchange Object #21WS keycard container (power on → loot)
  • Interchange Object #11SR room (power on → toilet switch → loot → extract inside)
  • Customs scav-base exfil (power on → extract)
  • Reserve bunker exfil (switch → extract)
  • Reserve D-2 (switch 1 → door switch → extract)

Extracts

• WorldEvent exfils (Reserve / Customs switch-gated)
• Train exfil (Armored Train availability window)
• “Drop backpack” exfils (Empty / EmptyOrSize) - usable when bot has no backpack, OR wounded bots drop the bag and use them anyway
• HasItem (RedRebel-style - bot must own a Red Rebel in inventory, ignore the paracord and WearsItem gear constraints entirely)
• Fallback to next-closest exfil if the chosen one is unreachable

Looting (post-MVP)

• In-raid weapon swap when bots find something strictly better (gun + mods + matching mags + ammo carried together)
• In-raid armour / helmet / rig / headwear swap, with item transfer from the old rig into the new one
• Magazine compatibility check (caliber vs the bot’s current weapon) before considering a mag worth taking
• Spare ammo preload to the secure container instead of crowding the main inventory
• Strip-then-throw on a weapon the bot is about to discard - keep the scope / silencer / grip / laser, drop the rest
• Post-loot inventory sort so the grid stays usable as the bot fills up
• Teammates can grab a dead squadmate’s spawn gear and stash it somewhere quiet - simulates a real squad taking care of their fallen friends’ stuff
• Stack-aware pricing (currency / ammo stacks evaluated as bulk value, not single-unit)

Tuning

• Faction takeover split: patrols → ORBIT, checkpoints → vanilla (RUAF / UNTAR / BlackDivision)
• F12 toggle to opt Raiders out of ORBIT entirely (they currently get the brain layer with no main objectives or loot, just patrol idle)
• Flip the faction-control model to opt-IN instead of opt-OUT, ORBIT only controls explicitly enabled bot types, safer for future custom-bot mods

Animations / polish

• Keycard / key swipe animation for PMC bots opening locked rooms (currently they call the Unlock function instantly with no anim, should walk to the reader and play the swipe like a player)

Bugs to fix

• Bots phantom-walking through closed doors instead of triggering the open animation (door-open condition misfires in some cases)

• 1.0.0 is the first public release - a few rough edges are expected. Bug reports and feedback on the Discord thread are very welcome.
• Most Reserve exfils require switches ORBIT doesn’t operate yet - bots there mostly stay until killed or raid end.
• Bots phantom-walk through closed doors - in some cases the door-open trigger doesn’t fire and the bot passes straight through without animating the open. Reported on Customs three-story side door so far. Investigating.
• Bots walk into minefield - the rebuilt POI generation doesn’t exclude minefield zones yet, so bots can be routed straight into them. Fix planned.
• Possible interaction with CactusPie’s “Transfer Loot Into Container Automatically” mod - reported symptom: items a bot loots end up in YOUR tagged containers (SICC case, etc.). Best theory at the moment is that ORBIT routes pickups through BSG vanilla APIs (same path as the player), so a mod hooking those APIs may end up applying its logic to bot pickups too. Investigating.
• Bots stuck at spawn on isolated navmesh - vanilla SPT quirk where a spawn point lands a bot on a tiny chunk of navmesh disconnected from the rest of the map (Streets near transits, Factory inside the silo, etc.). Shows up more often with ORBIT than pure vanilla because vanilla’s built-in TP rescue is disabled (it was teleporting bots constantly on every unreachable pick). Fix planned: targeted TP rescue that fires only when a bot is genuinely stuck for X seconds.
• Rare stuck bots - usually unstick themselves within a minute. Still iterating.
• Mod conflicts - tested with my own config. Yours may differ. Report anything obviously broken on GitHub.

I want to be upfront: I used Claude as a coding assistant on this mod.

That doesn’t mean it’s vibe-coded slop. I spent days reading the source of Phobos, and built custom debug overlays in Raid Review so I could see what every mod was doing per-frame before writing a single line of ORBIT. I’m the architect; the LLM is a productivity tool - same as a senior dev using Stack Overflow doesn’t make them a fraud.

I have 10+ years of professional dev experience. I know what I’m shipping.

If that’s a dealbreaker for you, I understand - uninstall and move on, no hard feelings. If you can judge a mod on what it does rather than how it was written, give it a try.

A huge thank you to the authors listed below.

• Phobos by janky - the original advection-field cell dispatch that ORBIT is built around (MIT, used with explicit permission - see screenshot below).
• QuestingBot by danW - inspired the quest-routing concept, no code reused.
• LootingBots by Skwizzy and ArchangelWTF - ORBIT started out as a Phobos + LB merge; over time many features were added and the looting layer was rewritten from scratch on top of BSG vanilla APIs to fit ORBIT’s design better. No LB code left in the current release.
• SAIN by Solarint, ArchangelWTF and DrakiaXYZ - without it, no personality system to plug into
• BigBrain by DrakiaXYZ
• The SPT team for an amazing modding framework
• The SPT Discord
• You, for trying the mod

Phobos authorization from Janky:

If ORBIT made your raids more interesting and want to support my work, feel free to buy me a coffee!

All my mods are free and open source. Your support keeps me motivated to create more!

What you need

• A working SPT already set up.
• This mod.
• The mod is turned on in its config (see below).

If other inventory or loot mods are installed, list them when you report a problem; they sometimes interact in odd ways.

Install

1. Download the release ZIP – the filename looks like Softwyx-LootInVicinity-2.14.40.zip (the version number changes each release).
2. Extract it so that your game folder contains:
   • BepInEx\plugins\Softwyx-LootInVicinity\Softwyx-LootInVicinity.dll
3. Start the game.

First launch may create a config file:

• BepInEx\config\com.softwyx.lootinvicinity.cfg

You can edit that file when the game is closed, or use Configuration Manager in-game.

How to use in-game

1. Enter a raid.
2. Open inventory (usually Tab) without opening a world container (body, crate, etc.).
3. On the right, you should see the Nearby Items panel (title may differ if you changed it in config).
4. Drag or quick move loot like any other stash.

Which items appear is set under 3. Scanning in the config (see below).

Settings

Open Configuration Manager in-game, or edit BepInEx\config\com.softwyx.lootinvicinity.cfg while the game is ** closed**.

1. General

• Enabled – master switch.

2. Inventory panel

• Panel title, Hide panel when empty, Append item count to title – how the right column looks.

3. Scanning

• Scan radius (m) – how far around you the list reaches (3 to 6 m). There is always a 1 m wide zone at your feet where items can show up even when they are under other loot or even under the ground.
• Main scan requires line of sight – when on, loot farther out in that radius must be in clear view (walls still block). Other loot piles and bodies on the ground do not count as blocking. The 1 m zone at your feet ignores this setting.
• Max items in panel – cap on how many rows show each time you open Tab inventory.

4. Quest items

• Show quest items in vicinity – whether quest loot appears in the nearby list.
• Route quest items to task stash – when on, moving quest loot from the panel sends it to the quest stash instead of your pockets.

Delete the config file with the game closed to reset all defaults (or reset manually in-game).

Known issues / quirks

These are behaviours players have reported; they may vary with game version or other mods.

1. Quest items in the Nearby list – Drag previews (green/red outlines) sometimes do not match where a quest item can actually go (for example armour vs backpack). Quick move (e.g. Ctrl + click, depending on your setup) is often more reliable than drag for those items.

2. Mods that change inventory, stash, quick move, or loot – Compatibility is best effort. If something breaks after adding another mod, try with only Loot In Vicinity + SPT essentials to narrow it down.

The mod is updated when issues are reproduced and fixed; the list above may shrink or grow in newer versions.

How to report a bug or ask for help

You get faster help if you include detail. Copy/paste this checklist and fill what you can:

1. Mod version – From BepInEx LogOutput.log: the line where Loot In Vicinity loads (it shows v…).

2. Game / SPT – Roughly what you use (example: “SPT 4.0.13, EFT client build …”). Exact numbers help.

3. What happened – One short sentence (e.g. “Tab in raid, panel empty” / “the game froze after I …”).

4. Steps – Numbered list: what you clicked, map, single player or group (FIKA), etc.

5. Other mods – Names of other BepInEx plugins that touch inventory, loot, UI, or progression.

6. Logs – With the game closed:

   • BepInEx\LogOutput.log (and FullLogOutput.log if someone asks for it)

Where to send it – Use the comments section, or issue tracker of the repo which should be listed where you downloaded the mod. Never email me about mods.

Do not send passwords, full Windows usernames, or unrelated personal files. I will try my best to remove any personal data whenever I see it but my availability is not guaranteed!

• Adds foldable behavior to supported weapons and stock setups
• Supports the current FoldThatStock custom stock bundle set
• Uses server-side template patching for foldable behavior and folded inventory size
• Uses client-side bundle overrides for supported stock visuals

• SIG Sauer Folding Knuckle Stock Adapter
• SIG Sauer Telescoping/Folding Stock
• SIG Sauer Thin Side-Folding Stock
• MPX/MCX PMM ULSS stock
• SIG Sauer Locking Stock Hinge Assembly

• SIG MCX .300 Blackout assault rifle
• SIG MPX 9x19 submachine gun

• Player fold/unfold animation is not implemented yet
• Some vanilla stocks that should logically be foldable are yet to be supported
• The current release should be treated as a working base with expanding stock coverage
• Future updates will focus on additional supported stock bundles, visual polish, and animation work

• If you do not want a supported stock visual override, you can remove that stock’s bundle file from BepInEx/plugins/FoldThatStock
• Removing a stock bundle disables the custom visual fold behavior for that supported stock

1. Download the release file
2. Extract it directly into your SPT installation folder
3. Start the game
4. Restart server after changing weapon category settings

Delete:

• SPT/user/mods/FoldThatStock
• BepInEx/plugins/FoldThatStock

If you uninstall the mod, weapons already folded in your profile may keep their saved state until they are updated again by the game.

Note: not all of these are guaranteed to have been changed, these are just what are supported.

Generic

• CanSellOnRagfair (BSG flea blacklist)
• ConflictingItems (item incompatibility)

Weapons, mods

• Accuracy
• Ergonomics
• Loudness
• Recoil
• Velocity
• CameraSnap
• CenterOfImpact
• DeviationCurve
• DeviationMax
• RecoilAngle
• RecolDispersion (not misspelled)
• RecoilForceBack
• RecoilForceUp

Magazines

• CheckTimeModifier
• LoadUnloadModifier
• MalfunctionChance

Ammo

• AmmoAccr (accuracy)
• AmmoRec (recoil)
• ArmorDamage
• BallisticCoeficient
• BulletMassGram
• Damage
• DurabilityBurnModificator
• FragmentationChance
• HeatFactor
• HeavyBleedingDelta
• InitialSpeed
• LightBleedingDelta
• MalfFeedChance
• MalfMisfireChance
• PenetrationChanceObstacle
• PenetrationPower
• PenetrationPowerDiviation (not misspelled)
• StackMaxSize

Armor, rigs, helmets, glasses

• BlindnessProtection
• BlocksEarpiece
• BluntThroughput
• DeafStrength
• MousePenalty (turn speed)
• SpeedPenaltyPercent
• WeaponErgonmicPenalty

Headphones

• AmbientVolume
• CompressorAttack
• CompressorGain
• CompressorRelease
• CompressorThreshold
• RolloffMultiplier
• Distortion
• DryVolume

Nightvision

• DiffuseIntensity
• Intensity
• NoiseIntensity
• NoiseScale

Keys

• MaximumNumberOfUsages

• ExcludeProperties: Each property can be individually excluded. See Properties tab or the included properties.md file for a list of property names.
• IncludeItems: Apply changes only to specified items. Ignores ExcludeItems.
• ExcludeItems: Apply changes to all items except specified.
• AllPrices: Update prices for all items
• UnblacklistedPrices: Update prices only for items that are newly available on the flea market
• UpdateGunsmith: Apply changes to Gunsmith tasks

Use the SPT Item Finder to find item IDs for lists.

• Fully compatible with WTT Content Backport
• Supercedes RuKira’s AttachmentBackport

• Live Flea Prices can keep item prices up to date with live.
• Skipper may be required to complete some Gunsmith or similar tasks.

Data is sourced from tarkov.dev. I’ll do my best to keep the data up to date with notable changes, keep an eye on the date above. Feel free to comment if I’m over a week late to an update.

Live loot value A native-looking label in your inventory screen shows your running total loot value based on current flea market prices, with handbook fallback when flea data isn’t available.

Animated raid summary A polished breakdown screen plays on extraction showing your total value, top 5 finds by price, items looted, and kill count. Click anywhere to dismiss early, or set it to auto-close after a few seconds from the F12 config menu.

Raid History panel A new HISTORY button in the main menu opens a side drawer with a card for every raid this session map, raid type, loot value, and kill summary at a glance. Holds the last 15 raids.

PMC & Scav support PMC raids track only newly acquired items. Scav raids include your spawn loadout in the total.

Flea + handbook fallback Pulls live flea market prices from your SPT server, falls back to handbook values when flea data isn’t available.

PIT Fireteam integration Automatically detects PIT Fireteam and adds a TEAMMATES section to the summary screen with each follower’s kill count also shows squad kills in the history panel. No configuration needed.

Secret easter egg Check the F12 BepInEx config menu.