Steenamaroo
-
Posts
3,701 -
Joined
-
Last visited
-
Days Won
210
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
haven't looked in context but `!string.IsNullOrEmpty(itemData.Ammotype),` is bool, true or false, so most likely Kits is just using that as a simple check to see if the item is, or isn't considered a weapon. -
Hi, You're running an old version. The issues you're seeing were fixed in the next version. -
Hi, He's added already as "DesertScientist". Sorry, I missed have missed him when writing the update notes.
-
You're in RustRewards discussion, just FYI. You can enter a name in the Parent_Monument field for any custom profile in BotSpawn. If you plan to add custom spawn points, make sure you set Parent_Monument first...That's important. To give an example, if you want the regular airfield default profile to have 10 npcs, then you want an additional custom profile with one, go to the airfield, use the /botspawn add *name* command, then go into your custom-profiles json, find your new profile, and set its Parent_Monument to "The Airfield 0". That name you're setting there must be exactly as it appears in the default profiles json. Now that profile will always be exactly where you placed it, relative to the Airfield. If the Airfield moves, so does your profile. If you add custom spawn points for that profile, they'll auto-move too. Custom spawn points for default profiles also carry over in this way, so if you were using custom spawn points for Dome + your boss profile, you could dictate precise positioning of all of those npcs, and make it that the boss is always in the centre, protected by the lesser npcs, for example. -
Thanks for the info, Shark. I had a few people with the same issue. Not exactly sure what caused that but there was a mistake relating to config loading/saving which I've rectified in the most recent version. Hopefully that stops the issue from happening again. I'll check autoturrets next time I'm on and see what's happening with those.
-
I could maybe add in a true/false option to make animal skulls count, if that would be helpful.
- 457 comments
-
- 1
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
I'm still not having these issues at my end. If one of you has the time it might be worth doing oxide.unload * then oxide.reload RustRewards then test, to rule out the possibility of some other plugin interfering.
-
Just go to your chosen location and do `/botspawn add many` and `/botspawn add one`. Now you have two custom profiles in the same place - You can customise them separately and call for different numbers of npcs, but they'll be in the same area.
-
If you set BotSpawn option to 0 in RustRewards, then use BotSpawn's per profile configurations you can do this. I recently replaced BotSpawn's 'Economics' and 'ServerRewards' options with one single 'RustReward' option.
-
Hi, Unless you can harvest corpses, not really.
-
Ok. I don't think I changed anything relevant but it's working here and my local copy does have a config related fix, so I'll push an update tomorrow.
-
Both patrol helicopter and bradley are working fine here. Ensure that you have no relevant multipliers set to zero.
-
Perhaps you've hit a limit? Are we talking about players with millions of points?
-
Hi, I haven't used it but I believe Alphaloot has an option to disable loot in npcs. If that is the case, and I believe it is, then you shouldn't have any problems using CustomLoot for your npcs, alongside AlphaLoot for other containers. -
Hi, There's a 'bug' in the current version where you must unload the plugin then change config values (and save) then load the plugin again. The next version won't be like that. You should only set one of the three currency options to true, though.
-
You sure your config isn't borked? Try verifying your config file at https://jsonlint.com
-
Hi, Right now, as in BotSpawn, that's all handled by Kits plugin. I'm not sure if Kits plugin notes down pre-loaded ammo type or not.
-
I'll have a think about this. Maybe I can write a hook that lets other plugins register new 'items', and have these custom items listed in a separate section so their easier to keep track of. Each should have all the options a regular item has but, then, in addition it would have to have the prefab full name and the category that the item should be in. Maybe that would work. If it works out nice then it means other plugin developers could register 'new' items with CustomLoot
-
Hey man, The categories and items are grabbed and auto-maintained from in game, so it would be kind of difficult to have multiple entries for the same item. On top of that keys must be unique. I could make it that displayname is customisable but I think having multiple options would be awkward. What I could do is have string array of names and one is picked randomly, as is the case with BotSpawn kits/names. It's not quite the same as you're asking for but close-ish. "pickaxe": { "display name": ["pickaxe", "pickaxe", "Uranium Pickaxe - 3x gather at the cost of radiation"], "probability": 1, "minStack": 1, "maxStack": 1, "blueprintChancePercent": 0, "skins": [859006499], "IncludeAllApprovedSkins": false, "MinConditionPercent": 100, "MaxConditionPercent": 100 }, That would give 1 in 3 chance of the name being Uranium blah blah. Any use?
-
Good to know. Thanks mate. -
Hey. I'm doing some Rust stuff later. I'll take a look at this then. If Mike did make that plug and it works, please let me know.
-
Just noticing, your console output isn't showing 'admin' or 'treasurehunter' either. Perhaps there's some option with groups to prevent them from being displayed by command? I'll investigate. -
Not sure what would cause that. PermissionsManager grabs the groups 'live' from oxide's permissions.GetGroups(), so it's not like it's caching old information or anything like that. Do the names dniper or ppop mean anything to you? Did they ever exist? I'll take a look into it and see what I can find.
-
Is there an oxide console command to list groups? If so, give that a bash. It may be that the groups exist but the remove command is case sensitive?
-
I've not been able to replicate this but I'll have another look and see what I can find out.
