As far as I am aware IDs have to be hexadecimal, otherwise they will result in the error you are reporting here, i.e. the ID is invalid because it includes non-hexadecimal characters.
Posts by Janghe21
-
-
Why does your item ID include non-hexadecimal characters?
-
Have BossNotifier and the profile editor been updated? Both still list 3.9 as compatible, and the most recent version of the profile editor on github is from July.
Does the game still crash with a new profile and all mods removed?
-
Just booted up a new game in 3.10 and the issue persists - accuracy for 5.7 weapons is lowered by 10% with any ammunition type, making the 5-7 and the P90 less accurate by default:
7.5 MOA -> 8.25 MOA with SS190 (which should have no impact on accuracy), 7.5 -> 7.5 MOA with SS197SR (which should have an accuracy bonus of 10%)
This is not the case for other guns where accuracy is calculated correctly:
Again asking if anyone can confirm the issue, any help (apart from: JuST ModIFy tHE aCcUracy YourSelf as iexistggrsd "suggested") would be welcome. Confirming this would take you what, five or ten seconds at most?
-
Try modifying the ammo stats with Server Value Modifier: Changing Individual AMMO Stats?
Doing so reproduces the problem - setting the accuracy to +10 for SS190 results in an accuracy gain of 0 in the 5-7 and the P90.
Does this also happen on your end?
-
I have run into an issue I am have troubleshooting - apparently all 5.7 mm weapons - both the 5-7 and the FNP90 - suffer an inherent 10% accuracy loss applied to any ammunition inserted - something I can not reproduce with other weapons and not with the prior version I was playing on (3.7.5).
Default accuracy for the 5-7 as per info window is 7.5 MOA:
Inserting any kind of ammunition degrades accuracy by ~10% - see example with SS190, which - as per item.json and info window should have no impact on accuracy. Despite this accuracy drops to 8.25 MOA:
Using SB193 - which should actually improve accuracy by 5% - instead lowers accuracy to 7.85 MOA:
This is the same for FNP90.
The rest of the pistols and SMGs using other cartridges seem to be unaffected by this.
Is there something I am missing here? Can anybody reproduce this issue?
EDIT:
Apologies, I just noticed that there where still some armor and overheating related customizations present which show up as data import errors. The reported bug persists even after replacing the database files with the default ones, here is the updated server log:
SPT PrivateBinVisit this link to see the note. Giving the URL to anyone allows them to access the note, too.codepaste.sp-tarkov.comHere is the issue as it appears on the P90:
-
Addendum:
The only way to get followers to spawn is to add them as supports, for some reason SPT is preventing regular escorts to spawn on streets.
Adding
"Supports": [
{
"BossEscortAmount": "3",
"BossEscortDifficult": [
"normal"
],
"BossEscortType": "followerBoar"
}
],
"Time": -1
to the boss entry spawns the defined number of followers without issues every time. Same goes for the snipers - the only way to get more than one sniper guard to spawn is to add them as supports.
Can someone from the team have a looked at this? Is this intended behaviour?
-
I am encountering a strange issue with bot spawns that is limited to streets, where enabling bosses exclusively spawns Scavs, and Kaban only spawns with one additional sniper and no followers. Server console shows that neither USEC, Bear or Kaban followers are even loaded in as possible bot spawns:
/client/game/bot/generate data was: [{"Role":"assault","Limit":50,"Difficulty":"normal"},{"Role":"marksman","Limit":30,"Difficulty":"normal"},{"Role":"bossBoar","Limit":5,"Difficulty":"normal"},{"Role":"bossBoarSniper","Limit":5,"Difficulty":"normal"},{"Role":"gifter","Limit":5,"Difficulty":"normal"}]
Scav spawns also act like tagged and cursed is active (as in they zero in on my position after passing a certain distance threshold) despite the option not having been selected. Kaban followers not spawning makes it impossible to complete "The Huntsman Path - Big Game" and PMCs not spawning regularely impacts other quests as well.
All other maps work fine as far as bot spawns are concerned, this only happens with streets. Any advice on how to fix this woudl be appreciated.
-
Thanks for the heads up, I'll wait for the update then.
-
Thanks for taking your time, but what does any of that have to do with my bug report about in-game settings being broken? I know how to change bot settings in the config, but that's not the point.
The point is that the recent "hotfix" which apparently meant to address the issue doesn't actually fix this.
-
After. I was on 3.2.2 before but looking at the changes I'd hoped it would fix the issues with setting bot difficulty to "medium". Unfortunately it did not.
-
People are saying the main game needs an update for bots to be fixed. The best guess is to wait for BSG to release a new version and to wait for AKI to be updated as well.
Why does the "main game" need an update to "fix" bots that are actually working fine in 3.2.2 but broke in 3.2.3? The "main game" hasn't broken bots for me, the update from 3.2.2 to 3.2.3 did.
I don't know what BSG messed up with their servers this time, but the whole point of this project is to not have to use their servers because you're running your own local server. The only thing that changed is my AKI version.
-
There is no Medium option in the difficulty selection. Easy, Normal, Hard and Impossible. Medium is available in spawn options.
With all due respect, but there is:
And as you can see in the log file it isn't working, and neither is the fix (which specifically addresses the "medium" difficulty).
-
Setting bots to "medium" difficulty (still) results in no bots spawning at all, despite the latest hotfix attempting to fix the issue (game calling the setting both "normal" and "medium" etc.). Other difficulties work fine.
error log:
"In response to http://127.0.0.1:6969/client/game/bot/generate: Error converting value "Medium" to type 'BotDifficulty'. Path '[3].Info.Settings.BotDifficulty', line 1, position 39305."
From bothelper.js:
// Translate into bot difficulty when medium is chosen from menu dropdown
if (difficultySetting.toLowerCase() === "medium") {
difficultySetting = "normal";
}
if (difficultySetting.toLowerCase() === "random") {
difficultySetting = this.chooseRandomDifficulty();
}
From what I can tell this isn't working.
-
With 3.2.3 (new hotfix), bots often fail to spawn correctly, my last run on shoreline had only Sanitar+guards and no other bots, despite bot amount being set to high and the difficulty set to "as online". I have only encountered this problem after updating to 3.2.3 - 3.2.2 works just fine and I never had any trouble with bot spawns on that version.
In cases where this happens I am also unable to extract correctly and have to close the client with Alt+F4.
I have heard reports that this is due to a bug in the base game itself, but seeing how I have been on the same version of the game I don't really see how that could be the case, on top of the only happening with 3.2.3 - which introduced bot caching. A fix would be appreciated.
