neat :3

Is there a version of this that lowers the spawn rate?

alright then thank you

The mod does not use apexmutant.

Caused by: (SpawnTypeDatabaseException) Duplicate spawnType named 'apexmutant' in config file '/spawntypes/uniques.spawntypes' does this mod use apexmutant???

It's compatible in that it won't cause any crashes or anything. But the camps will only spawn on vanilla biomes though, I believe.

is this fu compatible??

I believe this is the item they're wearing:
https://starbounder.org/Ragged_Cape

how do you get that black cloak on the glitch on that picture

Alright, glad it worked out for you!

It works! No crash and the guys are shooting at my character instead. The fix is much appreciated.

Apologies for the delay, I had to do something after my last message.

Anyways, try this: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?edit=true&id=2324648115

I'm not sure if it will work, but it's worth a shot I suppose.

I encountered a scavenging divers on the other ocean planet in the same system as the one with the problematic world file, without experiencing any errors. No errors about it listed in the log file either.

That's fine with me.

Let me know how that goes.

I think I can probably upload an unlisted mod that adds in diverCamps to fill that buggy void, and link it to you, assuming steam lets me do that. Think that'd be okay with you?

My memory's not good for the timeframe planet-wise, but I do know I've had your mod installed for quite some time, well before you renamed the dungeon files. And yes, the camp is underwater, that's where this error keeps spawning, when I go near it with a submarine. I'll check for other diver camps soon.

Looking at the name, diverCamps is most likely the previous name for Bcamps-diverCamps.

I fear that when I changed the names for the camps, there might have been some sort of side-effect with the diverCamps, since I handled them differently from the others (due to the fact that ocean floors don't normally spawn camps.)

A few questions:
The camp in question IS underwater, right?

How long have you had this mod installed? And when did you first visit the planet where this problem occured? (that's if you can remember, of course.) I want to know whether this was before or after I made the name-change update.

Did you check other ocean planets? Do any of the diver camps you encounter there give you the same problem?

I could try a bit of a haphazard solution, by creating another dungeon file named diverCamps, but I'm a little concerned about any potential issues it could cause. Want to know what you'd think of it.

Here's the full error listing. https://pastebin.com/jZzDEwc6

It only causes a crash when going near it, and kicks me up to my ship (or at least into a void that's supposed to be my ship, which will kill me if I don't warp back down the planet ASAP, but that's modlist loading issues more than anything, I think). The rest of the planet is still viable except for that one cell.

Can you show me the line in the log file that mentions the "diversCamp"?

I'd appreciate it. My guess however was that your update to change the camp names is what might've caused this problem, unless it's supposed to update. I don't know how world files are handled but I don't want to delete the one I'm on 'cause I've put too much work into a base I made on it.

The diver camps in my mod are called Bcamps-diverCamp. I'm not sure if I missed something in my mod, it's too late at night for me to check right now. I'll try to take a closer look later.

Is the dungeon "diversCamp" something from this mod? I'm getting an error about that dungeon spawn on a particular planet, and I think this is the only mod I have that would cause it.

Just dropping in to let you know what I found out (and that's the last of this). Upon closer inspection of the log file, the error was caused by a failure to place a dungeon called floranhutvillage (which is in the base game files), due to failing to place some ceiling bones and a tanning rack (floran-themed furniture I assume). After banging my head several times trying to find out what could be causing this, I resigned myself to the idea that it might just be a generation error, as I could not find any mod that alters these in particular.

It's fine, I feel like the changes I made was something I oughto have done a while ago anyways.

Also, I thank you for your quick response in the matter.

It seems the problem is something else. The changes you have made have done nothing. Worse, the problem happens even without your mod. As such, it is from somewhere else. I will review what other mods I have and see what might be causing the error. I apologies for wasting your time with this.

I updated the mod, hopefully without accidentally breaking the entire thing due to a typo or something of the sorts

if you're still having trouble, please post the entire log into https://pastebin.com/ and link it to me so I can take a better look at it.

[24] 7ff69bdd0677 std::_Func_class<std::shared_ptr<Star::SpawnTypeDatabase> >::operator()
[25] 7ff69bee200f <lambda_770d99c769b4950d94783c330804382d>::operator()
[26] 7ff69ba31ce2 Star::WorkerPool::WorkerThread::run
[27] 7ff69ba36d9e Star::ThreadImpl::runThread
[28] 7ffbc3797bd4 BaseThreadInitThunk
[29] 7ffbc536ce51 RtlUserThreadStart

[14] 7ff69bfc3669 Star::WorldServer::generateRegion
[15] 7ff69bfc1fb5 Star::WorldServer::findPlayerStart
[16] 7ff69bfc7080 Star::WorldServer::init
[17] 7ff69bfb03c2 Star::WorldServer::WorldServer
[18] 7ff69bed94f3 std::make_shared<Star::WorldServer,std::shared_ptr<Star::WorldTemplate> & __ptr64,std::shared_ptr<Star::File> >
[19] 7ff69bee1d31 <lambda_755fc2d76450663a5bb16a372c158895>::operator()
[20] 7ff69becd00f std::_Invoker_functor::_Call<<lambda_755fc2d76450663a5bb16a372c158895> & __ptr64>
[21] 7ff69bed40d6 std::invoke<<lambda_755fc2d76450663a5bb16a372c158895> & __ptr64>
[22] 7ff69becfbf9 std::_Invoke_ret<std::shared_ptr<Star::WorldServerThread>,<lambda_755fc2d76450663a5bb16a372c158895> & __ptr64>
[23] 7ff69bee5a16 std::_Func_impl<<lambda_755fc2d76450663a5bb16a372c158895>,std::allocator<int>,std::shared_ptr<Star::WorldServerThread> >::_Do_call

Caused by: (JsonException) Improper conversion to JsonArray from string
[0] 7ff69ba3a213 Star::captureStack
[1] 7ff69ba38f9e Star::StarException::StarException
[2] 7ff69b9d47fa Star::JsonException::format<Star::String>
[3] 7ff69b9e2212 Star::Json::toArray
[4] 7ff69bca9180 Star::NpcDatabase::generateNpcVariant
[5] 7ff69bf74f67 Star::DungeonGeneratorWorld::spawnNpc
[6] 7ff69bb58d40 Star::Dungeon::DungeonGeneratorWriter::flush
[7] 7ff69bb53407 Star::DungeonGenerator::buildDungeon
[8] 7ff69bbe885d Star::MicroDungeonFactory::generate
[9] 7ff69bf6dcca Star::WorldGenerator::generateMicroDungeons
[10] 7ff69bfe0e20 Star::WorldStorage::generateSectorToLevel
[11] 7ff69bfe0d5d Star::WorldStorage::generateSectorToLevel
[12] 7ff69bfe0d5d Star::WorldStorage::generateSectorToLevel
[13] 7ff69bfdf284 Star::WorldStorage::activateSector

[24] 7ff69bdd0677 std::_Func_class<std::shared_ptr<Star::SpawnTypeDatabase> >::operator()
[25] 7ff69bee200f <lambda_770d99c769b4950d94783c330804382d>::operator()
[26] 7ff69ba31ce2 Star::WorkerPool::WorkerThread::run
[27] 7ff69ba36d9e Star::ThreadImpl::runThread
[28] 7ffbc3797bd4 BaseThreadInitThunk
[29] 7ffbc536ce51 RtlUserThreadStart

[15] 7ff69bfc1fb5 Star::WorldServer::findPlayerStart
[16] 7ff69bfc7080 Star::WorldServer::init
[17] 7ff69bfb03c2 Star::WorldServer::WorldServer
[18] 7ff69bed94f3 std::make_shared<Star::WorldServer,std::shared_ptr<Star::WorldTemplate> & __ptr64,std::shared_ptr<Star::File> >
[19] 7ff69bee1d31 <lambda_755fc2d76450663a5bb16a372c158895>::operator()
[20] 7ff69becd00f std::_Invoker_functor::_Call<<lambda_755fc2d76450663a5bb16a372c158895> & __ptr64>
[21] 7ff69bed40d6 std::invoke<<lambda_755fc2d76450663a5bb16a372c158895> & __ptr64>
[22] 7ff69becfbf9 std::_Invoke_ret<std::shared_ptr<Star::WorldServerThread>,<lambda_755fc2d76450663a5bb16a372c158895> & __ptr64>
[23] 7ff69bee5a16 std::_Func_impl<<lambda_755fc2d76450663a5bb16a372c158895>,std::allocator<int>,std::shared_ptr<Star::WorldServerThread> >::_Do_call

Lets see if these extracts are of use:

Caused by: (DungeonException) Error generating microdungeon named 'encounterdungeons'
[0] 7ff69ba3a213 Star::captureStack
[1] 7ff69ba38f9e Star::StarException::StarException
[2] 7ff69ba39088 Star::StarException::StarException
[3] 7ff69bb4c110 Star::DungeonException::DungeonException
[4] 7ff69c370544 `Star::MicroDungeonFactory::generate'::`1'::catch$318
5] 7ffbbd151030
[6] 7ffbbd154388 is_exception_typeof
[7] 7ffbc53a0616 RtlCaptureContext
[8] 7ff69bbe885d Star::MicroDungeonFactory::generate
[9] 7ff69bf6dcca Star::WorldGenerator::generateMicroDungeons
[10] 7ff69bfe0e20 Star::WorldStorage::generateSectorToLevel
[11] 7ff69bfe0d5d Star::WorldStorage::generateSectorToLevel
[12] 7ff69bfe0d5d Star::WorldStorage::generateSectorToLevel
[13] 7ff69bfdf284 Star::WorldStorage::activateSector
[14] 7ff69bfc3669 Star::WorldServer::generateRegion

I think some people use pastebin for that kinda stuff, but I've never used that site enough to know how it works exactly.

But I think it'll be enough to just post the line where the error was stated here.


Right now I will assume this might be another naming conflict, I'll go ahead and rename the files again and see if that changes anything.

Right, I have an extract which I hope is adequate, after I cleared the world where the error happened previously. It happened again, as I hoped. I apologies for I do not know how to attach a file to the comments. Is there anyway I can attach a file to these comments?

And, of course, I didn't keep the .log file for future reading (I am sorry, really). When I initially read through it, I couldn't understand what it was referencing, what I did notice was that the cause of error was with "encounterdungeons", something about not being able to generate a microdungeon, but I didn't bother to remember the details. Please wait and I will reinstall the mod and revisit the location again (I will likely replicate the effect and provide a copy of the section).

Did the .log file not tell you which one it was? Did it simply just tell you that it was the "encounterdungeons.dungeon" file?

Greetings. I am popping in to let you know that I have found an error when using your mod. When I was going through a forest world, I was being constantly booted back to my ship. By inspecting the .log file, the problem was because of an microdungeon failing to generate. Going through my mods which add microdungeons, I have found, through process of elimination, that this mod was causing it. I have used your mod for quite a while now and, although I had some rare problems, I unfortunately can't tell which one of your additions is causing this (I haven't unpacked your mod to check), but my guess would be that it is either the camp of floran cannibals or one of the novakid ones. I have encountered the other ones in the past. Also, thank you for creating this and bringing more npcs trying to kill me while I explore.

Thanks!
Yeah missing/extra commas are probably the most common problem cause.

I went ahead and did as you asked.
I actually put those commas in there in the first place due to the fact that whenever my mods crashed my game while testing them, it was usually due to me forgetting to put in a comma.
But my game didn't crash when I removed them, so it's probably fine now.

Let me if know if there are any problems.

Hey, just wanted to let you know that there is a typo in the "npcthreats.config.patch" file.
At the end of both "value" tags there is an extra comma at the end " ], " and so the patch is not being applied.

or even more idk

They're twice as common as vanilla bandits/occasus cultists

Pardon, false alarm, Steam update seems to have changed the handling of how Workshop mods are downloaded and has been causing my stuff to get corrupted.

So, strange issue: If the loading order of the pre-load is the same as the actual load order (Priorities etc), then the moment my game is trying to load this mod, it crashes saying "exception thrown, shutting down: (AssetSourceException) Packed assets file format unrecognized!".

Not sure what that implies, will try redownloading the mod.

So i've only done a quick check so far but it seems to be working. I was able to beam down to a planet with no problem.

Also if you're having problems, do like Adenn666 did and provide logs! It helps me identify them!

I updated it again, don't hesitate to tell me if any problems persist!

Wait, hold on.... I think I might have found the problem.

I'll update it again, please excuse my incompetence.

Went ahead and reverted it, are people still having problems?

Because it turns out I can't just simply rename the files and expect nothing to go wrong.