Fin's AI Tweaks (FAIT)

Fin added a new file:

File

Fin's AI Tweaks (FAIT)

Makes the AI a little harder

Fin

Mar 25th 2023

Quote

This mod changes the AI, gear, and spawning patterns for scavs, PMCs, raiders and boss followers.

The AI changes make the AI more inclined to fire in bursts, act aggressively, and also tries to make their shooting patterns make more sense (eg. They're not very likely to randomly hit you with their first shots, but followup shots rapidly get more accurate, and when they fire in bursts, the bullets in that burst spread out instead of all hitting the exact same spot like a laser beam). There are a variety of configurable settings, from increasing their overall difficulty level to tweaking specifics like recoil or aiming / spotting speed.

The gear changes add more variety to AI loadouts, and have various options such as selecting minimum and maximum armor levels, altering the types of ammo they can use, and even a progressive gear system that syncs AI gear to both the class of bot, and the player level.

The spawning changes are designed to give the player some control over what kinds of bot appear in their raid. By default they greatly increase the number of bots in raids, and also the speed at which they appear. It also adds more varied cultist spawns to maps that can support them.

New as of version 1.21.1: If you have an error and need support, you must include the debug hash that appears in your server (It's also present in your user/logs/server.log file) when FAIT first loads, or your request will be ignored. The only exceptions are errors that prevent this debug hash from appearing.

A note on errors before raids, because I get this question a lot. TL;DR here, and the long explanation below:

TL;DR: The errors aren't harmful, and are just hiccups in weapon randomization where a flawed random weapon is being replaced with a weapon from Tarkov's presets.

Display Spoiler

If you're using the random weapon generation features of this mod, you'll most likely see errors when you load into a raid, saying things along the lines of "This part wasn't compatible with this part", or "This weapon was generated without a magazine". Due to weapon part interdependencies and conflicts, generating weapons without error from a limited selection of parts is difficult to do without significantly slowing the loading process. You can have a barrel that's compatible with only two out of twelve receivers, and only four out of twenty handguards, and each of those barrels is only compatible with three of those handguards, there are handguard / gas block combinations that aren't compatible.. And on and on. When every part is available there's pretty much always at least one combo that'll work no matter what you do, but if you start restricting weapon parts it gets much harder. Your choices for weapon generation boil down to trying to holistically generate the weapon, essentially looking at all the parts at once and making sure they all work with eachother.. Which in practice will basically involve a process very much like generating a few thousand versions of the weapon and then picking one from the list of weapons that don't have errors, or you can build it one part at a time. Upper receiver, barrel, gas block, handguard.. On and on, until you either hit a wall or get a working weapon -Doing it this way means you can run into errors and need to abort, but it also means you're only spending the computational resources to generate one weapon, as opposed to thousands (And I do mean thousands. The barrel / handguard / receiver combo for AR-15 type weapons has more than 400 possible combinations, never mind the gas blocks, stocks and buffer tubes that also have (admittedly lesser) compatibility issues). This is what AKI does, pretty much, and.. Because of this, in certain circumstances AKI's weapon generation code can paint itself into a corner, so to speak, and when it does it throws an error and assigns the bot a weapon from the presets list defined in AKI's globals file. -That's what you're seeing, and it's nothing to worry about.

One final note (for now): While I love and appreciate all your feedback in the comments, it had gotten to a point where there were so many it was slowing the page down, and the site mods had to disable comments for FAIT. -If you'd like to leave a positive comment, reviews are currently the best place for that. I'll try and field people's questions about the mod ion the help thread, but if possible that should remain mostly for technical support issues. Thank you all!

Display More

Fin added a new version:

File

Fin's AI Tweaks (FAIT) 1.9.1 AKI8

Version 1.9 for AKI8.8 servers.

NOT WORKING WITH THE LATEST BLEEDING-EDGE RELEASE

This is completely untested. I can verify that the server loads, but that's as much as I've checked so far. Individual parts of the mod may fail to function properly in the current bleeding-edge release.

Fin

Mar 25th 2021

Quote

Version 1.9 for AKI8.8 servers.

This is completely untested. I can verify that the server loads, but that's as much as I've checked so far. Individual parts of the mod may fail to function properly in the current bleeding-edge release.

Fin added a new version:

File

Fin's AI Tweaks (FAIT) 1.9.3.2.2 AKI7

Version 1.9.3.2.2 for AKI7 servers.

Update 1.9.3.2.2:
-Tiny change to default config file. All spawn changes were being disabled by default. They're now enabled by default, again.
-Fixed a bug where spawns were being incorrectly multiplied

Update 1.9.3.2:
-added spawn multipliers for every map
-should now be fully compatible with the Advanced Custom Weapons mod
---Bots will no longer be able to spawn with magazines that ACW adds to their respective weapons
---Players can still use ACW-added magazines
…

Fin

Mar 25th 2021

Quote

Version 1.9 for AKI7 servers.

Changes:

-Expanded difficulty ranges. Difficulty of bot types can be increased or decreased above / below old limits.

---I can verify this works for values between -3 and 3, but theoretically you could raise the number as high as you wanted.

-Option added to evenly spread out AI spawn locations (Best used when spawning extra waves immediately)

-Expanded blacklist to work with ammunition

-Added options to control how many extra magazines the AI spawns with

-Added options to control how PMCs of the same faction as the player will behave

-Debugging is now enabled by default, and saves files for Customs spawns and PMC loadouts to donottouch/debug

-Enabled reducing hat frequency for all types of bots

-Improved AI spawning with helmet attachments.

---AI is more likely to spawn with NVGS

---Quality of helmet attachments is affected by modQuality

-Performance improvements

Fixes:

-General fixes to spawning.

---disabling useNewSpawnSystem should now completely revert the spawn system to how it was in 1.6.4

Notes:

-Setting modQuality below 10 will cause errors in your server upon beginning a raid. These are caused by improperly generated weapons being replaced with defaults, and are harmless. Raising the modQuality values or disabling moreModVariety should fix the issues, but is not necessary in 99% of cases.

-If you encounter spawning issues, especially no PMC spawns, or entirely empty raids, try setting useNewSpawnSystem to false in the config. The number of bots spawning in your raid will be less controllable, but it seems to fix the problems that some people experience.

Display More

So apparently I don't get notifications when new messages appear in this thread. Sorry for the delay in getting to some of these.

Quote from DizzilyHQ

Hey im new to SPT Aki and i was wondering if i can make this work in spt aki r7 of the thing not sure if its possible and how and what not but i like the idea to have harder scavs.
Same for the Economy Tweaks. i would love to use both of the modfs

Economy tweaks only works with r7, so that shouldn't be a problem, and as long as you download the versions of the AI mod marked as being for AKI7, that should also work just fine for that!

Quote from DizzilyHQ

Hi its me again

So i tried to use this mod and i really like how the bots react and how hard they are. even that you can disable their voices.

but i get like 30 fps less then without this mod. (from 60[vsync] to 30). tried to change bot variables of spawns. used the vanilla spawn thingy and tried all i can think of. any ideas what else i could try?

FPS is largely tied to the number of living bots in your raids, so reducing the amount set to spawn in the config should help improve FPS, though I made some small changes in the latest version that also help things a little bit.

Quote from NugentGL

Should the removevanillaspawns (for scavs and AI) and newspawnsystem be enabled together or not? I had removevanillaspawns enabled and newspawnsystem enabled and had a completely dead Customs raid. I heard no shooting and traversed most of the map without even seeing a single AI.

I think I answered this in the main comments page, but that's probably due to useNewSpawnSystem, unless the config was set to spawn 0 extra waves of bots. You can use them together without errors, though.

Quote from Khadafi

Thank you very much for the new version and espcially for adding the possibility for PMCs of same side to become hostile.

I can also confirm PMCs spawning for me now, even with new spawn system set to true.

But I experienced something strange in the first two rounds I played.

I found PMCs (bear) just standing still, not moveing and not even having their weapon equipped, while their team mates very shooting at me right away. I even went and stood right in front oh them: nothing, not even a step aside...

Any idea what could cause this?

AI in general seems a little strange now. They just go full auto, everytime they spot someone, until their clip is empty, even at very long distance...

Display More

Quote from Roach

When updating to the new version of this mod, I can confirm the AI on Interchange with newspawnsystem set to True and both factions will attack Player on sight will now act very weird. Exactly like Khadafi said above, the AI shoot full auto until clip is empty and on a few occasions will just stand there or run off to a "safe place" and when confronted they won't shoot at all. On the other hand, on occasions they try and shoot you from 100's of meters away through vehicles, walls etc. Sounds strange but it happens.

I can't for the life of me understand what could cause the AI's to act like this, I haven't really changed that much in the INI file mainly the armour min-max, weapon min-max levels, mod-quality, how many Scav, PMC's & Raiders are on the map, that's it.

The mod itself is fantastic and gives the game more life but there must be something conflicting somewhere we just need to find it.

EDIT: I will test a bit more with some custom settings in the INI file and update with more information, sorry for being vague.

Display More

Unless the [bot]DifficultyMod_Neg3_3 values are changed, the AI is using almost the exact same values it was using in the previous version, so the only two things I can think of that could be causing that are the sameFactionPMCsShootPlayerOnSight_true_false_'Default' setting in the config, and the stat rounding function. Try setting sameFactionPMCsShootPlayerOnSight_true_false_'Default' to 'default', and see if that changes anything.

As for stat rounding, I don't expect this will do anything but give you slightly worse performance, but you can try disabling it by changing the line:

this.roundAllBotStats()

to

//this.roundAllBotStats()

Quote from Khadafi

Oh and in my Opinion there are way to many raiders now, at least on factory.

Is there a way to reduce their numbers with the new spawn system?

And when setting newspawnsystem to false, PMCs are absent again, at least for me on coastline.

The only raiders that should be getting added are ones set to spawn in the config, so you should be able to reduce them there. However, if useNewSpawnSystem is set to false, the precise number you get will be higher than whatever you enter, usually by about 50%, but it varies depending on the size of waves you add (The exact formula per-wave is 50%, and truncating the result. So 5 becomes 7, 2 becomes 3, and 10 becomes 15). This is not a problem unique to my mod, and occurs even with manual edits to the map wave entries. Setting useNewSpawnSystem to true fixes this, but can cause problems for some people.

Quote from NugentGL

I am experiencing the same PMC's just standing around. I originally had:

sameFactionPMCsShootPlayerOnSight_true_false_'Default' set to true

Changed it to false with the same behavior and tried to change it to Default, default, 'Default' and 'default' but get an error message from your mod upon server startup. I also have:

PMCDifficultyMod_Neg3_3 set to 3

Display More

Quote from Khadafi

I think it's this. I lowered it to 2 and haven't seen any brainless bot eversince, but I'll keep my eyes open.

Edit: Nevermind, happens on 2 also...

On top of all the weirdness, it was a group of two PMCs. While one was working as intended,

the frozen one was an excact copy of the first one. Same name, same equipment, same level. A scav was a few meters away, ignoring him the whole time. It's almost like the bot creation progress got interrupted.

So is it just PMCs that are doing this for you? I'm having a bit of a look over it this weekend, and if it's just PMCs that makes it a little easier to troubleshoot (I hope >>;).

The sameFactionPMCsShootPlayerOnSight_true_false_'default' option also needs default to be in reqular quotes. -It's hard to make that clear, though, without breaking the JSON format.