
MOAR + Bagels - Ultra lite spawn mod 3.1.6
Created by DewardianDev
176.4K 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…
36.0K 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.1K 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.5K 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.
201 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”.
When using version 3.1.6, do the values I adjust in the config.json file override the “life like” preset? Or do I need to use Bepinex every time I launch the game to change “random” to “custom”?
Because I couldn’t find an option in config files to force the use of the “custom” setting. 
can setup player spawn? i got spawn same place in street more than 20times
only spawn floating guns lol
just realised I dont see boss sturtman in the boss config for woods
Hey, anyone knows how I get rogues to spawn on the mounted guns on the roofs of water treatment plant like in live tarkov? I set exUsec: 100 and went there but not a single one on any roof.
I use standard settings btw.
Max bots: 28
Max bots per zone: 7
edit: Never mind. I made a mistake when I changed the config. Works perfectly now. Roofs full of very evil rogues!
Just played Customs, cleared the crackhouse, was walking away towards the RUAF exfil and got sprayed from the back. Checked in raid review, a PMC spawned 20m behind me, unloaded at me and went on his merry way. A similar thing happened on ground zero, but it was a scav in front of me in Terragroup building. Is there an option to disable spawns in a certain radius around the player?
Have a question about moar and night raids, about sectants, dont see the percentage how to spawn them frequently all nights
Hey there. Love your mod. Wondering if anyone is reporting issues with MOAR and 3.11.4. I have fika installed but there are no bots spawning on the map, just their weapons floating in the air.
Hi, first off, thanks for creating this mod it really adds a new dynamic to the game!
However, I have one big request that would improve the experience drastically: could you please add a boolean condition linked to a TickRate function, or Tied to mission timer itself to check whether the Player PMC is currently in active combat before spawning?
Right now, the AI waves spawn at really inconvenient moments like when I’m peeking, pushing, or engaging an enemy. The subtle stutter caused by the spawn often gets me killed with headshots or eye shots. It’s incredibly frustrating because it feels like the AI spawns exactly at the worst possible times for me.