Fin added a new version:
QuoteCompatibility update for AKI 2.1.X
Posts by Fin
-
-
Fin added a new version:
QuoteCompatibility update for AKI 2.1.X
-
Fin added a new version:
QuoteCompatibility update for AKI 2.1.X
-
Fin added a new version:
QuoteCompatibility update for AKI 2.1.X
-
Fin added a new version:
QuoteDisplay MoreFAIT 1.19.4 for AKI 2.1.X
Compatibility update for AKI 2.1.X
Changes:
- Made bot generation less incompatible with future mods
- Difficulty tweaks
- The default difficulty settings in FAIT are now approximately as difficult as 'hard' in vanilla SPT
- There are some notable differences in how recoil is handled, and how behaviour changes affect the AI
- If you've changed your difficulty settings in the config, you may want to re-adjust them. BSG's new AI changes affected FAIT as well, and I've adjusted some internal settings and scales around to take advantage of that
- Changed how spotting time works
- Overall reaction speed should still be the same, but it's now better split between the 'spotting' and 'aiming' phases
- The default difficulty settings in FAIT are now approximately as difficult as 'hard' in vanilla SPT
- Made bot generation slightly more CPU efficient
- Improved the mod's ability to restrict the number of optical devices on a weapon
- Increased the frequency of iron sights on AI weapons
- Improved the health-resetting safety that accommodates CoD Mode
- It now checks player health to see if it's equal to CoD Mode settings, and only resets if it that's true
- This should allow for players or mods to modify health values without issue in 99% of cases
- Added in a few more error checks
-
Display More
Hi,
I've been encountering this invalid mod error with aki 2.0.1, tarkov version 0.12.11.14290, & version 1-19-3 of the tweaks mod.
included in the error pic is my mods list in case there is any conflicts...
thanks
link to photo as i'm a little computer illiterate... - https://ibb.co/PzR6Qpv
I can't be sure without seeing inside the folder, but it looks like you made a new folder for FAIT. -That shouldn't be necessary, the archive you downloaded should be opened and the folder inside extracted into your mods directory, so that when your file structure looks like this:
user/mods/zFin-AITweaks/[A bunch of files and folders] -
Got a server warning after updating.
To make sure, I installed the previous version of Tweaks and didn't get the error.Oops. You can ignore that, that's some testing code I left in that runs a trial bot generation upon loading the mod. It doesn't do anything or go anywhere, it was just for debugging.
-
Fin added a new version:
QuoteFAIT 1.19.3 for AKI 2.0.X
Speculative PMC spawning fixes
- A handful of internal changes have been made based on user feedback, that may help fix the issues some users have experienced where PMCs can fail to spawn
- Certain error messages have been made less aggressive
- Minor internal streamlining of the bot generation alterations
-
Fin added a new file:
QuoteIf an item could not ordinarily be found on the flea market by searching for the text that appears on its thumbnail, this mod adds the thumbnail text to the end of the item's name, thereby allowing it to be used as a search term to find that item.
Credit to JustNU for the output formatting.
-
Hello!
I just downloaded this and messed with some of the settings but when I load into game and go on a map, the AI that should be friendly were targeting me. Scavs would target me as a Scav without me having killed them first and same with USEC.Is this a setting I toggled or something else going on.
...Oops. -Looks like I missed the ping about your question, my bad. If UprootedSeeker hadn't posted a new one I might not have noticed that, either.
Anyways, I believe this is tied in to behaviour changes being enabled. -It switches the kind of AI they are to a kind that's not set up to be friendly to players, so disabling that might fix the issue, however friendly AI is an incredibly weird subject that it's hard to say anything definite about, particularly when it comes to friendly / hostile PMCs.
-
Sorry to necro the bots spawning with wrong armor problem, but I still seem to be experiencing it.
Did a testing run with no mods enabled other than AI Tweaks and this config (Scavs using 1-3 tier armor and PMCs using 4-6 armor), I counted at least 4 Scavs using tier 4+ (two rigs, one t4 armor, one Slick) and two Bears using tier 2 armor, all wearing the correct armbands. Behaviour changes are disabled since I read that somewhere else in the thread.For some reason I seem to have reintroduced a very old bug. Looking into this now, there should be a patch that addresses whatever is causing this shortly.
Edit: It should be fixed now.
-
Fin added a new version:
QuoteUpdate:
In the previous version, shotguns with swappable barrels could not have their spread modified.
A method for modifying the spread of any given barrel in the game, as well as finding out which barrels can attach to which item IDs, has been added.
-
Fin added a new file:
QuoteCheck the config for additional information.
Note: The broken shotgun spreads are fixed right out of the box. No config changes need to be made in order for this to happen. The config only needs to be altered if you want to specifically customize a shotgun's spread.
-
[snip]
FIN - If I'm wrong in my explanation, I apologize. This is simply how I understand it and it seems to give me the results I want in the game.Nope, you pretty much got it, I think.
[snip]
3) Okay I think I understand this setting more now, correct me if I am wrong here but from my understanding it means the AI are 1x, 2x, 3x, 4x, 5x, 6x more likely to wear this armour compared to the default? The default is 1, 1, 1, 1, 1, and I changed my config for Scavs to 2, 3, 1, 1, 3, 2, I don't like Scavs having class 4 & higher armour and I think class 3 armour as the maximum is perfect for them and I might of copied what you said but I just want to make sure
You did it right, but 2, 3, 1, 1, 1, 1 would make a bit more sense, just since, if you've already limited scavs to only having class 2-3 armor via the "Min and Max armor class available" setting, they won't be affected by the last three numbers anyways.
Also, just to note, but 2, 3, 1, 1, 1, 1 is setting the chance of getting (Currently nonesistant) class 1 armor to 2x. If you wanted class 2 armor to be 2x, and class 3 to be 3x, you'd want to set it to 1, 2, 3, 1, 1, 1
As you assumed it's the latter: I've disabled GearChange for the time.
And yes I got some other mods, but none that touch gear or AI. I'll try later with just FAIT to be sure though.
I believe I've solved your issue, there was a weird problem with the order some functions occurred in that could cause issues. I need to do a little more testing, but when 1.19.1f comes out, the fix will be included. Should be tomorrow, hopefully!
-
Hey !
Sorry I couldn't post all my config file, It was exceeding character limits for the post
And no, I'm not using progressive gear.
No worries! -I'll take a closer look later today when I have the chance, and see if I can use your config file to replicate the issue on my end.
Before I do, though, I'm just noticing that you have disableAllGearChanges set to 'true'. -Is this the setting you've been using when you've had issues, or is this just something you were doing temporarily to avoid experiencing the issue? I'm assuming it's the latter, but I just want to check to be sure, as some people have assumed that 'true' enables gear changes and 'false' disables them before. -I also assume you've checked to see if this still occurs when you're using only FAIT, and have no other mods in the folder (Just to make sure it's not a mod compatibility issue)?
-
Display More
Hey Fin !
Love your work so far. My only concern is that for some reason if I let GearChanges enable in the config file, bots seems to have very limited inventory items ignoring all fine tuning in the settings (number of mags, number of healing items ...)
If I disable GearChanges ("disableAllGearChanges": true,) everything revert back to vanilla AKI inventories, so I suspect something isn't working within this setting.
I am using the latest version of you mod and if I recall correctly I didn't have this issues 3 or 4 versions ago.
Code
Display More"AIgearChanges": { "CheckREADMEforInfo": { "optimizedLoading": true, "saveGearToFile": false, "loadGearFromFile": false }, "scavBots": [ "assault" ], "raiderBots": [ "pmcbot", "followergluharassault", "followergluharscout", "followergluharsecurity", "followergluharsnipe" ], "pmcBots": [ "bear", "usec", "cursedassault" ], "scavs": { "changeGear": true, "moreModVariety": true, "modQuality0_10": 1, "modFrequency0_2": 0.6, "magQuality0_10": 3, "magDowngradeChance": 50, "removeHatsPCT0_100": 25, "armorRarityMinMax0_50": [ 0, 50 ], "primaryWeaponRarityMinMax0_50": [ 0, 30 ], "sidearmRarityMinMax0_50": [ 0, 10 ], "armorLevelMin_Max": [ 1, 4 ], "armorLevelWeights1_6": [ 1, 3, 4, 2, 1, 1 ], "weaponMaxDurabilityMin_Max": [ 100, 100 ], "weaponDurabilityMin_Max": [ 75, 100 ], "ammoRemovePCTGood_Bad": [ 35, 25 ], "healingItemsMin_Max": [ 0, 4 ], "magazinesInVestMin_Max": [ 2, 3 ], "backpackSizeMin_Max": [ -1, 16 ], "maxTacticalDevices": 1, "maxPrimaryOptics": 1, "removeWeaponTypesSemiAutoPumpBolt": [ "" ], "specificWeapons": [ "" ], "useWeaponsFromOtherMods": false }, "raiders": { "changeGear": true, "moreModVariety": true, "modQuality0_10": 7, "modFrequency0_2": 0.8, "magQuality0_10": 7, "magDowngradeChance": 50, "removeHatsPCT0_100": 0, "armorRarityMinMax0_50": [ 0, 50 ], "primaryWeaponRarityMinMax0_50": [ 10, 40 ], "sidearmRarityMinMax0_50": [ 0, 30 ], "armorLevelMin_Max": [ 3, 5 ], "armorLevelWeights1_6": [ 1, 1, 1, 4, 2, 1 ], "weaponMaxDurabilityMin_Max": [ 100, 100 ], "weaponDurabilityMin_Max": [ 75, 100 ], "ammoRemovePCTGood_Bad": [ 20, 40 ], "healingItemsMin_Max": [ 2, 4 ], "magazinesInVestMin_Max": [ 2, 2 ], "backpackSizeMin_Max": [ -1, 20 ], "maxTacticalDevices": 1, "maxPrimaryOptics": 1, "removeWeaponTypesSemiAutoPumpBolt": [ "" ], "specificWeapons": [ "" ], "useWeaponsFromOtherMods": false }, "PMCs": { "changeGear": true, "moreModVariety": true, "modQuality0_10": 10, "modFrequency0_2": 1, "magQuality0_10": 10, "magDowngradeChance": 50, "removeHatsPCT0_100": 0, "armorLevelMin_Max": [ 4, 6 ], "armorLevelWeights1_6": [ 1, 1, 1, 1, 1, 1 ], "weaponMaxDurabilityMin_Max": [ 100, 100 ], "weaponDurabilityMin_Max": [ 100, 100 ], "armorRarityMinMax0_50": [ 0, 50 ], "primaryWeaponRarityMinMax0_50": [ 20, 50 ], "sidearmRarityMinMax0_50": [ 20, 50 ], "ammoRemovePCTGood_Bad": [ 0, 60 ], "healingItemsMin_Max": [ 3, 5 ], "magazinesInVestMin_Max": [ 2, 2 ], "backpackSizeMin_Max": [ -1, 40 ], "maxTacticalDevices": 2, "maxPrimaryOptics": 1, "removeWeaponTypesSemiAutoPumpBolt": [ "pump", "bolt" ], "specificWeapons": [ "" ], "useWeaponsFromOtherMods": false }, "allAI": { "factionIdentifiers": true, "removeAIVogGrenades": false, "noHatsOnlyHelmets": false, "removeVanillaBotWeapons": true, "removeVanillaBotArmor": true, "botsWillNotSpawnWithTheseThings": [ "5d52cc5ba4b9367408500062", "5cdeb229d7f00c000e7ce174" ] },I can't tell because you didn't copy the entire config, but if you have progressive gear enabled, then that will override basically all your other gear settings. Could that be the issue?
-
Display More
Well ...... it appears my above message was incorrect.
I have a fresh profile and I just got the "assault bear pmcbot usec BACK UPS does not have an inventory entry" bug.
Here are ALL the settings I have in your config editor.
I tried the same settings in a brand new install of AKI on a totally different drive and I didn't get this bug, so what in the world could be causing this for the original AKI install? It's a fresh profile. Fresh as in "starting new and choosing which faction to play" fresh. Can the AKI server installation get corrupted?That's incredibly weird. -On the plus side it doesn't seem harmful, as going by the file's name it's just a backup of the default files used for scavs, raiders and PMCs, but on the other hand, I have no idea what could be adding a file called "assault bear pmcbot usec BACK UPS" to the bot folder. If you open your Aki_Data\Server\database\bots folder, is there a file like that inside?
As for the bug with Clodan's mod, that appears to be due to that mod pushing several undefined values as spawnpoints for bots. It can be bypassed (Though not fixed, as I'm reasonably sure this will prevent those waves of bots from spawning properly) by ctrl-f ing for this line in FAIT's mod.js (It appears twice in the file, and you'll need to do this for both instances):
let zoneList = map.backupWaves[wave].SpawnPoints.split(",")
And adding these two lines above each occurrence:
if (!map.backupWaves[wave].SpawnPoints)
continue
-
Definitely yellow.
As for me trying to do a clean vanilla raid, the game borked and gave me errors and in-game bugs.
Object reference error ... after a bugged insurance screen and missing body parts.It looks like you still had a modded item somewhere in there. In general I'd recommend creating a new temporary testing profile instead of trying to make your current one work, but.. -I had a question for you, just to try and get a better idea where the bug you're experiencing might be lurking.
If you set "Allow bots to use both armor rigs and vests" (In the misc tab) to true, do you still get the mismatched armor classes?
I'm still poking around at what might be causing PMCs to cease spawning.
-
Well ..... it didn't work. Still getting scavs with armor class above settings. And after setting PMC conversion to 50%, I now know I'm NOT getting PMCs.
I'm getting raiders (or what seem like raiders, given the gear they have) instead.
FYI - This was with all the mods listed before, so I will clean up my PMC and remove any non-vanilla items/presets...then try again.Can you verify that they are, in fact, raiders? -You should be able to tell by the colour of their armbands, white and yellow are raiders, while green are scavs. Red and blue are PMCs, and purple are boss followers.
-
OK. Thanks.
It's a bit confusing, but I think I'm starting to wrap my head around it.
Is there a way to have the setting be where you give 2 numbers and they be the min/max for pen like with the armor class setting? If not, due to how the game is coded, I understand. It would just make things a LOT easier.That's possible to do (In theory. At the moment it can't be done in the mod), and when I was designing the system it's one of the options I considered, but in the end I opted for the current system because it's better for allowing a 'spread' of ammo, and also works better between calibers (A good pen value for 7.62x54 weapons, which are all either bolt or semi-auto, is not going to be a good pen value for 5.56x45 weapons, or 5.7x28 ones, whereas being able to say "Use only the top 30% rounds available to this gun" works better when arming bots with a variety of weapons).
I might look into a way to toggle between the modes if I have the time, though.
