Fin's AI Loader (FAIL) 1.4.1b

I'm afraid I have no idea what might have changed three days ago, if you didn't do anything to alter the mod.

All I can suggests is to verify that the mod is, in fact, changing the AI settings. -To do this, go into the config and set the DEBUGGING_print_current_AI_settings option to 'true', and compare the files found in your debug folder to the base bot difficulty settings in Aki_Data\Server\database\bots\types.

Note that if you do that, the debug files aren't updated until you run the game itself, and reach the main menu. This is to be certain they're being properly applied. You may also notice that all four difficulty options, easy, normal, hard, and impossible, will use the same settings for a given bot: This is because of how SPT assigns difficulties across different bot types. Only some bots are able to use anything other than 'normal', and so to keep things consistent the four settings have been flattened out for all bots.

Hey Fin!

I just wanted to give my input on this thread as I'm having the same issue.

Right now I only have FAIL loaded and when comparing both files I can see that FAIL's settings are not being applied.

Just as an example for the "assault" bot under normal settings:

FAIL:

       "Aiming": {
            "MAX_AIM_PRECICING": 1,
            "BETTER_PRECICING_COEF": 1,

Database:

      "Aiming": {
        "MAX_AIM_PRECICING": 2,
        "BETTER_PRECICING_COEF": 0.8,

What's making you certain FAIL's settings aren't being applied? That looks like exactly what I'd expect to see, assuming Assault were set to a difficulty of 0, with the standard template (Edit: actually, I'd be curious to know what Assault is set to in your config. If it's not 0, that might be the problem?).

If FAIL's settings weren't being applied, the two files would look identical.

Hey Fin!

My assault difficulty is at 3, overallAIDifficultyMod is at 2.

It was my understanding that the settings in the database folder were supposed to match the ones found in the debug folder. Did I understood wrong?

Ah! -You did misunderstand, yes.

So, the way it works, the files in the database folder are what the server loads in when it first starts. It doesn't grab the files themselves, rather it makes copies of them in local memory. Mods then modify these copies without altering the original file in the database folder.

What the debug files from this mod do are show you what that copy in SPT's memory look like, letting you get a peak under the hood, so if the debug file is the same as the one in the database folder, then nothing has been changed.

That's odd that you're at difficulty 3, though, there may be a bug there. I'll look into that!

It may eventually be added to one of the advanced configs, but at the moment how AKI handles that has been changing fairly often, so it's not high on the priority list.

Glad you enjoy the mods ^ ^

Gotcha. I'm glad you're at least considering it.

Thanks for the quick reply.

@iStrong I believe the the "Server Value Modifier" mod can do the thing you are asking, they are under the second bot section.

I checked it out, and it seems it could do the thing i'm asking for indeed, but i'm afraid it might conflict with FAIT, because both of them modify bot equipment as well. And if i were to disable gear changes on FAIT, then i couldn't specify the helmet, armor and ammo rarity for SPT, since Server Value Modifier doesn't seem to have that customizability.

Oh, oops. Looks like I forgot to update that. bosstagilla, bossknight, followerbigpipe, and followerbirdeye.

I'll add that to the config when I get a minute.

Forgot to add: rogues are also "pmcbot", just like raiders, right?

Rogues are exusec, actually. ..Which is unfortunately also SPT's default for USEC PMCs, so any changes made to them will affect both unless you're using a mod to alter their bot type.

..Speaking of which, that's probably something else I should mention in the config..

Ah, that's probably it. I must have accidentally transcribed that as 1.17, instead of 0.117. I'll update the template this afternoon.

same here

FAIL shouldn't be able to affect how many PMCs spawn, as it only affects their AI. -I'll look into weird shooting behaviour, though, and see if I can replicate that issue.

Seems someone else found the issue for me: There's a value where I placed the decimal one to the left of where it should have been, which means that the curve spikes up the AI's scattering *super* fast on higher settings (Literally increasing it about 10x higher per difficulty level).

"ScatteringClosePerMeter": [0.273,0.233,0.195,0.156,1.17],

Change that to:

"ScatteringClosePerMeter": [0.273,0.233,0.195,0.156,0.117],

That should fix it, but I'll check for any other errors like that.

Thanks for your reply, I'll correct it in my file.

Moreover, I noticed PMC walking backward and not noticing me, even if I shoot at them...

Problem is still present for me with latest version, though it not happens everytime

There's a few ways. AI spotting speed is determiend by FarDeltaTimeSec, MiddleDeltaTimeSec and CloseDeltaTimeSec. Aiming speed is some mix of AccuratySpeed (That's their typo, not mine) and MAX_AIM_TIME

But I highly encourage you to experiment yourself, because I for sure don't know everything about how it's all set up.

That's odd. That sounds like something damaged your 'locations' files. Try re-downloading AKI, to replace those base files?

Same

ditto

reverted back to previous version and game/raid loads and plays like normal

same here

Working on a fix now.

Good news: That 100% confirms the AI are having FAIL's settings applied

Hello, Looks like you fixed it 1.4.1a is working for me. Thank you very much for your hard work.

That's odd. What program are you trying to open it with? WinRar is what I used to make it, and you might also try re-downloading, in case it got corrupted somewhere along the way.

I was trying it with WInRAR on my Windows machine, I was able to open it on a MAC OS with whatever archive viewer it has and transfer it. Thanks Fin.

I'd also like to add to this.

As per my comment below, I thought it might just be a visual bug but after running a few raids with the same drastic changes that you described I am also certain the mod didn't load.

Otherwise 10/10 mod.

What exactly do you mean by 'the list'? -If you're referring to the server console, then mods only appear there if they've been programmed to send a message to the console, which FAIL has not been.

If you'd like to verify that the mod is working, you can set the DEBUGGING_print_current_AI_settings option to 'true', and compare the files found in your debug folder to the base bot difficulty settings in Aki_Data\Server\database\bots\types.

Note that if you do that, the debug files aren't updated until you run the game itself, and reach the main menu. This is to be certain they're being properly applied. You may also notice that all four difficulty options, easy, normal, hard, and impossible, will use the same settings for a given bot: This is because of how SPT assigns difficulties across different bot types. Only some bots are able to use anything other than 'normal', and so to keep things consistent the four settings have been flattened out for all bots.

I checked the debug files and as you said there are some changes.

What confuses me is that when cranking up the difficulty in FAIT to 15, I get absolutely lasered.

When doing so in FAIL, the AI runs around completely braindead most of the time, and even when they see me takes 10 seconds to even shoot at me.

I'll try some more changes in the template file itself to see if I can fix whatever problem I created out of thin air.

Thanks again, Fin!

That could be down to the template being very old. -There have been a few big AI changes by BSG since it was last fully updated, so I'll see about re-syncing it with FAIT's current default.

That sounds awesome.

Thanks a lot, Fin.

Yes, you would just need to add their names to the botDifficulties entry, as you would other bots or bosses whose difficulty you wanted to alter.

Their names are bossKnight, followerBirdEye, and followerBigPipe

Can you paste the specific error text you're getting? -I'm not able to produce that error on my end, so I can't tell just what might be causing it.

Did a little digging because I thought it must be conflicting with another mod.

Some trial and error later, this is my console output with FAIL only.

ModLoader: loading mods...

Server: executing startup callbacks...

Importing database...

Started webserver at http://127.0.0.1:6969

Started websocket at ws://127.0.0.1:6969

Server is running. Happy playing!!

As soon as I add another mod, even if it's just Eerie Silence, this is the output I get.

Mod Fin-Fin's AI Tweaks is not compatible with the current version of AKI. You may encounter issues - no support will be provided!

Note that I am really using FAIL 1.4.0, uploaded 5 hours ago.

I'm confused.

No error text, nothing.

That's.. Weird. This is AKI 3.1.1? -What does the mod's package.json look like, specifically the "akiVersion" entry? It should say

"akiVersion": "3.*.*"

Edit: Also, I believe that message is just a warning, it shouldn't actually disable the mod itself, so you should be able to ignore it without issue. ..But then again, it also shouldn't be appearing at all.

Fresh install AKI 3.1.1

package.json is "3.*.*"

Very weird indeed.

Thanks for the quick response

Were you using 1.23.2, 1.23.2a, or 1.23.2b?

I'm using FAIL 1.3.0.

Seems like the other guy went from FAIT 1.23.2b to 1.23.2a.

Oh, oops! I forgot to include it in the upload. I'll put that back in there now.

If you'd like to get the readme without re-downloading it, I've put it on a pastebin here, as well

Thank you!

I'm terribly sorry, I forgot to upload the readme alongside the latest version. -I've fixed that now, the download should come with a readme file, and I've also included a link to a pastebin of the readme in my reply to the comment above. I hope that makes things a bit clearer, though it's still a bit complicated to work with, given all the variables BSG has for bots.

I haven't changed them myself. These are the defaults.

Oops, yes. Back when I was initially making these I had to transcribe some of the values manually for weird and annoying reasons, and it looks like I shifted the decimal place one to the right, for the last few in that entry.

It *should* be [0.273, 0.234, 0.195, 0.156, 0.117, 0.078]

I'll adjust that and reupload FAIL with the fixed defaults soon!

It should still work with a package update, yes ^ ^. -I'll try and remember to give it a proper update this weekend.

I don't have any specifics, I'm afraid, but the numbers can go as high as you'd like. I remember doing some tests ~12 before, and that proved fairly challenging, though it would have been with different base settings behind it.

I'm just about to upload a patch, and I'll include some changes to the config's information to make it clearer, but PMCs are now just 'bear' and 'usec', and it has internal logic that will automatically target whatever BotConfig has those bots set to use.

I have to thank you for pointing this out.

Unironically, I thought my game was just broken, and I never traced that problem back to this mod. -Now that you've pointed it out, though, it took two seconds to see that I'd forgotten to return the right response to a static route, and a quick test confirms that fixed it. I'll upload a patch momentarily.

Thank you very much, friend. Took me like an hour to figure out which mod was causing this issue but I'm glad it's going to be resolved.

Would also like to say I love your work. Its enjoyed and appreciated.

have a config with hard/impossible settings?

I'm afraid I don't, though the default one can be used with high bot difficulty settings (9+), and that's generally quite challenging.

And that string determines the possible values of XZ_COEF. -A bot set to a difficulty of 0 will use the first value in the list, difficulty 1 will use the second, etc. etc.

Disabling that should be fine, though I have.. ..Absolutely no idea why that would cause any errors whatsoever. All it does is check to see if the config has DEBUGGING_print_current_AI_settings set to true, and if so prints out the current AI settings.

But if removing it fixes the issue, then by all means ^ ^. It shouldn't hurt the mod at all.

Will removing this line cause issue on generating log? I was able get it generate once, but after that, logs seems not generating. I have tried deleted the old log, or pull the mod out and in of the mod folder. Any suggestion?

It shouldn't, but we may be talking about two different things here. -What precisely do you mean by 'generating logs', in this case?

I am mentioning the new feature on 1.0.0c, that new feature of creating a list of AI setting under debug folder that reflect value for each individual class. I had it created once, but wasn't able to create another debug log after I changed some AI setting.

Ah, yes. -Unfortunately, that line is vital for generating those logs

Have you tried backing up your current AI settings, and then replacing them with a fresh copy? The logging function involves printing out a json file of your settings, so if there's something especially weird it could be throwing a syntax error or some sort.

I believe AIO has an option like that, you might check that out.

It should be, yes

Yeah its still doing the same shows title screen then main menu never comes up even with only this mod. i can still use the ai tweak mod though so no biggie!

I think you run into the same error that some of us is experiencing. where game froze and not able to get into title screen. See above for temporary solution with a slight inconvenience draw back.

[ERROR] Trace:

TypeError: Cannot read property 'includes' of undefined

at Function.getResponse (B:\AKI211\obj\bundle.js:26283:16)

at Function.sendResponse (B:\AKI211\obj\bundle.js:26504:29)

at Inflate.cb (B:\AKI211\obj\bundle.js:26539:22)

at Inflate.zlibBufferOnEnd (zlib.js:153:10)

at Inflate.emit (events.js:315:20)

at endReadableNT (internal/streams/readable.js:1327:12)

at processTicksAndRejections (internal/process/task_queues.js:80:21)

@Madcowdsis, I saw in the comments you were working on getting an 'authentic' online feel with the templates. I'm basically trying to do the same with leaving everything besides PMC unchanged and making the PMC harder and react very quickly with greater accuracy. Were you able to do this? and maybe have some tips on what to change? Thanks for any help.