With the latest (1.0.4) version I get an odd hang during start-up. The hang occurs during the process labelled "[Forge] Sending event FMLLoadCompleteEvent to mod Forge"

Forge log with HarvestCraftWaila-mc1.6.4-1.0.4
Forge log with HarvestCraftWaila-mc1.6.4-1.0.3

As you can see (using a search) the "Unknown recipe class!" warnings at the end of the 1.0.4 log also exist in the 1.0.3 log, but the game halts loading at that point and no matter how long I leave it the game will not load any further. The 1.0.3 log contains a "SEVERE" error, a few lines after the 1.0.4 log halts, but continues to load anyway.

Yeah, exactly. Removing this and only this mod fixes the hang, replacing it with the old version works too. Like I said, it's odd. It cause a hang in a place I simply wouldn't expect it to and, based on the changelog, you haven't made any major changes.

If you can think of anything I can do to get more information about it I can do that.

At some point when I feel like I have the time I can try to determine if this is playing up with any of the other mods I have installed, but as there are 170+ of them that might take some time...

Try this version: HarvestCraftWaila-mc1.6.4-1.0.4-test.jar

It might spam your log, but if it does that'll narrow the cause down a lot, so post your log after trying to run with the test version installed.

Not sure how this mod could cause that and the update didn't really change anything about how the mod works.

You no longer get the hangup if you simply remove this mod and change nothing else?

Hmm, I couldn't find anything that the original 1.0.4 didn't have (just the regular forge loading messages and one saying the logging level was set to default). Are there configuration files I should be removing/changing?

Here's the log you can take a look at in case I missed something: http://filebin.net/mmjlmmei2h/ForgeModLoader-client-0.log

Weird. Try this version: HarvestCraftWaila-mc1.6.4-1.0.4-test2.jar.

Note that this test version removes the icon fixing part of the mod to see if that's the cause.

Any update on this @StarkRG?