-
Posts
3,236 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
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.
-
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.
-
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.
-
@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.
-
Hi, If it created a config file then it definitely loaded. You shouldn't see "unknown command" You'll need to either have the permission botrespawn.allowed, or be admin, then the chat command is /botrespawn There won't be any npcs until you get into the UI and set up some profiles. All of the default ones are set to AutoSpawn : false by default.
-
@Tanki - I found it. I cache it with ImageLibrary in RustRewards so the url is only accessed by the plugin once a month. Should work fine if you right click and copy image address here, then use that in your config. I'll change the default value so it's hosted at Codefling for new users from now on.
-
My pleasure. Glad to help. You've understood perfectly but there's an additional option in the global settings called Remove_BackPacks_Percent which may be set to 100. If you set that to zero all your BotReSpawn corpses will then leave backpacks and your timers in minutes will apply. You can use that Remove Percent option to make it that there's backpacks sometimes, and other times not, and balance it to your preference, or just go with 0 so backpacks always spawn. If you're gearing up to make them more difficult don't forget they can use (nearly?) every weapon. Bots with MGL or flamethrowers, rocket launchers, and even grenades, beancans, satchels, or c4! as backup weapons when line of sight is broken can be great fun.
-
Hi @ClockworkCat You found one solution. As long as that new profile remains parented to Airfield, the npcs from that profile will always spawn where you placed them relative to the airfield, so if you change maps and the airfield moves, that profile and its npcs will appear to be in the right place. There is another way just using just one profile. If you go into the UI and view the manually placed spawnpoints for the profile you should see an 'Edit overrides' button for each point. In there you can choose a kit (and some other settings) which are different from the main profile's settings. For example the main profile could be set to use kit 'soldier1' but one specific spawnpoint overrides that and uses 'soldier2', or whatever. On a per-point basis you can override the settings for stationary, Kits, Health, and RoamRange. If you need more control than that then the two profile approach is better.
-
When using Homing Launcher, im not getting points for killing
Steenamaroo replied to Tobie's Support Request in Support
Thanks for letting me know. I'll look into that. -
- 222 comments
-
- 1
-