Steenamaroo
-
Posts
3,660 -
Joined
-
Last visited
-
Days Won
208
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
My pleasure. Thanks for updating.
-
Hi, That works but you have to give each element a unique name. Try changing the second "Content" to "ContentTwo", or something. "Page1":{ "ImageElements":{ "BackGround":{ "URL":"", "GoBehindNav":false, "ShowOnSubPages":"0", "PosBottomToTop":"0.0,1.0", "PosLeftToRight":"0.0,1.0" } }, "TextElements":{ "Title":{ "Content":"Main", "FontSize":16, "AlignTopMiddleBottom":"top", "AlignLeftMiddleRight":"middle", "FontColour":"255,255,255,1", "GoBehindNav":false, "ShowOnSubPages":"0", "PosBottomToTop":"0.0,1.0", "PosLeftToRight":"0.0,1.0" }, "Content":{ "Content":"\n\n TEXT 1.\n ", "FontSize":16, "AlignTopMiddleBottom":"top", "AlignLeftMiddleRight":"middle", "FontColour":"255,255,255,1", "GoBehindNav":false, "ShowOnSubPages":"0", "PosBottomToTop":"0.0,1.0", "PosLeftToRight":"0.0,1.0" }, "ContentTwo":{ "Content":"\n\n TEXT 2.\n ", "FontSize":16, "AlignTopMiddleBottom":"top", "AlignLeftMiddleRight":"middle", "FontColour":"255,255,255,1", "GoBehindNav":false, "ShowOnSubPages":"1", "PosBottomToTop":"0.0,1.0", "PosLeftToRight":"0.0,1.0" } } },
-
Welcome to the party, Nick!
-
Hi, Thanks for pointing that out. I'll update the FAQ. If you're aware of more oversights, please let me know. Thanks.
-
BotSpawn Version issues, Stuff not working/breaking other things.
Steenamaroo replied to Khan's Support Request in Support
Hi, I don't see anything there that relates to BotSpawn. The first error is to do with input error when creating a UI, and the second relates to an SQlite issue, seemingly with a Rust file? If there's a proven issue of course I'll address it but from what you've pasted this looks like coincidence. -
Hi, Pookins, I think I know what the problem is. If you reload and do not delete /data/CustomLoot/default.json, does the problem cease?
-
That answers that, then. Thank you. I tried to track down an issue with airdrop npcs, that Mal was having, quite a while ago but couldn't replicate it. He found he only had a problem when he had them spawn with chutes in a small radius. If your guys are with parachutes try increasing the radius of the aidrop profile a bit. Hopefully I'll figure out what's causing it soon.
-
Hi, It's not but I'll have a think about adding that as an option.
-
This will do what you're asking for. BradleyProtect.cs.zip
- 1 reply
-
- 1
-
-
Hi, It's possible but I think I've seen that coming from CargoShip issues too. If it's coinciding with airdrops I'd say it's probably BotSpawn. If it coincides with CargoShip event, it's not.
-
I'll get back to you. Thanks.
-
You would need 20 spawnpoints and, also, Day + Night spawn amount would need to be set to 20, but if it's a very small area or there are lots of obstacles, some of the spawns may fail. There's a bit of trial and error involved, I'm afraid.
-
Hi, There's no simple true/false solution but you can allow npcs to spawn underground by using custom spawn points. You can enable that option "UseCustomSpawns" per profile, and manage spawnpoints with the chat commands listed in the description.
-
Version 1.0.5
3,588 downloads
Simple set of CUI info pages for Rust servers. InfoScreens offers multi-page, and multi-subpage,information viewable by command and also automatically presented when a user joins the server. Permission infoscreens.show - Enables ability to show info screens to other players. ChatCommand /infoscreen with permission : /infoscreen <playername> /infoscreen <playername <pagename> ConsoleCommand ISWipe – This clears InfoScreens' record of players who have joined the server. Configuration Global. PermaUIButton = false; Creates a permanent 'I' button at screen top right. SideNav = false; - Toggles navigation between top and side. OnlyShowOnce = false; - If true, info is only shown automatically on first-join. NeverAutoShow = false; - Never display automatically on first-join. NumberOfPages = 4; - Automatically creates nav and config entries on reload. GuiTransparency = 0.95; ButtonColour = "0,100,0,1"; ButtonColourSelected = "0,200,0,1"; CommandAlias = "is"; - Alternative, customisable, chat command. Colours accept RGBA – maximums 255/255/255/1 Per-Page. VisibleTo - "default,somegroup" Makes a page only visible to the listed groups. This is comma separated, with no spaces. Each page, by default, has three elements. Two are text and one is image. Each element has the following options. Text Elements Only. "Content": "Some Text Here", - use \n line break for multi-line "FontSize": 16, "FontColour": "255,255,255,1", "AlignTopMiddleBottom": "top/middle/botton", "AlignLeftMiddleRight": "left/middle/right", Image Elements Only "URL": "https://...", All Elements "GoBehindNav": false, "ShowOnSubPages": "0", "PosBottomToTop": "0.0,1.0", "PosLeftToRight": "0.0,1.0" Usage Info. The 'Pos...' entries are on a scale 0-1. Examples. "PosLeftToRight": "0.0,1.0” is full width, left to right. "PosLeftToRight": "0.0,0.5” is half width, left to centre. "PosBottomToTop": "0.0,1.0 is full height, bottom to top "PosBottomToTop": "0.5,1.0" is half height, centre to top Additional elements can be added by copying/pasting/editing name. 'ShowOnSubPages' can be altered and will automatically create next/previous buttons. For example, you could have a background image with "ShowOnSubPages": "0,1,2", then have three content elements showing on "0”, "1”, "2” respectively. This will give three sub-pages with different content and the same background, under one nav-heading.Free -
Examples of How/Additions to SET this up...Please!
Steenamaroo replied to TheEye's question in Support
Hi TheEye, I'm planning to do a basic setup video soon, and include some example loottables with the download, but, for now, here is some info. /config/CustomLoot.json contains all the 'container' categories that CustomLoot can modify. For the containers you want to change you need to specify a loot table name. If a loottable/file of that name doesn't exist, CustomLoot will create it when you reload. You can use the same loottable for multiple container types, or make each container type have its own loot table. That's up to you. Example - "Murderer": { "enabled": true, "lootTable": "MurdererLootTable", "maxItems": 1, "minItems": 1, "gunsWithAmmo": false, "noGuns": false, "MaxBps": 3, "MinWeaponCondition": 50, "MaxWeaponCondition": 50, "ClearContainerFirst": true } With that ^ set up, and the plugin reloaded, you now have /data/CustomLoot/MurdererLootTable.json. Open that. There's two stage probability here. The scale is relative - You make it up. All Item categories are listed then, further down, all the items in each category are listed. You need to set probability greater than one for at least one category and, also, for at least one item with that category. Eg "Weapon": { "probability": 1, "allowBlueprints": true } and "Weapon": { "bone.club": { "probability": 2, "maxStack": 1, "minStack": 1, "blueprintChancePercent": 50, "skins": [] }, "bow.compound": { "probability": 1, "maxStack": 1, "minStack": 1, "blueprintChancePercent": 50, "skins": [] }, ///etc With this set up your murderer corpses will have one item of loot in them. That item will be a bone club or a compound bow, with bone club being 2X more common than the bow. -
It's not about being allowed anything. For that message to show you must have UseCustomSpawns true, and have asked for more npcs than there are custom spawnpoints for that profile. To fix it you'd either need to reduce the number of npcs you're asking for, which BotSpawn does automatically, add some more custom spawn points for that profile, or turn 'UseCustomSpawns' off. For lighthouses and harbours I'd recommend adding more CustomSpawnPoints as those are fussy monuments. The reason for this setup is that BotSpawn keeps track of which of your custom spawnpoints have been used already, and won't spawn two npcs on the same spot. Without that setup if you had 4 spots and 5 npcs, two of them would spawn in exactly the same place. Was never a big deal because they immediately walk around but with having the stationary option now it's better to make sure spawnpoints are npc-unique.
-
Hi pookins. That's not an error. It's just telling you that you've asked for more npcs than there are spawn points.
-
Hi, At present there is not. It only gets saved to SQL table. The same was true for Economics, though, and I recently changed that (not released yet), so I could do the same for play time. Stay tuned. -
No probs.
-
Changed Status from Pending to Closed
-
Hi, The error is telling you have have a mistake in your DefaultProfiles json, at Wild Swamp 1 - BotNamePrefix. It's probably a missing comma or quotation mark, but paste the file contents into this validator if you're having trouble finding it.
-
Best comments ever ^.
-
+1 to that!
-
Loottable, but yes. If that exists and you've reloaded and are still getting the same issue then I'm not sure what it is. Can't replicate so far, other than how I described.
-
The only way I can see this happening is if 'default' loottable has been deleted and isn't in use, then some other plugin makes a call for a config entry that doesn't exist. Under those circumstances 'default' is used, and may not exist. Obviously I need to patch that but, if that is the case, reloading will create default.json and fix it.
