-
Posts
3,394 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
Thanks for flagging it, btw.
-
Hey, That's just two plugins disagreeing on what the APC should do. I'll have a chat with Krungh and see if we can do something. For now you can disable APC_Safe in BotReSpawn, or some setting in BradleyGuards, (not sure), or ignore the messages.
-
Oh, that was it? My pleasure! Glad to hear it was something simple.
-
Hi, Looks like `Oxum's Gas Station 1` is the only profile without a kit specified. The rest of the AutoSpawn:true profiles have kits specified. For some of the profiles you have "Keep_Default_Loadout" set to true, which would keep the default hazmat suit. Trying to move clothing from a kit in the case would fail, the same way you can't put on trousers as a player if you're wearing hazmat, or any full suit, so you might want to switch that to false. If you have it set to true on purpose, so your kit is adding to the default clothing and weapons, then leave it true. Are you able to redeem a kit yourself to confirm the plugin is definitely loaded without error? If so, have you recently switched the Kits plugin you're using?
-
Hi, Sorry for the late reply - I didn't see this somehow. As far as I know Auth Level 2 players are automatically put in the admin group, and all players are automatically put in the default group. Even if you manually remove players from these groups, I'm fairly sure they're put straight back in the next time they connect. If you want to differentiate between yourself and your other staff you'd be better making new unique groups and using those to designate permissions to ServerOwner and ServerStaff, or something like that. Keep in mind if your admins are really admin (authlevel 2) they can give themselves whatever permissions they want. It's best practice to reserve authlevel 2 for yourself only then give out permissions to your staff some other way.
-
Failed to run a x.xx timer in 'BotReSpawn v1.0.6'
Steenamaroo replied to Dr.D.Bug's Support Request in Support
Hi, Yes, that's the same thing and is fixed in the coming update. Thanks for reporting it! The consequence is one or two npcs will fail to spawn once in a while and, most likely, they'll respawn after a brief delay anyway. Worth fixing but nothing to worry about for now. -
Hi Grimm, I'll take a look at that and get back to you. I don't set an icon at present - What you see is default but I could make it an option for you.
-
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.
-
Failed to run a x.xx timer in 'BotReSpawn v1.0.6'
Steenamaroo replied to Dr.D.Bug's Support Request in Support
Just to update, this issue was solved and the fix will be included in upcoming V1.0.7. Thanks for the help debugging it. Dr.D.Bug. -
Responded to DM.
-
- 195 comments
-
- #permissions
- #admin
-
(and 7 more)
Tagged with:
-
@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.
- 195 comments
-
- #permissions
- #admin
-
(and 7 more)
Tagged with: