LexManos

Yes, its because when you say extract it's asking for a directory. Why would we show you files when we're asking for a directory? Why are you clicking the extract button on the forge installer? You don't need that.

They either need to update the mod {it's just a recompile} or you need to downgrade Forge. I'd advise you tell them and have them update.

That's the spawn fuzz, which is a randomized position around the actual spawn point. This is a vanilla mechanic not Forge.

https://github.com/MinecraftForge/MinecraftForge/tree/1.9/src/main/java/net/minecraftforge/items

Isn't this so much cleaner... and it does the EXACT same thing as your code.... You really need to go and learn some basic code style/java instead of copy pasting tutorials.

Be More Descriptive!

OR, get this, You could NOT create a NEW instance of your Teleporter every time, and instead use a single instance that you manage for the world. Maybe... Naw that would make to much sense...

The lookup is the most expensive part... sortof. The invocation is still ~60x slower then normal invocation. Constant usage of reflection is noticeable. People don't think it is because SOME JVMs SOMETIMES optimize the reflection classes that are used often by compiling them into native classes. The problem through extensive research that I've done i've found that this JVM optimization is not reliable, only about 15% of end users JVMs do this at all. And of those 15% only about 1/2 do it aggressively enough to be useful in MC world. And even when they do JIT it the resulting class still goes though a bulk of reflection redirection which make it at most 1/12th the speed of native code in my tests.

Again this is something that nobody has actually bothered to actually look into. But what is the POINT of extending the ItemAxe? Forge already has hooks in place to define what type of tool the item is, no matter what class it is. So why do you need to extend this specific class. I have yet to hear a SINGLE argument besides 'My 1.8 code errors in 1.9!!!!!!' I'm not against adding a bypass constructor. But I need someone to articulate WHY beyond just bitching.

Ohgodno. Reflection is awful. 60 to 80 tiles slower then normal invocation. Thats why our event bus is a BEAST. Its specifically designed to be the least overhead as possible.

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?