Steenamaroo
-
Posts
3,335 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
Hi, Can you ensure you're on the most up to date public version, please? That's V2.1.5.
-
The given key was not present in the dictionary
Steenamaroo replied to MON@H's Support Request in Support
Ah, yeah. Don't remove MigrationData. I think the title of it literally says "DoNotEdit", no? 😛 Setting Parent_Monument to "" should have no adverse effects, though, other than existing custom spawn points being automatically removed. -
You definitely updated the BotSpawn.cs file? I've updated public now so you may as well get it from there, but I did find an instant-respawn issue with default profiles, and fixed/tested it.
-
ugh, really? Ok, I'll have a look this evening. I made some changes to how custom spawn points are handled and it's had a few knock-on effects. Thanks for letting me know. Depending on the terrain around the lighthouse it may be very difficult to get random spawn points. In some cases custom spawn points may be necessary but they auto-migrate at wipe now (if you set Parent_Monument correctly before adding points) so at least it only needs done once.
-
Should be all good now @MastrJedii
-
Waiting for feedback on something else before releasing a public update (...again<sign>). Here's the respawn fix until then, for anyone who wants. BotSpawn.cs
-
The given key was not present in the dictionary
Steenamaroo replied to MON@H's Support Request in Support
@Sasquire- I'm not finding this one. Do you know the steps to reproduce it? Thanks. -
On it. Thank you!
-
The given key was not present in the dictionary
Steenamaroo replied to MON@H's Support Request in Support
Hi, Thanks for the info. No, Parent_Monument isn't (shouldn't be...) required - This is a bug that I'll fix. Got a few small things to fix so I'll most likely update some time today. -
The given key was not present in the dictionary
Steenamaroo replied to MON@H's Support Request in Support
Nice. Thank you. -
The given key was not present in the dictionary
Steenamaroo replied to MON@H's Support Request in Support
All good now? @MON@H -
The given key was not present in the dictionary
Steenamaroo replied to MON@H's Support Request in Support
Fixedamaroo. -
@Vedder Thanks for the screen shots. The plugin is unloading itself because ImageLibrary.cs is not installed. @TF Crazy If ImageLibrary is a requirement that really should be in the description. You should probably enable Support for your plugins too, so that reports are separate and organised. It's easier to keep track that way. Discussion/comments, ideally, is for suggestions and remarks. -
Have you altered the config value for chat command? `Command chat": "info"` If not, I don't see anything about permissions or auth level so it sounds like the plugin isn't loaded. Get your server console, or rcon, open and `oxide.reload CInfoPanel` Watch console to see if there are any errors. If you do see some error delete the config .json for this plugin and reload again. If there's still an error, please screen shot it or paste it here.
-
Hey Vedder. As I mentioned, the developer is going to need some details. How, exactly, is it not working? Describe your experience, please.
-
Custom locations (position relative to parent) are wrong after each wipe after last update
Steenamaroo replied to MON@H's Support Request in Support
Ok, thanks. I'll take a look. I may have updates pending - If so there'll be a new version released later today. Thanks for the info. -
Custom locations (position relative to parent) are wrong after each wipe after last update
Steenamaroo replied to MON@H's Support Request in Support
I asked people to test this for me and report back - from what I gather the issue is fixed in V2.1.2. Did you update to V2.12, set Parent_Monument for some profile, then `/botspawn move <profilename>` to where it's meant to be, and then see a failure to relocate after a wipe? If so, please share your custom + default data profile files and I'll take a look. -
Custom locations (position relative to parent) are wrong after each wipe after last update
Steenamaroo replied to MON@H's Support Request in Support
Hi, There was an issue in 2.1.1 which is now resolved. I introduced auto-relocation of custom spawn points, using the same Parent_Monument setting, but accidentally broke/disabled the relocation of custom profiles locations, meaning if you use Parent_Monument to relocate an entire profile (UseCustomSpawns : false) it wouldn't have worked. The solution is to update to V2.1.2 then manually put your custom profiles back where they need to be, with the `/botspawn move <profilename>` chat command. After that's done custom profiles and custom spawn points should all automatically re-locate after a wipe, when Parent_Monument is used. -
Custom Spawn Odd message and/or no spawn
Steenamaroo replied to Finchy911's Support Request in Support
Hey, That's great to hear. Thanks for the update. Glad things are working well again. -
No worries. regular players are Auth Level 0, Moderators are 1, and Admin/Owner are 2. No one should have auth 2 except the server owners. BotSpawn commands can be run by anyone who is Auth 2, or anyone who has the botspawn use permission.
-
Custom Spawn Odd message and/or no spawn
Steenamaroo replied to Finchy911's Support Request in Support
AdjustPopulation - Thought that might be the case. I'll get it sorted but, for now, just try to make sure each custom spawn point you place is definitely on navmesh. Not sure why they aren't spawning with Stationary: true - I'll look into that too. Thanks. -
Auth level 2, or the permission.
-
Custom Spawn Odd message and/or no spawn
Steenamaroo replied to Finchy911's Support Request in Support
Is there a more detailed error in the logs? Usually it gives you a trace - The name of the method. I expect it's "AdjustPopulation()" but if you can confirm that'd help. -
Custom Spawn Odd message and/or no spawn
Steenamaroo replied to Finchy911's Support Request in Support
Hi, I'm not sure why it's throwing that error. It should be set up to tell you, politely, if there's no navmesh or no custom spawn points or whatever. Throwing an 'index out of range' exception is no good. I don't have the code open right now but I think I put a navmesh check in when spawn points are added, so you should be able to know then and there if a point wont work and just remove it. I'll take a look tomorrow and see if I can figure out why it's able to throw errors. -
I don't think that's possible. Are you 100% sure you have auth-level two or the botspawn permission? Either should let you use the /botspawn in-game chat command. If you're sure of that, watch the server console while you do the `/botspawn add ***` command, to ensure it isn't throwing some error. If there's an error, please paste here.
