the key generation is no longer needed like the older version, are you using an old profile by any chance?
Posts by CWX
-
-
So we have investigated the raider spawns a bit and they do seem to be bugged, its a BSG issue tho, we have made a mod that will fix spawns on buttons:
Chomp-RaiderSpawnFix
and regards the PMC's, how AKI works is by converting the raiders to PMC's from what I have been told, so no raiders or few raiders will mean none or few pmc's. I haven't looked into how many spawn as its something a mod would have to address -
The first one is a mod issue, the weather in tarkov isn't the easiest to change and keep as intended from my experience, some people manage to get Rev's ChooseTheWeather to work perfectly, I wasn't able to so I went on an endeavor and made my own mod, with some of Rev's communication, check out CWX WEATHERPATCHER and that might be an option for you, it uses a different method and patches the game files directly when ran.
second one have you tried without mods to see if this changes?
-
client file shows you using 0.12.11.6.15092 which is the incorrect version for this SPT version
-
this isn't the right but as I will close it, make sure you don't have the default discord profile picture (avatar) and a bot should message you if you are blocked from entering, make sure you don't have a bot blocked/muted?
I'm unsure what bot it is personally, try a new account discord account?
-
Hi The_Katto, thanks for an amazing mod!
I've only started using it since AKI 2.1.0, but I've noticed that there's a bug with SVM enabled which causes quest items and flea market sales to not show up in the Messenger until after the game is restarted. I have attached my preset XML so you can attempt to replicate it yourself.
I have tested it and without SVM enabled, I am able to collect my quest rewards immediately after turning in a quest. However with SVM enabled I must restart the game or finish a raid for them to show up.
If you need any more info I will help as much as I can. Thanks again!
by restarting we had accidentally fixed the issue , its being looked into by the devs
-
Mmm we are currently looking into an issue related to quests, if you get a reward that hangs and doesn’t come through, try entering a raid and back out for the time being
-
Perfect, check SVM, I was talking to someone in general for a quest related thing and it was SVM, maybe it’s trader adjustments that’s causing it
-
have you tried without mods to see if the effect is the same?
-
can you show the settings screen on the launcher?
-
The only safe way I’d recommend is if you have an old backed up version to rollback your live install with, ofcourse you won’t be able to play live and opening the BSG launcher will ask you to update, but that should allow you to play 2.0.1 again
-
Have you got all three .nets installed?
-
Check the important section at the bottom.
This new version requires a new profile, changes in it won’t allow you to use it without editing them
-
can you try using no mods on a fresh version, adding traders and quests could have borked your profile or something, I haven't heard this happening yet, you could also try the latest AKI but ill warn you modders need to update their mods so some will not work off the start. and updating your live version will stop the older versions of aki working so think about it before upgrading
-
ill close this thread as its not an aki support, raiders spawned without mods? they are 30% chance on the button and 15% for patrol in reserve basement, if you need support with the mods find the mod thread and ask the author a question on updating the config
-
new version of AKI is up, give that a go, no need for a patcher, mods will be sparse to start tho
-
this is usually to do with the .nets required. make sure they are all installed, try reinstalling if needed, there is now also a newer vversion of aki too
-
new version of AKI is up, moving thread to solved
-
so from discussion with the third party, AKI was being left separate, needed to follow the install guide.
-
try the latest version of AKI and EFT and see how it goes, if the problem still persists, hit up another thread with updated logs