Steenamaroo
-
Posts
3,679 -
Joined
-
Last visited
-
Days Won
208
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
Continuing in DM. -
Hi, Thanks for letting me know. Is this issue only since updating to 1.3.1? I just tested to confirm - It's working fine here. Do you see a message in console when you reload BotReSpawn, [BotReSpawn] Automatically Harmony Patched...etc ?
-
Hi, I suppose try the different communities - Someone may reply here, or maybe post in some of the rust/oxide/codefling discords? Realistically, though, you're probably better just setting it up yourself as there are so many options that suits one sever but may not suit yours. I've tried to make BotReSpawn setup as easy as possible. The vast majority of settings can be changed via UI without editing any files, and profiles can be reloaded individually to save you having to reload the entire plugin. The default settings for things like health, spawn radius, damage dealt etc are all fairly sensible values, so you can simply set autospawn true and reload a profile to have working npcs. There's also a copy/paste option within the UI so if you find you want to set numerous things the same way across many profiles, you can use that. Every option name in the UI is clickable, showing a brief description of what that option does - You might make use of that. Oxide's free Kits.cs plugin does make kit making very easy - Again, all can be done via UI in a few clicks, and selecting them or some profile within BotReSpawn is also just a matter of a few clicks. Don't be afraid to ask if you've any questions but, hopefully, you'll find it's fairly quick and easy to get going.
-
Your question prompted me to revisit the rewrite. It's much farther on than I had remembered so maybe I'll prioritise this and see about getting it wrapped up fairly soon.- 447 comments
-
- 1
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
Not in the short term, no. I did have plans to rewrite PlayerRanks 'cos it could really do with it, and did make a good start but, like so many things, it's a case of finding the time, so I definitely wouldn't be putting any promises on a time scale for that, I'm afraid.
-
Maybe I forgot then. I'll check. I mean, everyone who is running the plugin is going to have to delete their lang file or manually fix it regardless but fair point - New users shouldn't have to.
- 447 comments
-
- 2
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
Continuing in private message.
-
HI @Kaj Van der Hallen Could you reload BotReSpawn and tell me if you see additional/different errors at that point? Thanks for reporting.
-
Hi @MooDDang No, I'm afraid not. Navmesh isn't something that's within BotReSpawn's control. I think the only real options are 1: Temporarily disable that profile, to see if things are fixed/reverted at some point 2: Temporarily (or permanently) relocate or remove those npcs 3: Set the profile to stationary, for now. The third option sucks, of course, because the npcs wont be able to move, but they will, at least, spawn in the intended locations and fight with people.
-
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.
