Keitaro

That's exactly what i did.? But i only use HORIZONTAL_FACING and was not sure what you would use, if you want to include the posibiity you let your block face up and down. It's somewhere in my commit history, but was to lazy to look it up. I had that before but changed it horizontal only, since it looked somewhat strange to have da machine lay on it's back instead of standing upright.

I just use @Nullable @Override public BlockState getStateForPlacement(BlockItemUseContext context) { return this.getDefaultState().with(FACING, context.getPlacementHorizontalFacing().getOpposite()); } But that's only for Horizontal, without UP and DOWN. If i am not mistaken your code set's the FACING to the Direction you are looking at, so you could just add the .getOpposite() to it. I think context.getFace() get's the Face your are placing against, but I am not sure. So context.getFace().getOpposite() should face it in your Direction.

You can use the PlayerModel from Minecraft and even the BipedRenderer, but your are limited in what you can do with that. I did just test it, you can use RenderingRegistry.registerEntityRenderingHandler(FarmerEntity.class, (EntityRendererManager rendererManager) -> new BipedRenderer<>(rendererManager, new PlayerModel(modelSize, smallArms), shadowSize)); to register the BipedRenderer with the PlayerModel to your Entity.

It usually means your signature doesn't match with the function you are overriding. As a result your function doesn't get called at all. Also i think your return value should be FAILED or SUCCESS. I am not sure at the moment, look at what the parents function does.

Developing a mod an mac is just the same as on windows or linux. Just install java 8, your favorite ide, download the forge mdk and open it as a project inside your ide. On how to write a mod, there is plenty of stuff for 1.12 available. For example the forge documentation and multiple online tutorials.

You recipe has no output, the result is empty.

I don't think it's high on the list, since the vanilla way works just fine. The 100 item models you will need either way. Since the changes should be fairly similar in all your files, you could look into regular expressions and a way to automate the conversion.

Since forge for 1.13 is still being developed and hasn't had a stable release yet, there is not really any documentation. I think 1 or 2 things have been updated at https://mcforge.readthedocs.io/en/1.13.x/ other than that your are stuck with looking at the mkd, finished 1.13 mods and the forge and mineraft sources itself to figure out how stuff is done. In your case look how vanilla displays these information and work from there.

IIRC the relevant stuff is in the net.minecraft.stats package.

You could save the current value if the player joins the game and at any given time calculate how far he walked since, with the new current value.

Blocks moved? Like how many blocks you pushed with a pisten? Or like how many blocks you walked? The later is in the player stats.

In 1.13 you can change the loottables with data packs. Just add the json loottable for whatever you want to change inside your data folder. Like data/minecraft/loot_tables/entities/pig.json for example.

Your log should tell you more about why it isn't loading the blockstate json. I just used vanilla format without the forge_marker, so i can't comment on that one. (Might have heard somewhere it's not implemented yet,but don't quote me on that.) As for changes, one change is that the "normal" variant is now just an empty string "". And the blocks and items folders now should be named block and item. If you use your block as an item as well you will need an json model for it, also you normally just use your block model as a parent and that's it. For an example just look at the vanilla files.

What version of java are you using? I know there can be problems if you use anything above 8, but not sure if that's related.

I don't you eclipse, but looks like a problem with your mappings or workspace setup in general. Try running the eclipse task again, or genEclipseRuns. That should update your mappings if something is missing. Also for me sometimes it helps to just close an open the project again.