Steenamaroo
-
Posts
3,670 -
Joined
-
Last visited
-
Days Won
208
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
Handled in private message. Will update shortly to address this. -
Actually, it looks like there's quite a few mistakes in that file. You'd probably need to go through with a json validator to remove all the stray commas. I guess someone went through this file deleting lines? That shouldn't ever be necessary. I'll DM back a fixed copy of the one file you sent. You can use https://jsonlint.com to fix the other. -
Thanks for sending the file. There is an issue with the file, and CustomLoot should be reporting this as the plugin loads. Remove the stray comma at the end of the highlighted line, save the file, then reload CustomLoot.
-
Not sure what to tell you. Could you DM me either of those loot table data files, please?
-
The plugin only updates loot tables which mentioned in the /config/CustomLoot.json file. I bet your files which aren't updated aren't actually in use.
-
Which new items, that you know of, are missing?
-
None, sorry. I just checked and all my files on the local test server have updated. Do you see any errors in console when you reload CustomLoot?
-
Hi, PermissionsManager does offer a backup and restore option but, of course, that'll only work if you used the backup command in advance. For normal use PermissionsManager doesn't rely on its own data record but, rather, oxide's permission system and storage. On oxide servers they're stored in /server/data/oxide.users.data, as far as I know. Maybe you deleted that by mistake? If so you should be able to shut down the server and restore that file from backup. oxide.groups.data is stored there too. -
I've never placed npcs there but I can fire up a map and check it out. Any chance you could fire me a screen shot for reference? -
I can only really reiterate what I said before, because I don't know that plugin, but my assumption would be that if you already have CustomLoot set up to put loot on the type of npc that plugin spawns, then the option provided would let you prevent that from happening for BossMonster npcs. It sounds like when I had 'Allow_Alphaloot' in BotReSpawn. I had dozens of people asking 'where do I put the loot table name' when, really, the option was preventative and should have been called 'Prevent_Alphaloot'. Maybe the author would consider adding "CustomLoot_Profile" as a string option, and making their own call for loot to CustomLoot if that's not empty. That would give more control.
-
I can only guess, without knowing a bit more, but if true/false is the only option I'd assume it's giving you the option to prevent CustomLoot from filling some container/corpse, in the event that you already have CustomLoot set up for that container/corpse type.
-
Unfortunately it's not just BotReSpawn npcs. I've seen the message with other npcs and, even sometimes, with real players. I wrote a small patch plugin to make the vendor flat out ignore any hostile npcs. I'll send it to you.
-
Thanks for the answer @Luuxen I wouldn't have known that - You saved me some time.
-
Confirmed fix in both BotReSpawn and NPCKits. Papa Bear DMd me shortly after this. Thanks again, all!
-
Sorry folks, I didn't get notifications for this until @Malkizid @ pinged me. Thanks for that. There is an issue with names introduced in the wipe update but I have since sorted it out and will be pushing a public update soon.
-
Scratch that - Looks like I can patch it fairly easily. I'll push updates for both soon. Thanks again.
-
Hi, Thanks for letting me know. I'm aware of this. It's something I can work around in BotReSpawn if necessary but for NPCKits it would mean a quite a bit of work for every npc type in the game. I'm hoping FP revert or make a change to accommodate us but who knows. Keeping an eye on it, thanks!
-
Oh, I see. Yes, CustomLoot does nothing at all unless you enable profiles within the config and set up a valid loottable to go with them so, simply put, if you just install it on the server and do nothing else, it wont change or interfere with anything. What you'd do is install it, set up RandomRaids config to use a CustomLoot profile name (which you make up), then the first time RandomRaids tries to ask CustomLoot for loot, CustomLoot will create a config entry, under API, of that name. In console you'd see the following as confirmation. CustomLoot had a call for a profile that doesn't exist. Adding profile {NameHere} using loottable 'default'. From there you can set up that new profile as if it was any other. If you need any help beyond that, let me know.
-
There's a global Remove Backpacks Percent in the global settings menu. Make sure that's set to zero and you should be good
-
There's API so that other plugins can make calls to CustomLoot. RandomRaids could offer that as an option, if it doesn't already.
-
Hi, BotReSpawn has both Backpack_Duration and Corpse_Duration Corpse_Duration is under Death tab and Backpack_Duration is under Other.
-
Consider it done.
-
If memory serves you should keep the probabilities to zero for those ammo items - gunsWithAmmo is a probability ignore/override setup, but the settings for minstack + maxstack are taken into account so that you can manage the amount of ammo that will spawn with each weapon.
-
In the config for each entry you'll find a setting called "gunsWithAmmo" If you set that to true then any guns which spawn will be accompanied with an amount of appropriate ammunition. To directly answer your question, though, no. You can't have multiple loot tables apply to any given container type.
-
I'm sorry, I'm not going to take all of the unique points from some other plugin and integrate them in to mine. I'm always open to suggestions and ideas but, in my opinion, that's a scummy move.
