Posts by RogueTech67

Quote from chomp

Ive removed 3 bot personalities from the pmc pool I found were becoming unresponsive, hotfix

Thanks for the update. However, I'm seeing the exact same issues with 3.3.0 HF5

ISSUES

1) Console Entries [Tried to edit a non-existant item:]: Yes

2) PMC's Agro - NONE, never retured fire

3) [Kill List], Player and Status: some showing, some [???]

11/20/2022 - Clean Customs run

All (6) never aggroed, and all (6) had [???] for player names

(LogOutput.log)

[Info : Console] Updated spt bot Kilgor616 : sptBear to cursedAssault

[Info : Console] Updated spt bot Braiden Mccormick : sptUsec to pmcBot

[Info : Console] Updated spt bot Максим Алексеев : sptBear to pmcBot

[Info : Console] Updated spt bot Степан Зорин : sptBear to followerBigPipe

[Info : Console] Updated spt bot Big Boss : sptBear to bossKnight

[Info : Console] Updated spt bot Solomon Mack : sptUsec to pmcBot

Display More

Quote from chomp

We've created a hotfix that fixes an issue with bots spawning without a brain, give it a try and let me know if the issue persists:

https://dev.sp-tarkov.com/SPT-…leases/releases/tag/3.3.0

11/19/2022 - CHOMP, Hello. -I did 5 SCAV runs on Customs with 3.3.0 HF4 (11/18/2022) with a clean/new USEC user profile. (** I edited \Aki_Data\Server\database\globals.json -> "SavagePlayCooldown": 1500, to "20" so I could immediately do repeated runs). Both the Bear's and USEC's were still just standing there and never aggroed. After shooting at then, they mostly did nothing, and on a rare occassion would run away. They never fired back. Upon extraction, in the [Kill List], the Player and Status just showed [???]. In the CONSOLE, there were numerous entries "Tried to edit a non-existant item:" when the bots were being spawned in.

I just went back and retried a clean 3.2.5 and 3.2.4. This SAME ISSUE is happening on 3.2.5. The PMC's on a SCAV run never aggro. The slight DIFFERENCE is that the PMC's once fired upon, would recognize it, and start firing back. NONE of this behavior was happening up to and including 3.2.4. Something was introduced into the 3.2.5 SPT-AKI that started to cause this change in PMC behavior toward playing as a SCAV.

I've saved off every Official game version since 0.12.11.2.14290 (16 Sep 2021) - SPT-AKI 2.0.0 / 2.0.1, along with the corresponding SPT-AKI files. I've played every SPT-AKI release since then. I've mainly played as a SCAV for years since I'm not very good at the game. One thing I am good at is I'm very analytical (55 years old - 35 year retired IBM Programmer / System Tester / Network Administrator). With ONLY "clean" versions of the game, the corresponing SPT-AKI, a USEC user profile, and the small change to globals.json for SCAV usage, anyone should be able to see the exact same things I am. I wish I could help in troubleshooting or fixing the issue, but unfortunately I can not. I am however willing to do any system/game testing you would like me to try. Thanks.

Server CONSOLE:

Note: Upon "Deploying In:" .........

[Client Request] /singleplayer/settings/bot/limit/assault

[Client Request] /singleplayer/settings/bot/limit/marksman

[Client Request] /singleplayer/settings/bot/limit/assault

[Client Request] /singleplayer/settings/bot/limit/assault

[Client Request] /singleplayer/settings/bot/limit/marksman

[Client Request] /singleplayer/settings/bot/limit/marksman

[Client Request] /singleplayer/settings/bot/limit/bossKnight

[Client Request] /singleplayer/settings/bot/limit/followerBigPipe

[Client Request] /singleplayer/settings/bot/limit/followerBirdEye

[Client Request] /singleplayer/settings/bot/limit/sectantPriest

[Client Request] /singleplayer/settings/bot/limit/sectantWarrior

[Client Request] /singleplayer/settings/bot/limit/bossBully

[Client Request] /singleplayer/settings/bot/limit/followerBully

[Client Request] /client/game/bot/generate

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

Tried to edit a non-existant item: body

Tried to edit a non-existant item: feet

[Client Request] /singleplayer/airdrop/config

[Client Request] /launcher/profile/info

[Client Request] /launcher/server/version

[Client Request] /launcher/profile/info

[Client Request] /launcher/server/version

Quote from chomp

If you're experiencing 'brain dead' bots, can you kill them and find the name on their dogtag.

Look this name up in the bein ex log: BepInEx\LogOutput.log

And let me know what types aren't working + what map you're on?

I'd be happy to do this for you guys and will. Have you 3-4 main guys writting, changing, maintaining and testing this SPT-AKI seen, this issue? It is so appearent and obvious, I find it hard for you guys not to be able to reproduce it. Just install a clean game version, and clean 3.2.5/3.3.0, modify the \Aki_Data\Server\database\globals.json ("SavagePlayCooldown": 1500, -> 0) and start repeated SCAV runs. Walk around any map (i.e. Customs) and most of the bots will not agro or notice you. Some PMS's, even after shooting at them, will not notice and never return fire. Both myself and my son have reinstalled "clean" 20243/3.3.0 numerous times, and this issue is just so appearent. With the very first comment in the SPT-AKI 3.3.0 Release notes reading (below), this issue can almost not be coinicidental. You made major changes to the PMC bots, and now users are seeing the bots not reacting correctly.

Really, sorry if I sound like I'm being an #$*%^, or that I'm upset, I'm not. I appreciate what all you guys do to get this game working and keep improving it. I will get the test results you asked for as soon as I can. Thanks

3.3.0 Release Notes:

"The biggest change in this release is the implementation of our new SPT PMC bots. These custom bots allows us to add PMCs with nearly any behavior of another bot without having to be that bot. This means we can have a Bear PMC with the behavior of Killa, a USEC PMC with the behaviour of a raider."

Playing as a SCAV, all the PMC's just stand there and never aggress you. Even after shooting at them, they just stand there as if they can't even see you. Shooting at passive SCAVs immediately makes them aggressive toward you, and they fire upon you like normal. Something is majorly wrong with the PMC logic in 3.3.0.

Then I went back an checked a "clean" Offical game/SPT-AKI install for 3.2.4 and 3.2.5. Playing as a SCAV in 3.2.4 works fine. the PMC's (Bear and USEC) both engage you immediatly. But on 3.2.5, there was the same issue as we're seeing in 3.3.0. The PMC's do not engage when you play as a SCAV. I'm seeing this issue started on 3.2.5, and is still in 3.3.0. If you read the Changes in the Release notes [ https://dev.sp-tarkov.com/SPT-AKI/Stable-releases/releases/ ], it appears PMC changes were made starting in 3.2.5, and more in 3.3.0 that would explain this issue.

The entire https://hub.sp-tarkov.com/ was inaccessible for me for the past 24 hours. Now that it is available for me, it appears most/all the Mod URL's have changed. The main SPT-AKI down was at ( That's a weird P90 ) and now it is at ( SPT-AKI ). The first few I have tried to go to to update were no longer available at the original "file number". Did the site crash? Are all the mods now at new URLS's? Thanks

Also, while the site was inaccessible, I had trouble finding where to go for information, and every Discord Invite to [SPT Pub] would not open the Discord.

1) Who/how do we contact someone for info on the site?

2) Is there a working [SPT Pub] Discord, and if so, what is the valid URL invite?

Thanks in advance

Thanks for replying so quickly, and taking a look at it.

Quote from GhostFenixx

It was `kinda` intended to be this way, but seems like it causes weird issues after that I wasn't aware.

Health changes does the edit in your profile that consist of Maximum and Current stats, I presume other modders change both whilst I change only the maximum.
The reason behind it to keep the mechanic of `regen over time`, you see - that function will proc every time you run the game(as long as it's active), making your health stats always maxed due every run it will rewrite `Current` to the same value as `Maximum`.

I'm more concerned about health doesn't change on your side after you healed, which is more of an AKI issue rather mine.

I could possibly make an `IF` statement that would check if the maximum health is the same value to not don't do any action.
Even tho it would look horrible in terms of code.

I'll tinker around and see what can be done and what went wrong.

Display More

Hello. Loving your AIO mod. Using 1.4.9 with SPT-AKI 2.3.1 (current). Believe I found an issue with the [Players and Skills] - > [Enable Health section]. If you take a new/clean game/user profile never even having done a single raid, this issue happens for me. It does NOT with the similar "player health" implementation from two other Modders [Kiki-HealthMultiplier] and [MuchNeeded]. Both of those when you set the health values, they stay the same and fully healed everytime the game is started.

The issue is if you simply change HEAD from 35 -> 135 and THORAX 85 -> 185 as an example and [APPLY] it, and then run the game, immediately you will see the player has the max values changed, BUT the current ones are NOT updated. So they show needing repair. Then if you repair them with a med kit to 135/135 and 185/185, close the game, restart it, the values are back to LESS then full??? It didn't even retain the full status from the med kits you used. As I stated, if you try setting the health values with those other two mods, they set the values to FULL from the start each and every time. Hope I explained this well enough. Thanks in advance.

Hello. I have to apoligize. It appears the BepInEx errors upon extracting or ending a raid are in fact caused by mod [Never Lose Equipments] - Never Lose Equipments. I did not realize I had that one enabled. I confirmed this by trying [KMC Server Value Modifier] - KMC Server Value Modifier. It too with the feature [Raid options] -> [Enable Softcore] causes the exact same thing. Almost every raid end causes this error and the game ends. I have informed both mod authors.

However, I still see some "red" errors/warnings from time to time with ONLY "vanilla" 0.12.12.15.17107 (11 Mar 2022) *** add SPT-AKI 2.3.0 and 0.12.12.15.17349 (01 Apr 2022) *** add SPT-AKI 2.3.1. I don't understand them, and none of them have caused the game to hang. If you simply 1) Install a clean offical copy of EFT and 2) Add the appropriate SPT-AKI version, upon running raids you should be seeing "red" errors/warnings in the BepInEx console from time to time. Since ALL I am using is the offical EFT and SPT-AKI, I would think you (and everyone) would see the random warnings if you simply enable "Console Logging" in the BepInEx .cfg. Thanks.

Hi, Sorry I'm not good with all this online communication sites/apps. I'm trying to report an issue with SPT-AKI 2.3.0 /2.3.1. I've tried to join the Discord server from several links and can not. It shows 4200 users on line, it starts Discord (browser and/or Win app), then comes up blank [NO TEXT CHANNELS - You find yourself in a strange place....] My other dozen channels work fine. I have no idea why [SPT Pub] shows nothing. Anyway, I've been using SPT-AKI for a year now. Always works great. However with the release of 2.3.0 and BepInEx, I've had/seen the game "crash" in the BepInEx console on a fairly regular basis. I enabled console logging in \BepInEx\config\BepInEx.cfg to see the console. At either starting a game [LAUNCH] or when exiting/finishing a raid, the game just "hangs" and in the BepInEx console with there are "red" entries like the two examples below. I have NO OTHER MODS installed at all.

I love this SPT-AKI and just want to know where I should be going to offically report issues. Thanks for being patient with me.

BepInEx Console Errors:

-----------------------

[Info :RequestHandler] Request GET json: 36be4be2f1885fb39c7b070f:http://127.0.0.1:6969/singleplayer/settings/version

[Error : Unity Log] WebException: The request timed out

Stack trace:

System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)

System.Net.HttpWebRequest.GetResponse () (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)

Aki.Common.Http.Request.Send (System.String url, System.String method, System.Byte[] data, System.Boolean compress, System.String mime, System.Collections.Generic.Dictionary`2[TKey,TValue] headers) (at <48b96717ca0d4a76904ee6eb28bf85d9>:0)

Aki.Common.Http.RequestHandler.GetJson (System.String path, System.Boolean hasHost) (at <48b96717ca0d4a76904ee6eb28bf85d9>:0)

Aki.Custom.Patches.VersionLabelPatch.PatchPostfix (System.Object __result) (at <53263d79bb154f079d027d6a7d745dc7>:0)

(wrapper dynamic-method) GClass1183.DMD<GClass1183::Create>(string,string,string,string)

GClass1183.get_Current () (at <2b480cfba3fd4ee98dd33579220a6fc8>:0)

EFT.UI.PreloaderUI.Awake () (at <2b480cfba3fd4ee98dd33579220a6fc8>:0)

UnityEngine.DebugLogHandler:LogException(Exception, Object)

Class293:UnityEngine.ILogHandler.LogException(Exception, Object)

UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

[Info :RequestHandler] Request PUT json: cd422a17ee173c83c9fc31f3:http://127.0.0.1:6969/raid/profile/save

[Error : Unity Log] WebException: The request timed out

Stack trace:

System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)

System.Net.HttpWebRequest.GetResponse () (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)

Aki.Common.Http.Request.Send (System.String url, System.String method, System.Byte[] data, System.Boolean compress, System.String mime, System.Collections.Generic.Dictionary`2[TKey,TValue] headers) (at <8901c85307f24904afe119969c3adebc>:0)

Aki.Common.Http.RequestHandler.PutJson (System.String path, System.String json, System.Boolean hasHost) (at <8901c85307f24904afe119969c3adebc>:0)

Aki.SinglePlayer.Patches.Progression.OfflineSaveProfilePatch.PatchPrefix (ESideType ___esideType_0, Comfort.Common.Result`3[T0,T1,T2] result) (at <53e82d26bf4b444b8f460f00c4218315>:0)

(wrapper dynamic-method) EFT.MainApplication.DMD<EFT.MainApplication::method_44>(EFT.MainApplication,string,EFT.Profile,LocationSettingsClass/GClass1054,bool,Comfort.Common.Result`3<EFT.ExitStatus, System.TimeSpan, GClass1723>,EFT.UI.Matchmaker.MatchmakerTimeHasCome/GClass2413)

EFT.MainApplication+Class1003.method_0 (Comfort.Common.Result`3[T0,T1,T2] result) (at <7c3debc6f4e34749902c535c0dd675ad>:0)

EFT.BaseLocalGame`1+Class1129[T].method_1 () (at <7c3debc6f4e34749902c535c0dd675ad>:0)

GClass735+Class344.MoveNext () (at <7c3debc6f4e34749902c535c0dd675ad>:0)

UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <42787f1e61944d5b8428e15b82ac9c47>:0)

UnityEngine.DebugLogHandler:LogException(Exception, Object)

Class293:UnityEngine.ILogHandler.LogException(Exception, Object)

UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)