Added a debug logfile function for the plugins loot container population
This is meant for those people who believe the plugin does not work properly and does not spawn the configured loot into containers on startup and/or while runtime
You can enable the log-file by this switch:
JavaScript:
"Debug": {
"debugLogEnabled": true
},
The generated file tells you exactly whats it's doing with every existing or spawning container and logs also a fresh server-startup and begin/end of the plugins start procedure.
In case of you find there any unexpected output, please append your file in the plugin thread.
The plugin does generate(drop) scrap, based on vanilla specification per container, once a container (mainly barrels) got destroyed.
The default amount of scrap being dropped is multiplied with the containers "UsedMultiplier" setting.
Added switch "enableLootFraction" (def: false), to control if loot can spawn fractioned (lowered condition) like by vanilla loot.
Added switch "enableDefaultRarityOverrides" (def:true) to enable/disable the plugin internal override of some hardcoded item raritys. False would disable this function, and the defaults are taken on next reboot and deletion of "ItemRaritys.json" before that.