-
Posts
3,481 -
Joined
-
Last visited
-
Days Won
204
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
- 424 comments
-
- #statistics
- #leaderboard
- (and 12 more)
-
- 424 comments
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, No, that's not a thing. Plugins need to register their own permissions but, more importantly, they need to write the code to determine what that permission allows you to do. You'd need to put in a request with the author of that plugin.
-
- 424 comments
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, Vanilla npcs can't use bows I'm afraid. NPCKits does customise some surface things like appearance and whether their inventory wipes, but it doesn't modify their behavioural code. BotReSpawn, which does have it's own custom behaviour, does let the npcs use bows as well as flamethrowers, MGL, rocket launchers etc.
-
- 195 comments
-
- #permissions
- #admin
-
(and 7 more)
Tagged with:
-
- 195 comments
-
- 1
-
-
- #permissions
- #admin
-
(and 7 more)
Tagged with:
-
- 583 comments
-
- #hud
- #interface
-
(and 6 more)
Tagged with:
-
Hi, No, it doesn't automatically wipe or anything like that so if your arena is in the same place each wipe it should be fine. Glad you're not having issues. Please let me know if anything comes up. There haven't been many request, or complaints, in a long time so I never really look at this plugin now.
-
JsonReaderException: Unexpected character encountered while parsing value - line 0, position 0. ^ This error is occurring when BetterNPC is loading its config file. BotReSpawn definitely has nothing to do with that, or your ServerHud issue. The error you've shown means, in the vast majority of cases, a user has made a mistake when editing the config file. In rarer cases it could be data corruption or an issue that resulted in the config file being saved as null. I'd recommend unloading BetterNPC then restoring its config file and data files from backups, but also verifying those files with a visual inspection, and also by passing them through https://jsonlint.com before reloading the plugin. I'm quite sure the authors of ServerHud and BetterNPC will tell you the same thing.
-
Hi Your issue seems to have come from a problem in your betternpc config or data file. it’s a coincidence, I’m afraid. BotReSpawn didn’t cause this.
-
Hi, For cases where the user has multiple multiplier permissions, the plugin does check through them all and just pick the highest one. It does, however apply all categories of multiplier so if, for example, some action is subject to Permission multiplier of 2 Distance multiplier of 3 Weapon multiplier of 4 the total multiplier would be 24. In your given example the permissions component of the player's reward multiplier would be 2, not 8. I did get a request to make multipliers add together rather than multiply. This will be in the next version and, if enabled for my example, would result in a total multiplier of 9 instead of 24.
-
Hi, I've had this requested a few times so it is on the list, but the obvious way of doing it is quite expensive so I'd like to find a more performant way if possible. Leave it with me, and thanks for the suggestion.
- 1 reply
-
- 1
-
-
Hi, If you're recycling the same map you can set `Disable_Non_Parented_Custom_Profiles_After_Wipe` to false. That way the custom profiles will remain AutoSpawn: true after your wipes.
-
HI, Permissions Manager doesn't facilitate this but the console command for it is oxide.group add GroupName
-
Hi, There hasn't been an update since November so, no, nothing's changed recently. Is this a different map? Maybe there just isn't navmesh in that particular area. There is, and always was, a water level check, though, to prevent the npcs spawning in, or navigating into, water. Maybe I can experiment with the threshold slightly to allow them to spawn+navigate in very shallow water.
-
Yeah, looks like that's the one. The developer could keep a record of IDs of entities they have handled and just return if an entity's ID is already in that list, to prevent the code running multiple times for fast-paced multiple damage (like buckshot), or they could check if barrel is null or destroyed before running their .Kill code and only call OnEntityDeath hook in cases where it's not null or destroyed. Or, as you said, you can just remove it.
-
Hi, Sounds like you've got notifications disabled for activity. This is a per-player preference. You can change your preferences in the Rust Rewards UI.