Have you tried opening or closing a door and then logging out and logging back in, to see if it was synced up?
It sounds to me like the mod or server/clients aren't syncing properly.
You have 2 different declared types in that field.
I recommend reading this if you don't understand.
But using Github is way better as you can also access it out of your local network too and it is less complicated than doing it on a network drive and you can sync your changes between your devices easily using the pull feature. If you don’t want others to see your code you can create a private repository making it accessible only to you and the people you want to be accessible.
I think they're more concerned about working on their project on the main computer, then moving onto their other computer, without the extra steps of having to commit, push and pull.
Use a symbolic link in the network folder for the gradle files and source code (build.gradle, src, gradlew, gradle), excluding the build and .gradle folders.
Then on your other computer, create a symbolic link from those files, then setup the workspace.
The changes you make should sync between the two, aside from the main issue of remaking the dev workspace every time you decide to change the gradle build file.
getPos()doesn't exist in 1.7.10
Use xCoord, yCoord and zCoord.
Locked due to necro posting and update spam
Registration happened during the Initialization event, while recipes were also being registered during the Initialization event.
Basically a "race condition", since block registration happened before or after recipes were registered.
tl;dr Recipes were using a null block/item since it didn't exist before.
Assuming Forge hasn't changed much since 1.7.10, you should be able to use "events".
The documents Forge gives isn't much compared to the code they do give.
You don't really need the get and set methods unless the fields are private, but that works too.
Read up on access modifiers and why you may or may not need them: https://www.javatpoint.com/access-modifiers
That's your issue. You're not using that registered object in a crafting recipe, so Minecraft doesn't know what it is or what to do with it.
You already have the fields set up, so it's not that difficult to change.
Refer to that Stackoverflow link.
You're not using the registered item in the crafting recipe.
Use the item object that is registered using
GameRegistry.registerItem. And no. That does not mean to re-register the item again using that method.