heres the crash log
http://paste.fedoraproject.org/199562/42669190

Have the same crash, here is my crashlog: http://pastebin.com/9eDvf5WR

Seems that some recipe stuff somehow is referencing client side stuff.

looking at the code in WasherRecipe its not immediately apparent to me HOW its referencing client stuff.

stacktrace references these lines: (in the caused by section)

public FluidInput waterInput = new FluidInput(new FluidStack(FluidRegistry.WATER, TileEntityChemicalWasher.WATER_USAGE));

this(new GasInput(input), new GasOutput(output));

Perhaps it interacts with the chemical washer class somehow causing the server to attempt loading the client side sound stuff?

New tile sound implementation is a bit rough with its client references, I'm trying a fix but it's acting weird. I'll push a fix as soon as I figure it out.

src/main/java/mekanism/common/tile/TileEntityNoisyElectricBlock.java has the import for mekanism.client.sound.IResettableSound; which is likely involved in this.

Yes. The import won't necessarily matter though unless it is referenced...

looks like line 22 might be the culprit.

In the entityNoisyelectric class i mean

the sound member variable has type IResettableSound which extends import net.minecraft.client.audio.ITickableSound;

Fixed

Yeah, it seems to happen the INSTANT TileEntityChemicalWasher is loaded.

is the code in an uncommittable state atm? I notice there is no new commit, so as of yet , can't test for further bugs.

There we go, forgot to push ^^

odd... now i'm getting a buildcraft related crash that I wasn't getting before.

no, without mekanism it launched without a crash.

@unpairedbracket, just revert and add your change - my fix was definitely messy :P

Does that happen without Mekanism installed? Also, @aidancbrady, I figured out a solution to the server-side sound issues that works and seems to avoid the issues you were encoutering, and doesn't require the usage of a wrapper class. Shall I revert it before I pull, or go with my solution in a merge?

I put the crash report and the other message into a new issue, since i'm not certain it has anything at all to do with the sound problem.