Steenamaroo
-
Posts
3,692 -
Joined
-
Last visited
-
Days Won
210
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
I wasn't aware of that either! I'll have to take a look. Not a proper solution but for anyone who doesn't know the PVE_Safe option toggles whether barbs and cacti should hurt the npcs. -
Hi @Lei_Wong I got a bit mixed up earlier with the CustomLoot question but CustomLoot is support for BotReSpawn npc corpse loot. The management is done at the CustomLoot config end, though, since there are more options such as min/max item amounts, etc. Would have been cool to pick a loot-table right in the BotReSpawn UI but since CustomLoot needs more info it wouldn't really work. The preset export/recall is a great idea. I sort of have that in already, although not as ergonomically as you describe. If you change DataPrefix in your BotReSpawn config file then reload the plugin, you'll be working with three new data files of that name. As it stands you could set up a prefix for WeekOne, WeekTwo, etc, although there's no UI method of switching between them. That's something I should do ^. Great idea.
-
Thanks @pookins. Can't see any reason those would be missing but I'll fire a test map up and make sure.
-
It's in minutes @Covfefe
-
Hey, I think I misread, or misunderstood this. You always had the option to allow, or disallow, rust's vanilla scientist corpse loot. You also had the option to use CustomLoot to supply the corpse loot, or add to the existing vanilla scientist corpse loot. The new option just allows you to change the loot type from vanilla scientist to some other vanilla container/barrel loot table, but it doesn't change the old mechanics at all. If you want CustomLoot to be supplying the loot, with or without vanilla scientist loot, you can still do that. If you haven't made any changes to the profiles, loot wise, everything should work exactly as it did before.
-
@pookins- That sounds like the NoSash conflict we were talking about there. Either unloading NoSash, or setting `"Target_Noobs": true,` will solve. In the next update I'll just make this option do nothing if NoSash is installed.
-
@Lei_Wong- @Covfefeis correct - Thanks for that. Melee weapons used to be OP, not by choice. I've balanced out weapon damage across the board now so nothing's OP, but understand some people will still want greater than normal melee damage. That's what that option is for. @pookins- I could bring in CustomLoot profile as an option, for sure. The focus, for now, was other existing loot containers from the game, by request. Thanks! @Snivel- Use of grenades and meds are both automatic. The npcs will use them at strategic times, when line of sight is being broken/unbroken.
-
Yeah, looks like Target_Noobs:false and use of NoSash.cs don't play well together. Having Target_Noobs:true as default would have been ideal but that ship has sailed, so in the next update I'm just going to have the Target_Noobs option ignored if NoSash is installed. The result would be that noob players are targeted regardless of the setting, rather than the current setup where presence of NoSash (and Target_Noobs false) means all players get ignored.
-
They're meant to respond if they're attacked from distance. In previous versions they'd return fire regardless of their weapon but in the latest version you have an option called Limit_ShortRange_Weapon_Use which you can set true if you don't want npcs with pistols only, for example, to return fire over very long distances. In that case, and with the limit option true, the npcs will attempt to move closer before firing. You can, of course, still give them a rifle or bolty or something and they'll return fire from where they are.
-
Noted. Thank you!
-
Some things have changed and been added but, no, there are no hard requirements for update. Can't think of any reason npcs should be ignoring players now where they weren't before, but there is a damage issue which I'm about to patch for.
-
Hi, The name for the npc is picked randomly from your list of botnames by default. If you have 20 names and 5 npcs, you should eventually see all the names being used as npcs are killed/respawned.
-
Hi @406_Gromit That's another found/fixed/will be in V1.0.7. The biome spawnpoints are meant to randomise so they don't keep respawning in the same place over and over, but it wasn't working. I should probably add a building priv check, though. I'll take a look at that tomorrow. Thank you!
-
Hi @PandaJun Thanks for reporting. This is found + fixed. Fix will be in the next update.
-
It's not in the UI under animal kills? It should be there automatically, as far as I know. -
Issue found and solved. Changes added to V1.0.7, coming soon. Thanks for taking the time @MooDDang
-
I'd need to look into that but it's pretty unlikely in the short term. Not ruling it out but I have other things I'm planing to work on first.
-
Thank you! -
@Covfefe+ @Snivel Grenade tossing is in V1.0.7, which is more or less release ready.
-
Hi, I'll make a note and take a look at that next time I'm working on RustRewards. Thanks for the suggestion!
-
Hi @Adam Lewis- That makes perfect sense. Can't see why I shouldn't be able to add that for you. Thanks for the suggestion.
-
Hi @Leonardo, The plugin can be configured almost entirely by UI. Just do `/botrespawn` in console to bring up the UI and start customising event and default profiles, or do `/botrespawn add SomeNameHere` to create a new profile (at your current location) and auto-open the UI at that page. The minimum a profile needs to start spawning npcs is Autospawn:true, and a day and/or night spawn amount above 0, then just click 'Reload Profile'. Everything else is preference.
-
Hi Steven, Thanks for asking. DM sent.
-
@pookins " `/chat group list cmd` - what command is this?" Never mind - I found it. This command lists BetterChat chat groups. That's not the same as oxide groups. Use `oxide.show groups` in console to list all oxide groups or, better yet, use PermissionsManager. -
@pookins- The attached file was directed at Chernov. Your issue was described as Permissions Manager showing players who never joined your server, but your example shows group names. Do you have an issue with listed players too? treasurehunter is a real group, created by DangerousTreasures. `/chat group list cmd` - what command is this? Try oxide.show groups in console - It should show treasurehunter and oxide.group remove treasurehunter should remove it although, as Jbird says, it's created by DangerousTreasures so you'd need to disable the option in its config otherwise the group will just be recreated next time you reload.
