Crash based on mob spawners and agitators?

[ObeliskofDeath]

Issue / Bug

I had the issue earlier in the day, playing on LAN, my brother was making a grinder and it seemed that a certain spawner crashed the game on my end, closing the connection. I re-launched the game and the same thing happened. Next time, I logged in and changed the difficulty to peaceful, eliminating the mob. This time when my brother logged in and rendered the chunk, the mob didn't exist and we proceeded as normal. Now a similar thing has happened, however with no way to log in. I have tried profiles outside of the render distance of where we believe the crash is originating from, with no luck. I even tried changing the difficulty in the game files in options but to no avail.

Possible Solution

I have no idea, I don't know anything about coding or computers really.

Steps to Reproduce (for bugs)

1. Open Game
2. Open saved game
3. Loading world
4. Rendering Chunks
5. 0%
6. Crash

Context

Just trying to play the game, have had very few issues until now

• Crash Log: https://pastebin.com/eEmF1txK

Client Information

• Modpack Version: 3.0.6
• Java Version: 1.8.0_25
• Launcher Used: Native
• Memory Allocated: 6GB
• Server/LAN/Single Player: Single Player and LAN
• Resourcepack Enabled?: Soartex Fanver - Modded
• Optifine Installed?: No

[ObeliskofDeath]

Found a temporary solution, friend went into MC edit and removed all tags from the helmet crab spawner that we believed was the issue. He then loaded up the saved world which was previously unable to launch without instantly crashing. The spawner had an agitator from pneumaticraft on it. Whether this is the cause of the issue or the spawner itself is the cause of the issue this is still something that should be looked into.

[Lomare]

I also have a crash loop after placing a pnuematicraft agitator on a blaze spawner in the overworld. Good thing I keep backups.

[ObeliskofDeath]

Interesting, I had figured all vanilla mobs were safe to agitate, good thing you said something. So far we have found that the helmet crab, NPC, and now blaze cause the crash. We have 6 spawners agitated consisting of zombies and depths ghouls that are not crashing us. Thanks for the heads up

[predakanga]

I encountered this as well with a Spawner Agitator on a Blaze Spawner in the Overworld.

The simple workaround for this is to disable the "displaySpawnerParticle" option for the "Despawning Spawners" mod.

Fun discovery, that mod stores spawn counts per-position, not spawner. So if you move a spawner, you reset it's amount of spawns. Conversely, if you place a new spawner in the same place as the old one, it'll break on the first spawn.

[Lomare]

I tested this on my broken save and confirmed, resolves the issue.

Thanks for the info.

[ObeliskofDeath]

Does disabling that option have any negative effects on the game? Do the agitators work as normal, just a particle effect goes away?

[predakanga]

There are no negative gameplay effects to disabling that option and the agitators work as expected, but I've yet to confirm whether "Despawning Spawners" works at all with agitated spawners.

The only purpose of that particular option is to show particles of different colours depending on how many spawns the spawner has left to give; green particles if >= 200, yellow particles if >= 40, red particles otherwise; it's purely informational.

[xanderhunter]

I cant seem to find the option when going through the configs of pneumaticraft anywhere, the 6 configs in it's folder and the main config file.

[predakanga]

It’s not an option for Pneumaticraft; it’s for the mod called “Despawning Spawners”. Accessible through the mod config GUI or by config file

On Wed, 18 Apr 2018 at 2:26 pm, xanderhunter notifications@github.com wrote:

I cant seem to find the option when going through the configs of pneumaticraft anywhere, the 6 configs in it's folder and the main config file.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Darkosto/SevTech-Ages/issues/1841#issuecomment-382256180, or mute the thread https://github.com/notifications/unsubscribe-auth/AAystYGqnlH52ALFYyGm9sQ40Y7evD1Wks5tpsCHgaJpZM4TVVIg .

-- Lachlan

[desht]

A bit more info (I'm one of the PneumaticCraft devs):

• Disabling particle effects in Despawning Spawners is the valid workaround for now. That's in the Despawning Spawners config, setting is B:displaySpawnerParticle
• The Spawner Agitator should work fine in conjunction with Despawning Spawners, apart from this particular problem; spawns caused by the Agitator will count toward the spawner total as far as Despawning Spawners is concerned.
• The crash appears to happen because of the particle effects, and the fact that the Spawner Agitator creates a fake player near the spawner (to fool it into thinking there's a player nearby). The fake player currently lacks a valid net connection, so Despawning Spawner's particle effects can't be sent to it - an exception is thrown. I say "appears to" because I haven't been able to reproduce the crash myself yet, but it's the only cause I can see, based the stacktraces I've looked at.
• This is fixed in PneumaticCraft dev builds, and I plan to do a release within the next 24 hours. Dev builds are available from http://jenkins.k-4u.nl/job/PneumaticCraft-Repressurized/ but if you're going to use such builds, don't bug the Sevtech pack developers about any problems you encounter!

[desht]

Update: PneumaticCraft: Repressurized v0.6.2 has now been released. It should fix this problem (I did some testing on a dedicated server with the two mods installed and couldn't get it to crash). Hopefully this will make it into 3.0.7.

[Rixxaw]

Thanks Desht..

[artdude543]

The update is in 3.0.7 so issue will vanish upon update 😄