Steenamaroo

Hi, Not sure what's going on there but I'm sure someone can help you out. Have you joined my discord and/or codefling discord? Might be easier to talk it through in one of those.

The name of the first item in electrical has been deleted - "autoturret". "Electrical": { //name should be here with opening bracket "probability": 10, "maxStack": 10, "minStack": 1, "blueprintChancePercent": 0, "skins": [] }, "ceilinglight": { "probability": 10, "maxStack": 10, "minStack": 1, "blueprintChancePercent": 0, "skins": [] }, Attached is a repaired copy. default.json.zip

Those are the correct names ^. Might be easier if you attach a zip with your config file and contents of /data/CustomLoot. I've added error catching code to be released in the next version but that doesn't help you - It just means it'll fail with a nice message instead of red text.

Just tried a few things. The only way I could get the exact error you're getting was to remove one of the item names in a loot table. Like this, for example. "ammo.nailgun.nails": { "probability": 2, "maxStack": 1, "minStack": 1, "blueprintChancePercent": 90, "skins": [] }, //Title missing here "probability": 2, "maxStack": 1, "minStack": 1, "blueprintChancePercent": 90, "skins": [] }, "ammo.pistol.fire": { "probability": 2, "maxStack": 1, "minStack": 1, "blueprintChancePercent": 90, "skins": [] }, Validating and repairing your loot-tables should solve any problems.

k. You must have the same, or a similar, issue in some of your other data files then. If you're using an editor that flags errors I'd open the config and all data files and have a scan through. If not, paste the contents of each into https://jsonlint.com to verify.

I turned this off ^^ @Death

There is no update. I just made a small change to the documentation. UpdatesChecker will notify you if any of my plugins have newer versions available. @Death - ^^^.

The error isn't fixed. "botabag": { "probability": 0, "maxStack": 1, "minStack": 1, "blueprintChancePercent": 0, }, Skins entry is missing. "JsonSerializationException" is the plugin (any plugin) saying data or config is not as expected.

Changed Status from No Response to Not a Bug

Not seeing a problem here with BotSpawn 2.0.8 and DeathNotes 6.3.5.

Hi, Yes and no. It checks when it loads, and when other plugins load. It also checks on an interval, set in your config file. If you want it to check-all on command you can simply reload the plugin.

Ok. Are you on BotSpawn 2.0.8?

Hi Pookins. I'm sorry for the late reply. No idea how but I didn't see this notification. It looks like you have a mistake in your file ^. the entry for "skins" is missing under "botabag"

Also...do I know you from discord?

Hi, Yeah that sounds about right. I'll see about making sure the attacker is correct in the HitInfo. Thanks for letting me know.

Hi, BotSpawn doesn't do anything to the default populations at those two locations. If they're missing it's because the server hasn't been live long enough for them to spawn or they've all been killed by someone or another plugin. If you have CustomLoot installed it has a command "Repop" built in which should respawn those npcs. I put it in mostly for convenience when testing and forgot to remove it.

This is nothing short of badass! Love it!!

P.S. if you're not in here or here you're very welcome.

Keirox's previous bundled files were for an out-of-date BotSpawn and some changes (Bots is now Day_Time_Spawn_Amount) would be needed to make it work with current version but, other than that, his bundled spawn points should work just fine. If a handful of them are too far away from Navmesh that's either an oversight on his part or the result of recent stricter water checks in BotSpawn. Either way you should be able to just manually move the ones which aren't good. If you create a spawn point in, or move one to, an no-good location, current BotSpawn will print a message to chat to say something like 'consider moving this point or enabling Stationary option', so at least you don't have to keep reloading to check if you've fixed it.

Hi, I can't remember if BotSpawn saves down spawns files, from memory, on unload/reload or not but either way you'd be better using the built in chat commands to move spawnpoints. You shouldn't ever need to manually edit a BotSpawn spawns json file. When you've identified a problem spawn do /botspawn edit <thatprofilename> then /botspawn movespawn <TheSpawnPointNumber> It should tell you straight away, in chat, if the new location is too far from navmesh. If it is move around and do 'movespawn' command again until you get a usable spot.

Hi Vector, I replied to your PM saying I think you just need to make sure that the image, if it's full-screen, matches the aspect ratio of your screen or, if this is a smaller image within the screen, that the Left/Right/Top/Bottom values you provide match the aspect ratio of the image. You might want to prep your images in advance to get round numbers, to make it easier to work with. 400x400 is easier to set up than 378x409, for example. There are no examples, other than the default config, but I do plan to provide some, and a video tutorial, in the near future.

Hey. Thanks for letting me know. There may not be much I can do about it but I'll take a look and see what's up.

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" } } },