Steenamaroo
-
Posts
3,407 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
Left some debug in by mistake. Fixed + updated. Thanks for letting me know.
- 1 reply
-
- 1
-
-
Done. Thanks for letting me know.
- 1 reply
-
- 1
-
-
Thanks for the info ZEODE. I'll take a look at this soon and see what I can find out.
- 1 reply
-
- 2
-
-
Hi, Glad you've found it's coming from elsewhere, although RustRewards shouldn't throw an error regardless. If an item or player is null it should silently handle that - I'm not seeing how OnCollectiblePickup can NRE, but I'll take a closer look at it. Thanks for the info.
-
I could maybe add in a true/false option to make animal skulls count, if that would be helpful.- 424 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.
-
Looks like they're being detected OK. I'm seeing "Abandoned Military Base". Is that not them?
-
Can you unload the plugin the open your /config/RustRewards.json and check it's as it should be? It might be a legit error, but I've had a few 'Failed to call hook...' which were actually the result of config file becoming null. Not sure why, yet.
-
Ok, good to know. Thanks pookins.
-
Hey, If there are new monuments BotSpawn should be picking them up automatically. If that's not the case, please let me know.
-
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?
-
That's automated. I did test, though, and can't replicate the issue.
-
Ah, good. Thanks for coming back to let me know.
-
Hi, Permissions Manager is just a UI for the existing oxide permissions and groups systems. It doesn't store any or manage any of the data itself. if your players were removed from their groups I'd guess something, or someone, has deleted those groups, or emptied them.
-
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. -
I tossed a coin on ai.dormant and ai_dormant Glad you found it.
-
Hi, It's a server setting - ai.dormant. Put ai.dormant false into rcon, server window, or f1 console as admin and that should sort it out. You can add it to the server start up config to make it persistent.
-
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.
-
Hi, Not really, I'm afraid. The only thing I can think of is that it doesn't announce on initial spawn, to prevent a blast of spam when you reload the plugin. It only announces when an npc has been killed and then a new one spawns, after that profile's respawn timer.
-
BotSpawn provides one profile per monument but you can have additional ones by creating custom profiles, using the chat commands, then adding the name of the parent monument, the monument this profile should always be near, in the custom profiles data file. Parent Monument name should be copied verbatim from the default profiles datafile so, for example, Parent_Monument:"The Dome 0", This means if the Dome moves (new map) the custom spawn points you added in this custom profile will also move, maintaining position relative to the Dome. You can also use Parent_Monument without custom spawnpoints - That just means BotSpawn will randomly pick spanwpoints but your custom profile will still always relocate to be in the same place, relative to the Dome. Note - Adding or changing 'Parent_Monument' will wipe any existing custom spawn points for that profile. Set Parent_Monument for you custom profile then reload BotSpawn, before adding custom spawn points to it.
