MOAR + Bagels - Ultra lite spawn mod 3.1.6
Created by DewardianDev
186.6K Downloads
SPT 3.11.4 Compatible
Ultra lite bot spawning mod, that expands spawn points and works great on servers. Highly recommended to be used with SAIN/QB/LB for an immersive live-like experience. Highly configurable. Built for use with FIKA.
Waypoints is now REQUIRED!!
A big thanks goes to DrakiaXYZ!
What is this?
This mod is a bot spawning mod similar to SWAG but it’s focus is on performance.
Although it has a bepinex .dll, this is primarily a server mod; meaning that it works great with FIKA and generally has less stutter/lag spikes..
(3.10 is still what it is though )
Why this over SWAG/Donuts?
This is likely less performance intensive… maybe.
But donuts are great, and they have sprinkles..
Features:
- Expanded spawn locations (over 300 at present)
- New marksman and player spawns included!
- High configurability! Just open the MOAR bepinex f12 menu and read through the tooltips for each options.
- A ton of different presets, and the ability to create your own! (for those with the aptitude)
- Starting PMCS now works with presets out of the box.
- Configure your preset weightings with PresetWeightings.json (server config)
- Configure every maps bosses with the bossConfig.json (server config)
- Configure every maps bot quantities with the mapConfig.json (server config)
- Create your own spawnpoints with a keypress by turning on the advanced config in your bepinex settings.
Note: YOU BREAK THE WARRANTY BY DOING THIS, DO NOT COMPLAIN TO ME!
All of this and MOAR.
**Q: How does MOAR choose it’s spawn locations for bots?
A: The Cascading Wave Spawn Algorithm (think a drop in water):**
MOAR now looks at where you spawn, and roughly makes bots spawn in a ripple outwards from that location.
The result of this means you generally need less bots to have the same amount of action.
Q: How are waves distributed?
A: By default, MOAR now uses wave smoothing to prevent more than one spawn at time.
The quantity of waves is configurable of course, but they now are spaced regularly to provide a smooth, highly performant experience.
The idea is to avoid the client from doing it’s botgen CPU work more than once in a particular period.
What do you mean???
Here’s an example:
The BaseGame/SWAG may look something like this:
Game Starts [wavewawawawavewave ——— wave–– wave————wavewawawa–– wave—————] Game ends
This mod will do the following by comparison, depending on settings:
Game Starts [ wave—wave—wave—wave—wave—wave—wave———wave———wave———wave—] Game ends
Basically you will have a smooth wave spread, with a leaning to the beginning of the raid by default (*cough* configurable…).
The above wave behaviour is dynamic, thus true for extended raid times (which is configurable under the map settings).
Moar now works with extended raid times out of the box, without configuration needed.
It will adjust if your raid time values are too long and let you know what it has changed in the console.
If you’re really digging the mod, consider supporting my caffeine addiction ☕:
Compatibility:
Should work with most things except for OTHER SPAWN MODS
Known Incompatibilities:
Realism’s Spawn changes
Turn of spawn changes in Realism if using that.
Raid Overhaul’ boss
Turn the boss off in the config to prevent errors.
HIGHLY RECOMMENDED MODS:
So bots aren’t dumb
So bots loot and move around more
So bots quest and move across the map
My other mods that go well with MOAR:
So bots level with you (like a real wipe)
So one can adjust the tedium of quests
If using SWAG/donuts, choose this or that.
=== INSTALL STEPS ===
1. Download the zip from the link on this mod page
2. Extract to your SPT folder
3. Play
Feel free to install the mod and play the game without ever looking at the config, just adjust what you like in the Bepinex.
==== Main Config (config.json) ====
This is the main config that is affected by presets.
The Bepinex basically controls this.
==== Boss Settings (bossConfig.json) ====
Change boss spawn settings.
==== Map Settings (mapConfig.json) ====
Map specific settings
Reference for hotzones:
Map Zones
3.1.1 Default Spawn Locations and BotZoneNames
==== Preset Settings (Presets.json) ====
Lists the presets and their overrides that will be applied to the the config above when said preset is enabled.
==== Preset Weightings (PresetWeightings.json) ====
This is a list of the presets from the presets.json, with relative (to eachother) weights (this controls how often each is seen).
This basically controls the “Random Preset” mode that runs default for MOAR
I’ll update this some day with more some day…
45.4K Downloads
The “MOAR PRESETS” update!
-
Added quite a few new presets to try out!
REMEMBER, you CAN set the random preset weightings in the presetWeighting config
(think of these numbers as tickets added to a bucket and you randomly pull one out).
Set any preset you don’t want used when on random to 0.
Fika users: Set all to 0 except for the one you want to effectively have that be set on server.
Spt users: just select the preset in your bepinex menu if there is one you prefer. -
Updated a number of configs to help with performance
-
Updated Partizan spawn logic (He can now spawn anytime, properly).
-
All bossConfig changes that are off of default will print to server, feel free to go update the bossConfig.json if you don’t like these.
-
Reduced total bots on certain maps (lighthouse/streets) these are overrides that dramatically help performance.
If you don’t like good frames, adjust those in the mapConfig.json for each map.
That’s all for now.
14.2K Downloads
The “Must spawn faster” update
- Increases scav spawns a bit across the board
- Bumps up initial spawning speed for both scavs/pmcs (too many empty starts
Beware: You may have bots close on spawn (within 15 seconds).
YOU HAVE BEEN WARNED
- A small change in match calculation fixed a bug in smooth wave generation (this was one of the fixes for the above).
That’s all for now!
3.6K Downloads
The “spawn cascade” update
- Enforces cascade logic
- Reduces min spawn for spawnpoints (may fix spawning on certain small maps)
- Improves chances of seeing action early.
That’s all for now.
236 Downloads
Small config/spawn update
- Added a few more spawnpoints to maps
- Adjusted the culling algo so scavs can group up a bit more
- Narrowed the spawn range for players so cascade should be more accurate.
1.3K Downloads
Major bug fix for Bagels (custom spawns)
- Implements a patch that MOAR was relying on from SAIN.
- Improves reliability of custom spawns and having spawns be successful in general.
- Snipers still broken and absent from this release, will be working on them soon.
That’s all for now.
1.8K Downloads
Small Bug fix
- Removes additional pmc spawns that may have been sneaking in.
That’s all for now!
Details
-
GUID
Not Available
-
License
-
Source Code

For FAQ’s sake, please read, before commenting:
I don’t understand difficulty something something… ?
Moar sets the difficulty preset (easy/medium/hard/impossible), sain or spt decides the bots behaviour from there.
Yes this works fine with SAIN, and is intended to be used with it.
I changed pre-raid settings something something… ?
Don’t! Moar has it’s own controls to disable bosses or handle difficulty. If you use the pre-raid menu, do not post about your broken game here.
I don’t understand Bepinex something something!!?
Hover over the value in the bepinex and read the tooltip.
I changed Something something in the bepinex but its not working grrr!?
>>>>>> Hit “**Save”** at the bottom of the bepinex <<<<<<
FIKA something not saving bepinex something something!?
For fika, the configuration is saved in memory on the server, the idea being that fika servers should be run on dedicated machines and have long up time.
If you want your settings to persist through restart and use FIKA, make sure to set those defaults in config.json/presetWeightings
**Bepinex version is saying XX but I downloaded latest? I forgot to update the version for the client mod, if you downloaded latest, this is fine.
The client mod requires changes rarely, thus I don’t always repackage it (updating the version).
*Something something..server configs broken, I’m no Coder something 不明白 .json !%#@?
If you are attempting to adjust the server configs and are not technically inclined please take a look at this handy tutorial.
*My CPU is dying with maxBotCap of 25 and/or startingPMCs turned on ANGRY something…!
People love the idea of startingPmcs as this is what live is like, what it actually does is forces your potato CPU to spawn (the most cpu intensive operation in spt) all of the pmcs for the entire raid at the same time (or over the first few minutes in the case of Moar), to add to this, all bosses, there followers, rogues, raiders, are already using this period to smash your potato CPU to bits.
When you spawn all of the pmcs at once, those pmcs will then go forth to murder each other and whatever other bots have spawned on the map (much like live), further heel smashing your already mashed potato cpu into the dirt.
I would suggest leaving startingPmcs off if you don’t have a cpu with X3D in the name, or if you do not want the majority of your pmcs to die off in the first 10 minutes of the raid, or if you do not like finding piles of bodies around the map.
If you still have performance issues:
An alternative to turning off starting pmcs would be to reduce the maxBotCap, but be aware, pmcs/bosses will blast through that limit, meaning you will have a harder time finding marksman/scavs early game if you do both turn on startingPmcs AND turn down the maxBotCap.
Thus, I recommend only reducing maxBotCap if startingPmcs is already off, pmcs will still largely spawn in the first 10 - 15 minutes by default.
One can also set the maxBotCap via the mapConfig.json per map if so desired.
Extra potato mode:
Some settings to try if you are still having issues.
Change these values in your user/mods/Dewar…Moar/config.json to ensure they are always active.
“pmcWaveDistribution”: 0.5,
(this makes it so pmcs will spawn over the entire period of the map)
“scavWaveDistribution”: 0.3,
(as bosses spawn at the beginning this pushes those initial scav waves a bit later in the raid to balance cpu load).
“maxBotCap”: 18,
(lowest recommended 15)
“maxBotPerZone”: 3,
(lowest recommended 3)
“pmcMaxGroupSize”: 3,
“scavMaxGroupSize”: 3,
Once you open the game, reset the default settings in the bepinex by clicking “reset to default”.
I know we’re not supposed to ask, but I just have to!! - version for 4.0.~ coming?
I’m 99% sure something is wrong with the boss invasion option. I set the chance to 1, but I CONSTANTLY meet foreign bosses everywhere I go, sometimes more than one. There’s only 10 bosses in Tarkov (-1 since almost each map has its own boss) bosses in Tarkov, and if we apply the 1% chance of spawn to each one individually, the chance of NONE of the invading bosses spawning should be about 91%, but that’s not what I’m seeing. This is obviously excluding the raids where an invasion preset is selected, as that drastically increases the chances.
What a dumpster fire of a mod
Hey guys. I just reinstalled 3.11 and for some reason when I use MOAR no bots spawn except for the boss on that map. Im not getting any errors in the console too. This is my mod list, maybe someone can spot a mod that is incompatible: SVM,WTT,brightlasers,scorpion,ALP,Painter,pityloot,botcallsigns,latetotheparty,questingsbots,doorbreacher,ERT-Weapons,fika,Hephaestus,toxicbullets,medicalSICC,blackcore,TGC,lessrestrictingheadwear,speedloader,olympus,Priscilu+specialweapons,Lootingbots,dynamicmaps,realism,uifixes,markedroomloot,makeshotgunsgreatagain,VCQL,SAIN,bullettime,waypoints,headshotdarkness,hollywoodfx,actuallyfoundinraid,deadzone,bigbrain,doorrandomizer,traderscrolling,questskipper,visceralcombat.
i just tried your mod and omg im not gonna use anything else for spawns and stuff bec i really appreciate the qol stuff, the best spawn mod on the site
I love the cascading spawn system of this, but i also like playing with SPT realism, i understand they have compatibility issues. My only issue with MOAR is the boss spawns, is it possible to turn off any tweaks/changes MOAR makes to boss spawning? I assume the most direct way is to just readjust the config spawn chances back to normal, put realism above higher in the load order, and pray that doesn’t mess up the cascading spawn. I’m just tired of the lack of action in my raids..
Hey guys, quick question. I’m trying to find the optimal balance between smooth performance and FPS. I have an insanely powerful PC with a 9800X3D and a 9070XT, and I play in 2K with excellent FPS. However, I want my framerate to stay perfectly smooth and stable at around 120–140 FPS even during heavy firefights.
Here’s what I’m interested in: How can I make it so that AI doesn’t spawn farther than 450 meters away? I want them to always appear relatively close. I’m not interested in having enemies spawn 800 meters away instead of nearby — I’d rather have, say, 12 enemies within 450 meters than 30 enemies 800+ meters away.
Hello! I am very thankfull to you for your mod, but can’t buy u coffee from Russia( Can u please answer me. At 3.11.4 if Bully spawns on Customs there will be only a few bots on the map (i had 1 PMC and 8 scav’s only for all game even after i killed the boss). I had “More Scavs and PMCs Preset”. So I understand that because of the boss it’s very hard for PC to calculate more bots, but I don’t understand why no scavs or pmcs spawning after the death of Bully. Raid feals so peacefull(