wolfington

I'll try again one day this week when I can, I'll let you know if I find a solution, perhaps it might work for you too. Hopefully someone with Forge experience will chime in before then, these things always end up being way more painful than necessary.

Both. I started first with a basic item mod, then ran into the issue. Since I've tried reinstalling everything, switching to openjdk, changing to different versions of forge and the jdk etc etc. Aside from a few times I made a typo, and one time I had a dependency of 1.15 and was running forge 1.14 the same problem has occurred relentlessly. I can build the mod, I get as far as the minecraft menu, I can see the mods installed (forge, minecraft, examplemod) and then when I generated a world, it goes through 100% and as soon as its about to start rendering, while it says 'save' the thing crashes. Every time it's mouseclick event. The last thing I tried was a fresh install of 15.1 forge and I just did a gradlew build and a gradlew runClient on it with admin privileges, literally uninstalled avast, stopped my browser and other programmes, turned off the windows defender firewall, did a restart and all that business too mind you, and still the same issue.

I downloaded the mdk again and started over, this time I tried to get it running with just the example mod, but it still crashes at exactly the same spot. This is pretty tedious...

I still haven't been able to resolve the issue, if anyone is familiar with the problem please advise before I try to start from scratch.

Hello, I thought I'd try my hand at Minecraft modding so I downloaded Forge, Eclipse and the jdk (though after it became apparent that Forge does not support the latest jdk's I switched over to the openjdk with the 1.8 lts version. After reading the crash report and seeing the mouseclick event handler error, I looked into it, and apparently it is a known bug that can be caused by antivirus software, particularly avast. I happen to use Avast, so I uninstalled and tried again, but no luck. Next I tried turned off windows defender, but that still made no change. I'm not sure what to try next, I've looked over the code, and while I don't use (nor do I like) Java, it seems to be correct. Please advise. The program crashes consistently as soon as it renders out "save" to the screen and goes to start rendering the world. Gradle reports either 2 of 6 actionable tasks, or sometimes 3. I have tried giving it more memory but even 8194M isn't making a difference. There were a couple of yellow warnings in the output when runClient was running, seems to do with keymapping, and there was a red output, which said the config was changed, but neither of those seemed relevant. There was also mention of realms, but that too seems to be superfluous to the current issue at hand.