LexManos

Little known fact, the loading screen will log timing info for each bar as it completes. You could try grepping your log for thise lines tobsee what mod is being a hog.

hehehehe But yes, this has nothign to do with reflection its bytecode inspection. It's simple if you know what you're doing. But stupid complex if you're the average modder. Its WAY more complex then a normal system needs to be.

You say this like I don't know it. There should be no reason mods need to explicitly subclass ItemAxe, any item can be an axe, that class means nothing. Just subclass tool and do it yourself.

Modder error, not Forge.

Alright, I know this is complicated. It goes all the way back to elementary math class. But It's asking for version 1566, you have version 1558 installed. 1558 is LOWER then 1566

Yes those stairs are abusing a bug in vanillas culling system that forge fixes. Blocks need to be the basic shapes that vanilla blocks are. Solid sides need to be solid, simple as that.

Alright, seince you cant fucking seem to understand being polite and pointing you twards the correct procedure. Logs, or you get a ban. I HAVE verified that the Villager registry works just fine, all recipes work just fine. So SOMETHING on your end if screwed up. I can not magically guess what the hell is going on without atleast SOME form of debug logs. So once again, follow the damn rules and post your logs or I will ban you -.-

Forge has had block reach hooks for players for years.

That's great, but as your video shows you're playing vanilla not Forge. {HINT: You arn't showing any useful build info like the debug screen or a log file}

Show me a video of what exactly you're doing. There is no 'fix' as it's working just fine in Forge.

Just tested and everything is working fine, and as intended. However, as it sits i've added some safeguards to the villagers so that if a modder or user does something wonkey it will be sure to better sync data. Check the latest build. All 5 vanilla professions work just fine.

No it doesn't, You're using the wrong model for your blockstate. If you notice your 'corner' is in the wrong spot. The engine THINKS it is where it supposed to be so it culls some of the faces in the neighbors block. This is how the engine works, if you use a invalidly shaped model for any other block this will be the same result. Fix your model.

Ya fry derped up and killed the FML/Forge mod for the server. We've fixed it and it all should go correctly now. I've verified this myself with the latest build.

Update and let us know if it happens again with a new log.

1) Forge is the one who creates and controls all of those registries, not Minecraft 2) Downgrading vanilla worlds *might* work, but with their new world fixer system i'm honestly not sure. 3) That registry in question SHOULD exist unless you've derped something up that is causing the FML pre-init event to not fire... So what are you doing?

NOT ALL BLOCKS NEED ITEMS! The old method is a LONG standing hangover from back in the day when we had to make sure both were the same ID in the constructor. Now, they are completely separate registries with no real link between the two. If you want an item, then opt in for a item.

Don't make coremods, what you're doing and how you're doing it is extremely bad.

I've finished the MCP update for 1.9.1 and 1.9.2. Once bspkrs/Searge decide to release that we'll be updating to 1.9.2 for Forge. However, the changes are MINIMAL, seriously look: 1.9.0 -> 1.9.1 1.9.1 -> 1.9.2 90% of the 'changes' are just constants being inlined by the compiler.

Actually no, his 'non-srg' detector is just dumb. There are a lot of 'Non-srg' methods in Forge's code base.

Reika seems to be doing something stupid, coremod and other crap. Our advise is to remove DragonAPI.

Magically, No. However we DO have mechanics in place for Mods to tell us what versions of MC they are compatible with and we skip over the ones that we know are not compatible. So yes, thanks for the blatantly obvious suggestion on something we already do. If a mod loads for the incorrect MC version that's the mods fault for explicitly going out of their way to REMOVE that information we encode in them for this purpose.

No we are not rewiring the world save format/networking/every 3rd party map editing/viewing software. Seriously You think we haven't said to ourselves "Wow it would be nice if we had these blatantly obviously restrictions lifted" We have. It's not gunna happen there are to many downsides.

That's not how rendering works we cant just wave a wand and say 'here you go GPU is now doing it!' 1.8/1.9 do LARGE strides to move the rendering away from the CPU, but that's the #1 thing modders are bitching about because it means they have to adapt. As it sits, we are not in the market of rewriting extensively large swafts of Minecraft. So no.If Mojang continues to change to better rendering we will encourage and make it easier on modders to move, but we don't dictate something this fundemental.

Auto mod downloading like this will not be supported or endorsed on this forums. There are fsr to many security issues to even contemplate this.

That the install log, and its a successful install... so.. give us the launcher log please.