Fin added a new version:
QuoteVersion 1.4.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 1.4.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 1.4.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 1.8.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 1.5.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 3.6.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 2.5.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 1.4.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Fin added a new version:
QuoteVersion 2.5.0 for AKI 3.1.x
- Compatibility update for AKI 3.1.x
Thank you for your great works Fin!
I found some weird loot bug on vests. Half mask, a-2607 knife, Bloodset, kite gunpowder are appear repeatedly. Tested over 30 rounds, changed many things but results were always same.
I thought medical change in advanced inventory config cause this bug so changed it to false, tested again but same at all.
Is there any solution to fix this?
As far as I'm aware this is just how PMC loot is set up in SPT. FAIT doesn't do anything to modify the loose items in bot inventories.
Hi Fin thank you for updating FAIT and I know it is late for you right now lol.
[snip]
Should be fixed, the MP-18 was causing errors when bots tried to spawn with it.
Fin added a new version:
QuoteVersion 1.24.0 for AKI 3.1.x
1.24.0 - (July 25, 2022)
- Compatibility update for AKI 3.1.x
- Fix for a number of errors
- Errors on creating new profiles
- Compatibility errors with weapon-adding mods
- Others I can't remember right now. It is late x.x
[snip]
AXMC have conflict, because some of bundles or parameters broken in this mod, with other gun mods like samswat M32, G36\G36 Dreammaker or RD704\Ak545 Fait works fine, some unsupported items like new g36 optics just ignored by fait generation list
The item incompatibility issues are something I've already fixed in my dev version. I was hoping to fix airdrops before I did another update, but it turns out that it's a super-weird issue that isn't concretely tied to just the one setting. In my testing I've been able to cause airdrops to fail to appear in a couple of different ways, with differing levels of frequency, and the exact cause is still super murky. Even when I could cause it, it wouldn't prevent them from spawning 100% of the time, and it's been suggested to me that it could be a more general server issue that FAIT is exacerbating, under the right conditions.
So airdrop fixes won't be part of the 3.1.0 update, but that (Which won't be relevant now, because 3.1.0 is properly out, but that fix will help ensure compatibility with future weapon mods), some cod mode errors, and some other things I don't remember will be. They're all implemented, I just need to copy over my updated EFT and install 3.1.0 myself so I can make sure it runs on the new version.
no errors, but it does not save my progress in the game
Can you give me any other details to work with? The most important I can think of are:
Do you get a black screen on raid end, or do you return normally and find progress isn't saved?
If you exit the game without going into a raid, does it save changes you've made to your inventory (Purchased items, etc.)?
And if you run the game with no mods, does the error still occur?
I'll take a look at your debug hash in the meantime, and see if I get any issues when using your settings
[snip]
I've identified the source of the issue to be the breakUpSpawnWaves setting. I have no idea why, yet, but if that is set to true it kills air drops. Working on a fix. I'm glad you were able to get a working debug hash, as without that it would have taken much longer to track down
Is server value modifier compatible with this mod?
I have this weird issue where i try to use FIAT to set the server time but it still runs off my computers clock instead, the setting in FIAT basically does nothing. Ive checked it a couple times. do i need to set mod compatibility in SVM?
Thanks for your mod
Oops. I forgot to list that as a known bug, but 3.0.0 broke that function, and it still needs to be re-made.
Fin added a new version:
Quote-Fix for immediate crash on server startup. Oops.
Yes I was. Culprits were both Olympus and AXMC Sniper mod. Removed them and not it works fine.
Thank you.
There'll be a fix for that error in the next minor update, but at the moment they're incompatible, unfortunately x.x
Question, assumed and I thought in the past I was just able to edit the bot inv of each specific group to add sepcific backpacks to loot pool for them, but whenever I do any changes get reverted. Wasnt able to find anything in the readme when I quickly went through it, thought it might have something to do with the optimizedLoading setting in config but I am not sure. Dont get any errors do get a log saying changes have been made and reverting back, can make changes again and get log if need be.
That is an optimizedLoading thing, yes. You want to turn that off, and turn "Load from file" on.
I found the same reverting behaviour, and I think that's why the new "miscellaneous bot items" have been added to the advanced inventory config.
[snip]
That's my mistake, I forgot that objects can't have duplicate entry names. It just needs to be converted to an array format instead, and I think one extra line needs to be added to mod.ts, so it'll be out in the next minor update as well. And it runs all those times because it's been attached to a function that runs once for each bot, because I was lazy. I'll need to change that as well >_>;
Display MoreHi Fin,
I'm having below error when launching server;
[snip]
Server is running. Happy playing!!
(node:20476) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '_props' of undefined
at AITweaks.adjustPatronSlots (G:\Oyun\Escape From Tarkov\user\mods\zFin-AITweaks\src\mod.js:8860:39)
[snip]
Any idea how to fix this ?
Are you using the Olympus mod, by any chance?
Display MoreI have an issue that stops my server from generating a debug hash. At least I assume so because there is no debug hash in my logs. I did a quick look through and I didn't see any other ways to fix this problem so.
[2022-07-18T00:00:21.418Z] error: TypeError: Cannot read property 'deserialize' of undefined
[2022-07-18T00:00:21.419Z] error: TypeError: Cannot read property 'deserialize' of undefined
at Function.generateDebugHash (D:\BSG\SPT\user\mods\zFin-AITweaks\src\mod.js:5246:35)
at HttpServer.getRandomisedMessage (D:\BSG\SPT\user\mods\zFin-AITweaks\src\mod.js:142:30)
at WebSocketServer.<anonymous> (D:\BSG\SPT\obj\bundle.js:14577:60)
at WebSocketServer.emit (events.js:315:20)
at Server.emit (events.js:327:22)
at emitListeningNT (net.js:1352:10)
at processTicksAndRejections (internal/process/task_queues.js:79:21)
Can you post the full error? There should be additional white text beneath that, that contains some information I need.
Is it possible to add a spawn timing function? Like spawn x bots at y time at z location? and your mod is a game changer for SPT thank you Fin
Not at the moment, due to UI limitations, but it may be something I can do in the future!
Display More[snip]
I keep getting this error upon creating a new character.
[snip]
I saw the undoCodMode part and I know I can't have it enabled upon the creation of a new character but I do not have it enabled and have never used it.
Unless it was fixed, CodMode breaks your game even when it's off and you're creating a character, that's the issue I was having.
If you're starting a new character disable this mod and re-enable it after you're done.
That's odd. I don't get that error on my end, but I can put in additional safeties to the next mini-update. I'll try and put 1.23.2c out later tonight, with that included.
hi Fin. Is it broken or you just made it like that ? I am using advanced spawn config, all exusecs seems like Usecs\bears with usec and bear dogtags. In first record FAIT converted vanilla Exusec waves into PMCs
[snip]
That's an error, though I don't have an ETA for a fix. AKI uses exusec as the default Usec bot type, which throws a huge wrench into how FAIT works, that I'm still trying to get around.
Fingers crossed, I'll have it fixed soon!
So, I'm not running into a technical issue with the mod per say, but I do have a question regarding the spawn options itself. I've been finding an annoying problem with how many Scavs and Rogues are spawning into the start of the of the raids. What would I need to change to alter the ratio of Scavs, Rogues/Raiders and PMCs there are at the start of the raid?
UPDATE:I may have found the setting to alter that in the config application. Currently testing it real quick...
That's a little bit complicated, as there are a *lot* of options that affect that. But TL;DR: By default, FAIT does not remove vanilla spawns, so everything in the 'Extra Waves' section is being added ontop of the regular spawns. If you want to precisely control the ratio of PMCs to Rogues to Raiders to Scavs, you'd want to remove vanilla spawns and *only* add spawns in via the 'Extra Waves' section.
Fin added a new version:
QuoteVersion 1.3.3 for AKI 3.0.x
1.3.3 - (July 15, 2022)
- Added an option to multiply the damage done to weapons found in-raid. This option can only increase damage, at the moment, it cannot decrease it due to the particular math involved.
- If a weapon would be lowered to 80% durability, then setting this multiplier to '2' would lower it to 40%
Display MoreFound the issue, either need to create a missing folder, or adjust line 143 to save the files in the mod's root.
In this case I created the folder to make it simple.
Fin-LimitedInventories/Fin-LimitedInventories
I see the archive does not ship with this folder in the structure, that either should be adjusted or alter the code on line 143 to save to mod root.
CodeDisplay Morestatic setupTraderInventories() { for (let traderId in traderIds) { if (["579dc571d53a0658a154fbec", "ragfair"].includes(traderId) || !traders[traderId]) continue let newInv = FRET.randomizeTraderInventory(traderId, savedSessionId) if (newInv == false) continue traders[traderId].assort = newInv FRET.saveToFile(newInv, `/${traderIds[traderId]}`) // FRET.saveToFile(newInv, `/Fin-LimitedInventories/${traderIds[traderId]}`) FRET.consolidateTraderInventory(traderId) // FRET.findLostChildren(traderId) FRET.clearInvalidTradeEntries(traderId) if (TraderAssortService.pristineTraderAssorts) TraderAssortService.setPristineTraderAssort(traderId, JsonUtil.clone(traders[traderId].assort)) if (debugMode) FRET.saveToFile(traders[traderId].assort, `z${traderIds[traderId]}.json`) } FRET.saveTraderInventories() }
Oh, oops! ..I can't believe I didn't notice that little debugging error this whole time. I'll patch that out! Thanks for pointing it out :>