-by "regenerating", I mean that my spawnlist entries are being overwritten with default values. As far as I can tell, it's only happening with the MoCreatures Spawn List Entries.

This spawnlist was working fine pre 0.15.. I've tried changing the "FILE_VERSION" from "1.0" to "2.0".

I've tried manually re-editting it (which took ages. It would have to be MoCreatures ) and I I've tried editing the first 2 entries of the regenerated file, saving, then using the command "/jas loadconfig". Those first 2 lines were reset to default values. I don't know what else to try.

Is there a reason why it would just be MoCreatures?

What'd you do to fix this? How do I fix it? I'm running Mo's creatures on my server with JAS and thousands of mobs are being spawned every minute, causing the server to lagg badly.

They DO spawn where they should but they spawn in too large quantities, nomatter how much I change the spawn cap or despawning timer / radius they keep on spawning each time i leave the area and return they're more.

What should I do?

how did you fix this?

Thanks in advance.

Radixy, make sure you disable spawns done by MoCreatures itself.
Open the Mocreatures ini's and set all the spawn chances to 0.

Mo Creatures has always spawned WAY too many of every creature. Even if you disable vanilla spawns, they will still happen because Mo Creatures has its own system.

####################

ant

####################

ant {
B:canspawn=false
I:frequency=7
I:maxchunk=4
I:maxspawn=4
I:minspawn=1
}

####################

bear

####################

bear {
B:canspawn=false
I:frequency=6
I:maxchunk=4
I:maxspawn=2
I:minspawn=1
}

Etc... I've set all of them to false. If that's what you mean by ini. I just went to
\minecraft\config\MoCreatures and edited the two cfg files.

I'm playing on MC 1.7.10 btw. With the Mo's creature version being Mo'Creatures 6.3.1

What version of MoCreatures?

And I assume the version of MoC is unchanged from when it was working on 0.15 to not on 0.16.1

Cannot seem to reproduce using JAS v0.16.1 and MoC v6.3.0

Newly generated config file. Changing value Beach.MoCreatures.Ant and Beach.MoCreatures.Bee and running loadconfig results in the value not being changed.

Thoughts:
The changes are formated incorrectly and cannot be read?
Entity mappings are changing / not saving (set to read only?) and thus Moc are detected as new mappings.

Is there anything about MoC settings you've changed?

In temporary save settings, the file version is set to 1
{
"FILE_VERSION": "1.0",
"_IMPORTANT": "# DO NOT TOUCH. Internally used to remember how the Configuration file was actually saved.",
"Use_Universal_Entity_CFG": false
}
but I notice at the top of every spawn list entry file, the "FILE_VERSION": "2.0",

My old pre 0.15 configs have "FILE_VERSION": "1.0",

The entity handlers folder AND the spawn list entries folder were set to read only. I've never touched these settings or even looked at them until now. Seems strange that the spawn list entries folder would be set to read only. JAS certainly had no trouble writing the conversion outputs to the files within.

update: having removed the read only setting from everything, I find the files are still being overwritten. This time I altered the entry for in BEACH for BiomesOPlenty.JungleSpider. It was reset.

Next step, newly generated configs - compare "file version" in GlobalProperties.cfg, LoggingProperties.cfg, temporarySaveSettings.cfg, etc

hm.. completely regenerated the entire JAS folder, opened up the vanilla.cfg spawnlist entry in Notepad++, change the weight for Bat in Beach to 0, then run /jas loadconfig, open file again in Notepad++ and find the weight is set back to 10. What am I doing wrong?

Just to add, the EntityHandlers don't seem to be rewritten. The BiomeGroups.cfg isn't being overwritten either.

I've just heard from Blue on the forums that it's not just MoCreatures. MoC v6.3.0. I'm starting up again now and will look at it again. It was late last night that I first reported this - time difference is annoying.

Not sure what the issue was. I couldn't reproduce it in dev, but when I tried the uploaded version it was indeed happening. I recompiled and tested live and it doesn't seem to have the issue. I've uploaded it as v0.16.2.

thank you. I'm beginning to think there's still an issue though, sorry and it's got me stumped. I've only tried it with BoP so far (basically because it's near the top of my list). I will try with Vanilla.cfg in a second.

I've transferred my old biomeGroups.cfg and the converted EntityHandlers files from my backup. Then I deleted the spawnlist entries, exited and reloaded the world to let the lists regen with my edited biome groups.

I then open up the BoP spawnlist entry and change the first value for BEACH - Bird. It previously had a 0 weight for Bird and a weight of 8 for jungle spider. I changed it to look like this:
{
"FILE_VERSION": "2.0",
"SORTED_BY_BIOME": true,
"SPAWN_LIST_ENTRIES": {
"BEACH": {
"AMBIENT": {
"BiomesOPlenty.Bird": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "1-4-0-4"
},
"BiomesOPlenty.Pixie": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-0-4"
}
},
"CREATURE": {
"BiomesOPlenty.Rosester": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-0-4"
}
},
"MONSTER": {
"BiomesOPlenty.Glob": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-0-4"
},
"BiomesOPlenty.JungleSpider": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-1-3"
},

..then I do /jas loadconfig, reopen the config file and find the entry is now
{
"FILE_VERSION": "2.0",
"SORTED_BY_BIOME": true,
"SPAWN_LIST_ENTRIES": {
"BEACH": {
"AMBIENT": {
"BiomesOPlenty.Bird": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "1-4-0-4"
},
"BiomesOPlenty.Pixie": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-0-4"
}
},
"CREATURE": {
"BiomesOPlenty.Rosester": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-0-4"
}
},
"MONSTER": {
"BiomesOPlenty.Glob": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-0-4"
},
"BiomesOPlenty.JungleSpider": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "8-4-1-3"
},

I'm scratching my head here. I'll check with Vanilla and then try from a freshly generated set of configs again.

Some more debugging: Settings the weight to 0 seems to cause it to reset to default

Strange.. I just deleted the contents of the EntityHandlers and SpawnListEntries folders, let them regen..

Then I changed the Vanilla.cfg SpawnlistEntry
"FILE_VERSION": "2.0",
"SORTED_BY_BIOME": true,
"SPAWN_LIST_ENTRIES": {
"BEACH": {
"AMBIENT": {
"Bat": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "10-4-8-8" <changed 10 to 0
}
},
"CREATURE": {
"Chicken": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "0-4-0-4" <changed the 0 weight to 1

...just saw your message. Yes that's what I've found. My vanilla.cfg got changed back to

"FILE_VERSION": "2.0",
"SORTED_BY_BIOME": true,
"SPAWN_LIST_ENTRIES": {
"BEACH": {
"AMBIENT": {
"Bat": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "10-4-8-8"
}
},
"CREATURE": {
"Chicken": {
"Weight-PassivePackMax-ChunkPackMin-ChunkPackMax": "1-4-0-4"

Seems the issue was relatedto the 'improved' conflicted mapping detection combined with the new mapping detection. Entities that already existed were being detected as 'new' so were trying to be regenerated. Incidently due to how it is setup the regenerated value is ignored if the spawnentry is 'valid' i.e. is set to spawn.

Should be fixed in v0.16.3. For real this time.

Then I happily close this.

I can verify it is working this time. Thank you.