cpw

Don't ask awkward questions. Mojang code is PERFECT, and NEVER NEEDS FIXING.

Some observations: If Mojang had content to go along with this, it would almost definitely have received the 1.20 version number, in olden days. This may be the beginning of a new paradigm: all future dot releases (1.20.1,1.20.2 etc) will likely be major breaking changes, with the only viable "long term" version becoming the .0 version - where all the previous version's in-development features "go live". This is seriously screwed up by Mojang.

Yeah, your numbers don't make any sense at all.. 1393 has the progress bar in it. If it was related, I would expect to see that as slow as any of the others. Are you using optifine? He "sorta" supports these versions of forge..

We know. The trade off was this, vs total server lockdown. Mods add a lot of extra mobs, that inherit this behaviour (as you noticed). Once that count gets too high, the server will start to lag, HARD. Too many mods circumvent the spawn limits (though it was quite reproducible in vanilla too). Multithreaded mob AI in 1.8 may mean this patch can be removed. Don't get your hopes up before then.

Overmind, with the timings in his initial log, he's lucky he can even play vanilla. It must be an excruciating experience. Even my 10 year old laptop does better than this.

Your computer is too slow to run both a modded server and client. Get newer hardware!

You need to obfuscate your mod to run it outside eclipse. You can't just collect the classes from the eclipse bin folder. Run "gradlew reobf" to generate an obfuscated jar at build/libs

I am working on aliasing. It will be possible to force the "minecraft:milk" name to point at a different block/item, as an example. The original block/item won't be replaced, so much as any requests for it will become diverted. This is not in FML yet.

Reproduce with the very latest forge, and grab the "latest.log" from the logs dir. it may contain clues.

yup

What is the version of Java, the version of Windows, and how much memory do you have?

Close your old launcher processes. Those logs are because there's an old launcher running, locking the log file, so it can't be rotated.

What is your java version? Do you know? It seems to be pretty broken.

Test with latest forge/fml please. It should be working. there was a bug that derped runtime deobf for a bit.

Impossible to fix it. He does a direct replacement of a class that is incompatible with FML in every way. It was coincidental that it worked before. (In this case: the class in question is TileEntityMobSpawner).