Steenamaroo
-
Posts
3,406 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
Hi, It's the short prefab name so what you're looking for is bow_hunting.entity, bolt_rifle.entity, and l96.entity.
-
Are you sure CustomLoot is causing that? Doesn't sound like something it would/could do. -
Hi, No, it's just a UI front end for the permissions system in oxide so it has no storage of its own. Your timing is interesting, though, because I'm working on local+sql backup and restore as we speak! Thought it might be useful for people who set up servers in advance, or run the same perms/groups across multiple servers.- 195 comments
-
- 2
-
-
- #permissions
- #admin
- (and 7 more)
-
Glad to hear it. The scientist noises isn't really related to NPCKits but maybe I can put out a small fix-it plug. -
Thanks, Jaws. Would you mind letting me know if this sorts it? Failing that, I'll get a look tomorrow. NPCKits.cs
-
No immediate plans, but plans. Thanks for letting me know.
-
Version 1.0.8
4,116 downloads
UI spawn amount/time control for monument crates, keycards, barrels, etc. MonumentSpawnControl provides a UI per vanilla monument, listing each spawn group for that monument, with controls for spawn population, respawn timer, and max amount to respawn per cycle. Each group can be emptied, filled, enabled, or disabled, with one click. Respawn durations are in minutes. Where there are multiple monuments of the same name (e.g. Lighthouse), they are all controlled by the same settings. Notes Does not offer control over RustEdit created monument spawns. Does not govern spawners which are part of a puzzle, as these have their own reset criteria. Chat commands. /msc - Usable by admin, or with permission. Permissions. monumentspawncontrol.allowed Configuration. ButtonColour "0.7 0.32 0.17 1" ButtonColour2 "0.4 0.1 0.1 1" - Used for disabled / inactive. Config also stores an entry per monument with information per spawn group. There is no need to edit or view this - It’s all controllable by in-game UI. Useful tool for picking CUI colours - RGB Decimal.Free -
Hi! Thanks for posting back to let me know. Sorry it was forgotten about for so long.
-
When you see npcs in the location you're not expecting to see them, do bots.count in console and screenshot or note the populations per server, then do oxide.unload BotSpawn and watch to see if they vanish, to confirm 100% that they are BotSpawn npcs. If they are BotSpawn npcs, at least you now have a list of possible profiles that they are from. Next thing to do is figure out if they are spawning in the wrong place, or walking to that place over time. Reload BotSpawn, stay there, and set the server time to day, or night - whichever that profile needs. You can reference bots.count repeatedly to make sure they've spawned, if you don't see them. That ^ should tell you if they spawn in the wrong place, or they are walking there. If they're spawning there, ensure that UseCustomSpawns is false for that profile, go to the correct location, and do /botspawn move <profilename>. reload BotSpawn and test. That will rule out the profile's location being in the wrong place by mistake. Also ensure that the profile's spawn radius isn't larger than it needs to be. Try something small-ish like 40 or 50 for testing. If they were spawning in the right place but wondering off to somewhere unusual, check their roam radius and their aggro/deaggro settings. Keeping these reasonably tight should keep the npcs in the areas you want them.
-
Hi, Are you certain that the npcs at 0,0,0 are BotSpawn npcs? If so, do you know what profile they are from? Does that profile have UseCustomSpawns true, or false? If true, have you added custom spawn points and confirmed that they are where you think they are?
-
kk. That's very old debug from when I thought there might be some issue. If it's just one messages once in a while it's probably nothing to worry about. I'll remove the debug some time. Thanks for flagging.
-
Thanks pookins. How often? How many npcs do you have across the map, and how often is the server restarted?
-
Yeah, the titles issues are fixed in V2.15 which is coming soon. Thanks for reporting, regardless. -
Hi, This is fixed in V2.1.5 which will be released fairly soon.
-
Yes, you can add players to, and remove them from, groups with PermissionsManager.
-
I'll check and confirm some time soon but as far as I know it should be good.
-
HI, Yeah, as far as I know they should be covered.
-
I'll see what I can do.
-
How to change colour of "has taken title" chat message?
Steenamaroo replied to Kleementin's Support Request in Support
Just the same as in any other plugin "<color=#c73d1f>Text here</color>" -
How to change colour of "has taken title" chat message?
Steenamaroo replied to Kleementin's Support Request in Support
PlayerRanks has a lang file with all the messages in it. "tooktitle", "{0} has taken the title {1}." is in there. -
I guess you mean brackets? Yeah, you can add whatever you like as the tag, including colours tags, brackets...whatever you like.
-
Hi, Glad to hear you found the issue, and even more glad it wasn't BotSpawn. Thanks for sharing your findings, for anyone else in the same boat.
-
Hi, Do you mean when a player with titles types a message? If so, I can make that optional.
-
Hi, There's not really a lot to it. Just install the plugin in your plugins folder, look at rcon or server window to confirm it loaded, then type /perms in chat. You must be admin (auth2), or have the permission, to use the chat commands.
-
BotSpawn does work on CustomMaps but there are assets, seen and unseen, which can prevent npcs from spawning, or moving. The reason I'd test on a proc-gen before anything else is because that proves the issue to your files and settings, or your map. If it proves to your map then there may be something the creator can do. If you have the same issue on proc-gen then that's either a plugin conflict (run BotSpawn + Kits solo to prove), or something I have to look into.
