Krungh Crow

{ "probability": 1.0, (float so can be 0.01 to 1.0) "shortname": "ammo.pistol", "name": "", "skin": 0, "amountMin": 5,(int so rounded values 1 2 3 100 1000) "amount": 5 (int so rounded values 1 2 3 100 1000) },

on what ? fractions as spawnRATE not amount those are 2 things he prob built in a conversion when people use fractions instead of whole numbers so its rounded up as a full value. This should not be a thing since you have to understand what a value does. Do not compare shit others do so inexperienced users use wrong values on other plugins and ask themselves why the cfg is throwing errors

well we been saying this for allot of cfg mishaps so far. try to keep in mind the int and float values (whole numbers and fractions) and watch console always when edit testing a new cfg.

0.6 items ? you really need to work on your cfg editing skills since you obviously don't know what it all does NO plugin uses a minimum spawn amount of 0.6 that is 1 or 2 or 300 not a fraction spawnchance is something else depended on the plugin can be either a 0-1 value or 0-100 value

well items are whole numbers (int) and not fractions (float) i see several items to spawn as 0.6 instead of 1 or more

you are using fractions for the item amounts in loot tables and min amount should be 1 not 0

i added the fix cause it was breaking the skins for several plugins for a long time. It is obsolete now and apperantly fixed so its removed.

that's fine now you'll see splitting the bones results in having no skinned bones after splitting since that is not handled by stackmodifier. his plugin was breaking the shit hence i added it.

stackmodifier breaks the skins thats why there is a splitfix built in. doubt that sulfur has a skin cause when it has no skins my plugin does nothing and returns null

its a bugg that popups once in a while it used to happen when using plugins like alphaloot having the apc health set (i know should never be in a loot plugin but its in there). random plugins setting its health is hard to target which ones alter it since its not always clear why they would even do so

yeah its the cfg now being edited correctly. just do it step by step it gets easier once you done this more

backup the file you use now and generate the new one change values 1 by1 there has to be a variable not set right otherwise the cfg would not throw an error

if it gives errors after changing cfg it means the file has been edited wrong. don't rely on json checkers they only check if brackets and commas are correct. you cannot change all 1 to 1.0 without knowing what type of value it is. this is not the only plugin you had issues with when changing its cfg ?! Compare the values from the default cfg. anything that is a fraction is always ending in a 1.* and amounts as 1

prob one of the many npc plugins not removing their inv correctly

make sure that formatting is all correct when changing the cfg file. this is the same for every config for all plugins check if you didn't make any 1.0 values in 1 values for example since this happened during the editing of the file. json checkers do not check or see if it was 1 or 1.0 (int or float values) "probability": 1, and "Bradley Throttle Responce": 1, also is a float value so that needs to be "probability": 1.0, and "Bradley Throttle Responce": 1.0,

tiers are random have to respawn some to see it happen and use the debug and watch console when triggering bradleys

the json checker does not see if it is a float or int by changing that 1 to 1.0 should fix the syntax error for each profile

"Bradley Throttle Responce": 1, should be| "Bradley Throttle Responce": 1.0,

this was after you changed the loot ?

means you edited the cfg file incorrectly

if you use custom maps make sure you installed rustedit for the bradleyspawning

then there is nothing i can do for you if they spawn with health assuming other plugins change it. seems like a map issue if it is only at launchsite

Changed Status from Pending to Closed

it has not changed you where using 2 different bradleyguards plugins