Blocky McSquare

Thanks for the response. Problem solved. Apparently the big red banner on the home page was too subtle for me.

First, thanks for Forge. I've enjoyed for a couple of years now. While this may not be your issue, I'm hoping you may be able to point me in the right direction. I've been playing the DW20 pack (version 1.3.2) on the curse client (Forge version 12.18.3.2185), with WAILA (version Waila-1.7.0-B3_1.9.4). Until today, everything was good. Today I started receiving a pop up that Java has stopped working. This is occurring during the mod loading process, always during Waila post-initialization. If I disable Waila, the pack loads fine. I updated to Java 8 update 121 between the last time I played successfully with Waila enabled and the issue beginning to occur. I've tried removing and reinstalling Java, rolling back to an older version of Java, and removing and reinstalling the curse client. I created a new mod pack in the curse client, with only Waila (Waila-1.7.0-B3_1.9.4) and Forge (12.18.3.2221). The result is the same, Java stops working during Waila post-initialization. I tried a few different Forge versions, but no change. I've attached all the log files for the test pack I made. I'm assuming it's related to some interaction with Waila, and something I did (or the Java update did), but have no idea where to start looking beyond what I have already done. Any information or suggestions are welcome. fml-client-latest.log Thanks