-
Posts
1,264 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Krungh Crow
-
Changed Status from Pending to Closed
-
sorry was in bed sick for couple days. what was the fix ?
-
so it does not display what is in the loot in console ?
-
use debugg and check what the messages say in rcon
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
fun fact... rust started as a dayz clone ^^ with terrible graphics even for its time lol -
npc's are just a part .. any loot alterations or bad spawns including lootcrates roadsigns etc etc has this. This is normal behaviour and every server has to deal with this. Finding a good plugin the clean that mess up is the next step. But if you like to think npc's are not a part of the problem be my guest , sure they not all to blame for this hence they call this an item leak. You deleted those items from the npc's ? and where do you think they go ?
-
Planners is not the item `Planner` creating an npc is Planner since its apparently constructed as object. so its seen as a planner that is not removed when spawning has failed
-
known issue since rust sucks removing items during removal. cases when npc are killed (generic) : example cargo ship or bad navmesh respawning Same for lootspawners. More plugins means more items
-
looking into it -
{ "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
