Steenamaroo
-
Posts
3,330 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
I like you a normal amount.
-
Hi, Surprisingly, no. That wasn't behind a config option. I've added it now so the next version will have 'Corpse_Has_Skull` true/false.
-
There is Disable_Non_Parented_Custom_Profiles_After_Wipe : false will do what you want. Be aware, though, this is only useful if you recycle the same map each wipe. If you're not recycling then the locations for the npcs wont make sense on your new map.
-
yesterday's facepunch update broke the plugin
Steenamaroo replied to Tage2's Support Request in Support
Thanks for updating here. Glad it's not broken. 😂 You can add pr there and reload, or just use ranks. Whatever suits. -
yesterday's facepunch update broke the plugin
Steenamaroo replied to Tage2's Support Request in Support
It's working perfectly here. Check your config file to make sure "pr" is listed under `chatCommandAliases` It may be that it's just missing in there. -
yesterday's facepunch update broke the plugin
Steenamaroo replied to Tage2's Support Request in Support
Hi, Are you seeing any console errors when you try to use it, or any message in chat? You're the only person to report although that doesn't necessarily mean there isn't a problem. -
Sorted, thank you.
-
No problem, thanks for letting me know. That makes sense as an admin option, being able to easily and quickly TP to a raidable base to check it out. ðŸ‘
-
Hi, I think I’m following. Are you talking about the minStack/maxStack options, and setting that min to zero? If so the plugin should just completely ignore any items where minstack, or maxstack, is zero, so they’ll never be picked or created. If you’re just talking about probability of zero then any category set to zero (and all of the items in it) will be ignored, and any item set to zero, regardless of its category’s probability, will be ignored. If there’s only one category and item (in it) with probability above 0, then that item will always be picked and created, cos there’s no other choice. I order to give that item a chance of not being picked, there needs to be at least one other viable item which could be picked instead. I.E. You can set the plugin up to create wood or stone, for example but you can’t set it up to create wood or nothing. It’s hard to describe but people usually get a feel for it. If everything was probability zero except for category tools 1 item timed explosve 1 category Resources 9 item wood 1 item stone 1 Then for every item created there’s a 9 in 10 chance it’s going to be a resource, and beyond that it’s a 50/50 whether it’s wood or stone. 1 time in 10 the item will be a tool and if it is a tool, it’s guaranteed to be c4, because there’s no other option. When people are starting out I often suggest that they pick a handful of common items that could make up their base common loot, and set the probabilities for those items to something a good bit above zero, to allow room for other things to be less common. Say you have wood with a probability of 10, for example, you could then have stone at 7 so it’s less common and scrap at 3 so it’s even less common. If the only category enabled was resources with those three items set that way, and the profile’s asking for one item (for simplicity) then, on average, you’d get scrap 3 time out of 20 stone 7 times out of 20 wood 10 times out of 20. Of course I don’t expect anyone to follow the actual fractions like but you get the idea - It becomes a ‘feel’ thing. -
Hi, If it's showing you the correct message "Grid TP map right-click has been disabled", but right click TP is still working, but only on one server, then I'd guess you've got a second mod that's enabling right click to TP. Try temporarily unloading everything, then loading GridTP, to confirm. ðŸ‘
-
Oh sorry, I misunderstood. If they're getting loot with a fresh table then you're right - It's coming from somewhere else. Sorry, I'm not sure what else to suggest other than maybe temporarily unloading everything except BotReSpawn and CustomLoot, just to prove?
-
Ok, that's good to know. If you made a new loot table and the bot inventory was completely blank, then that means CustomLoot is working, which almost certainly means the loot you saw came from CustomLoot. Any chance the loottable you wanted to use just isn't set up how you thought it was? Some copy/paste mistake or..something? I just tested here with SuperMarket BotReSpawn profile and a loot table with Ammunition 1 and ammo.grenadelauncher.buckshot 1 and nothing else changed, and the npcs had nothing but 40mm buckshot on them.
-
Ok, I'll fire up and test here in case there's something unique to that BotReSpawn profile.
-
If you reload CustomLoot and watch the console do you see any complaints? It's possible there's a mistake in the Market.json - If so CustomLoot should tell you when it loads/reloads.
-
It would be set true by default and probably should be true in most cases. You'd only set it false if you want CustomLoot to add to whatever is already there, be it vanilla loot or stuff from a kit. If you're seeing vanilla loot (or anything that's not from your CustomLoot table) in those npcs then either something else is giving them loot after CustomLoot, or CustomLoot just isn't firing for those npcs at all, although I'm struggling to see why one specific BotReSpawn profile wouldn't work when others do. I suppose a simple troubleshooting tip would be to change "Market" to a made up name - Some table name that doesn't exist, then when CustomLoot creates a file for that name, do not edit it. That way it'll be really obvious if it's working or not because the npcs should get absolutely nothing. CustomLoot should clear their container, and give them nothing. If you find loot in there that would definitely point to something giving out loot after CustomLoot has done its bit.
-
I see you've got ClearContainerFirst set to true so I'd guess something else is giving them loot after CustomLoot, or what you're seeing is stuff from their kit possibly?
-
Hi, It sounds like the plugin isn't loaded. Maybe you didn't grab the most recent essential update for wipe? Download again to make sure you're on V1.2.7.
-
I'm glad you got a solution and thanks for sharing it. Feel pretty bad that you've been doing all your spawnpoints manually every month for two years! I went to quite a bit of trouble to try to make it all as easy and seamless as possible. CustomLoot, on the other hand... Different story. 😂 -
Strange. That has to be something external renaming the file. Do you have any kind of automated backup system or something that could be doing it? It's certainly not something BotReSpawn is doing, anyway, but it makes sense that BotReSpawn would create a new blank file if something/someone renamed the old one.
-
Wow, that's a new one to me. Why was that happening, do you know? I'm relieved, lol.
-
That doesn't sound right. BotReSpawn only wipes custom spawnpoints in cases where the user has changed the setting for "Parent_Monument", just because of how it's written...setting parent monument needs to happen before spawnpoints are added. Certainly for default monuments, and custom spawnpoints you add should be good forever. If you set a bunch of custom spawnpoints for, say, the Airfield profile, no matter what map you change to those npcs should always be in the right place, relative to the airfield. Do you keep the same map wipe after wipe?
-
Hi, It depends what you mean. Custom spawnpoints added for default profiles (monuments) should never need to be updated or redone, because those spawnpoints will automatically move to where the monument is when you change to a new map. For Custom profiles with custom spawnpoints, BotReSpawn automatically disables these profiles when you change maps, because those spawnpoints will no longer make sense on a new map. The exception here is servers which recycle the same map over and over where, of course the points will make sense, so I provided the option Disable_Non_Parented_Custom_Profiles_After_Wipe for those users to set to false. For Custom profiles that you've added which are meant to supplement default profiles - I.E. additional profiles at the airfield, dome, etc, you should set "Parent_Monument" for your custom profile to the name of the default profile it's meant to be near. That can be done with clicks in the UI. If you do that, then add your custom spawnpoints to the custom profile afterwards, that custom profile will act just like a default one, meaning the custom spawnpoints and profile will always relocate to where the monument is on your new map. Basically default profiles are set and forget, custom profiles parented to default ones are set and forget and custom profiles "in the wild" will need to be redone if/when you change your map. Does that answer what you're asking, or are your circumstances different? Let me know. ðŸ‘
-
No, I have a 'proper' update with quite a number of fixes and additions, but didn't want to push that for forced wipe, so the most recent update is literally just a patch for Rust's update.
-
@raviolithecatYou good? For clarity, botrespawn.allowed isn't a command - It's the permission required to use this UI, if you're not admin. If you are admin (auth level 2 - Console will tell you when you join), then it doesn't matter. To grant a permission type oxide.grant user 765611980******** botrespawn.allowed into server console window, but with your full steam ID instead of my placeholder. The command to access the UI is a chat command, entered in game - It's /botrespawn If you still see unknown command then the plugin isn't loaded, and console will have some information about why. You can o.reload BotReSpawn ( or c.reload BotReSpawn if you're on Carbon), then watch the console for warnings or errors and let me know. If you're still having trouble maybe we can connect on discord or something and get it sorted.
-
Something strange going on, for sure. "Unknown command" would mean either you're typing the command wrong, which I doubt, or the plugin isn't loaded. Could it have become unloaded for any reason? Pull up your console and do `o.reload BotReSpawn` then watch to see if you see any errors or complaints.
