Direwolf20 Pack [V4] - No Hostile Mobs Spawn

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

danielford167

New Member
Jul 29, 2019
19
0
0
I currently host this server on 1GB (not recommended but its for a small amount of people) but we have been having a problem with "Hostile" Mobs spawning.

So to get the silly mistakes out the way:
Code:
#Minecraft server properties
#Mon Jan 14 15:16:31 GMT 2013
generator-settings=
allow-nether=true
level-name=world
enable-query=true
allow-flight=false
rcon.password=
server-port=
query.port=
level-type=DEFAULT
enable-rcon=true
level-seed=
server-ip=
max-build-height=256
spawn-npcs=true
white-list=true
debug=false
spawn-animals=true
texture-pack=
hardcore=false
snooper-enabled=true
online-mode=true
pvp=true
difficulty=3
gamemode=0
max-players=10
rcon.port=
spawn-monsters=true
generate-structures=true
view-distance=6
spawn-protection=16
motd=\u00A76[V4] \u00A7bDuffia Direwolf20 Server\!\u00A7f [\u00A74HARD\u00A7f]

So when we first started, as expected we had lots of mobs (and died a lot), but after many people got settled we started seeing less and less hostile mobs until we haven't seen any in about 1 week.

So I did some investigating around the map and spawns Thaumcraft 3 aura node is a evil node that throws out Wisps, didnt think this was a problem until..... I found a large circle of 100's of wisps around spawn. I thought this could have caused the problem, and so went around and got rid of most of them and regened the aura nodes and got a happy aura node at spawn.

However these evil nodes seem to be quite common and flux up other nodes, and keep spewing out Wisps, and so I feel that the Wisps are taking all the "mob entities" that can be loaded on the map (I am sure theres a limit).

I secondly thought it maybe to do with the small amount of chunks the server loads for each player, which may cause less mobs to be spawned as the recommended is 7 - 10 for the "view-distance" setting. So I did more testing with that and set it to a max of 25 with no change (except RAM usage wise).

So I was wondering if anyone could tell me a way to either:

1) Increase the Mob Spawn Limit (If there is one)
2) Disable Wisps to see if there the problem.
3) Any suggestions you may have to why this maybe happening.
 

Nessiroj

New Member
Jul 29, 2019
855
0
1
Config files look good so it should work, it could be that the wisps did corrupt 1 or more chunks, whats causing them to not spawn.
Apperently it's happening more, did a quick google search:
http://forums.multiplay.co.uk/minecraft/88334-no-hostile-mobs-spawning
http://www.minecraftforum.net/topic/1110142-monsters-not-spawning-on-server/

No idea if it works, can't replicate it since it works fine on my normal and test server.
I can give you my emailadres or FTP access if you could zip / rar / 7zip send / upload your worldsave see if i have the same problem. If so we can rule out the config settings.

EDIT you could try if you download the save from your server and copy it towards your client saves folder to see if the problem also happens in your single player.
 

danielford167

New Member
Jul 29, 2019
19
0
0
I will ZIP it up and test on singleplayer now and see if I can reproduce if not then it must be something server side.

Add: So after testing in singleplayer mobs spawn and so I dont really know what could be causing it :/
 

Nessiroj

New Member
Jul 29, 2019
855
0
1
Out of options aswell, only thing i can think to check (since it aint a world issue):

Did you change alot in the server config files? If not maybe delete all files on the server make a fresh install and reupload the world (or leave the world and delete all other files and redownload those)
 

danielford167

New Member
Jul 29, 2019
19
0
0
I did that recently with the V4 update which we update to about 3 - 4 days ago, however reading those threads you posted, I see that setting the View Distance lower can affect mob spawns due to the mob spawning distance and so I will turn the view distance up to 10 and I will report back :)

Edit: After setting the view.distance to 10, mobs have started to return to the server :p Thanks for the help Nessiroj

Edit 2: After a few minutes Mobs Stopped spawning again :/
 

Raffel

New Member
Jul 29, 2019
1
0
0
I run a FTB server where I initially set the view-distance to 15, which caused the mobs to disappear. Then I lowered it to 8 which again causes the mobs to glitch out.
I tried several restarts using the original view-distance of 10, and the console commands 'gamerule doMobSpawning false/true' to no avail.

However from another post http://www.creeperlabs.com/threads/hostile-mobs-failing-to-spawn-over-time.645/ it was suggested to go back to the original server spawn.

The fix that worked:

Note that if you have any animal farms, the animals will disappear and you have to herd them again.
If this is a big no-go, try steps 5 - 9 first without doing any changes to the server.

1. Turn off all mob-spawning in server.properties (animals, monsters, npc's)
2. Restart the server
3. Turn them all on again in server.properties
4. Restart the server
5. Destroy your bed
6. Die at night
7. Spawn at the original server spawn
8. Mobs are back
9. Enjoy the sound of exploding creepers
 

Goobdude

New Member
Jul 29, 2019
53
0
0
1. Turn off all mob-spawning in server.properties (animals, monsters, npc's)
2. Restart the server
3. Turn them all on again in server.properties
4. Restart the server
5. Destroy your bed
6. Die at night
7. Spawn at the original server spawn
8. Mobs are back
9. Enjoy the sound of exploding creepers


Well, this fix works temporarily for me, but within a couple of Minecraft days, I'm back to no hostile mobs again. Has anyone made any headway on this?

Oh, and if it helps at all, I play on an Ultimate server, and my view distance in the server file is at 10, with the difficulty at 3.
 

Terregator

New Member
Jul 29, 2019
1
0
0
I ran into a similar problem with my server lately. I just updated it to Direwolf20 1.6.4 version 1.0.16 and after a few hours or playing, no hostile mobs were spawning unless spawned from a spawner or other device. About 5 minutes ago, I typed into the console /cofh killall, and it said Removed 101 hostile entities. (100xarsmagica2.MobHecate, 1xPigZombie).
So I don't think it will be a permanent solution, but hopefully it'll be resolved shortly.
 

KH0RNE

New Member
Jul 29, 2019
1
0
0
The Problem is the following: The Hecate-mob in AM2 1.1.2b is buggy in 2 ways.

The first thing is that he doesnt do anything but standing around doing nothing.
Thats not that bad and im sure most of the players enjoy this fact a little, since Hecates are nasty little things.

The second, extremely annoying bug is that invisible hecate's spawn till the monster cap is reached, disallowing
ANY other monsters to spawn. Soon after a restart or '/cofh killall' more than 80% of all monsters are invisible hecates.

I found a way to FIX BOTH bugs:

Downgrade to AM 1.1.2.

This way you lose only some minor fixes, you keep everything like mage-level/skills/spells/items since the 1.1.2b hotfix doesnt add/remove items.
I highly recommend to backup your server/saves before doing that. Also, DONT delete the AM2 config. This will destroy ANY compability with the dw20 pack
and result in MASSIVE id-conflicts.

The 1.1.2b fix changes the way hecates spawn, making them dependend on the 'average mage-level in the area' or something and i think somewhere there is the bug located.

You may notice, that even after that hecates STILL cant be disabled by other mods/configs etc (still due some bug) but from a 100 monster cap 1-5 are fully working hecates,
which is a great deal compared to other methods. Monsters spawn at the normal rate again. Yay!
 
  • Like
Reactions: Yldron

Earthclaw

New Member
Jul 29, 2019
1
0
0
The Problem is the following: The Hecate-mob in AM2 1.1.2b is buggy in 2 ways.

The first thing is that he doesnt do anything but standing around doing nothing.
Thats not that bad and im sure most of the players enjoy this fact a little, since Hecates are nasty little things.

The second, extremely annoying bug is that invisible hecate's spawn till the monster cap is reached, disallowing
ANY other monsters to spawn. Soon after a restart or '/cofh killall' more than 80% of all monsters are invisible hecates.

I found a way to FIX BOTH bugs:

Downgrade to AM 1.1.2.

This way you lose only some minor fixes, you keep everything like mage-level/skills/spells/items since the 1.1.2b hotfix doesnt add/remove items.
I highly recommend to backup your server/saves before doing that. Also, DONT delete the AM2 config. This will destroy ANY compability with the dw20 pack
and result in MASSIVE id-conflicts.

The 1.1.2b fix changes the way hecates spawn, making them dependend on the 'average mage-level in the area' or something and i think somewhere there is the bug located.

You may notice, that even after that hecates STILL cant be disabled by other mods/configs etc (still due some bug) but from a 100 monster cap 1-5 are fully working hecates,
which is a great deal compared to other methods. Monsters spawn at the normal rate again. Yay!


Has anyone tried going into the config file and setting the spawn rate for hecate to 0, i'll do it on my server but its just a thought