Leaderboard

Since this is such a big update for forge, is there a way to keep more in the loop of updates of how far the team will be till done? Or any ways people can help, other than to not ask for 'when will it be done' threads? And I am not asking when it is is done, just how to be kept in the loop of how far you guys have been able to be with it.

First, I want to thank every modder on here for your time developing mods for kids around the world to enjoy, including my 7 year old. After over a year playing and watching Minecraft, my child asked me if he can learn how to create mods and hack games. I'm studying how to code while teaching him at the same time. He wrote his first "Hello, World" program the other day. Now, I need to get up to speed with Forge's API before we get started on basic in-game mods and automation. We're excited, but it's going to be a steep learning curve! So, how's the modding community on Minecraft as of late? I know some of the mods for 1.7.10 aren't updated anymore which is a bummer. I hope the both of us will learn enough to bring some old mods back to life for the latest version of Minecraft. Again, thanks for the great mods.

Is this being properly overriden? and how are you registering your block?? Can you post your entire log using GitHub Gist or pastebin and your code as a github(or similar) repository?

Look into Forge's Access Transformers, I don't think we have an official docs page on them at this time, but this is the tutorial I followed.

You would be able to work on it, I think so, yes, not exactly needed but likely appreciated & you will get a feel for how Forge works by working on it

You would need to use ore dict there was a post recently on how to do any type of planks it should function the same as the answer on there.

The oak log isnt called minecraft:oak_log yet, that is its name in 1.13. In 1.12 you need to use its metadata value via the data tag in the JSON.

Thats the one! I couldn't find the link

https://github.com/ichttt/MCLang2Json

What I said about only taking 10 mins was refactoring your @Mod annotation I’ll break down the times (that I think it would take, from my Modding experience): Refactoring @Mod annotation to META.INF file: 5-10 minutes (5 mins for basic mods, 10 mins for mods with dependencies) Rewriting .lang to .json: 5 mins (10 mins if you do it all by hand, 2 mins if you use a tool to do it, 15 secs if your already prepared for it) Flattening & removing getStateFromMeta & getMetaFromState: about 10 mins per block (5min for simple blocks with variants stored in meta, 10 mins for blocks with multiple types & variants stored in meta, already done ✅ if you prepared for it) Changing OreDictionary to the Tag System: about 2 minutes per OreDictionary entry Updating texture references (“/blocks/“ to “/block/“): 5 mins (15 seconds for a well written mod, 5min for a badly written one, 15min for a horribly written one) Updating model variants (“normal” to “”): 10 mins (15sec for a well written mod, 10 for a badly written one, 15 for a horribly written one) Moving data from /assets/ to /data/: 1min Rewriting mod functionality: between 0 and infinite minutes, it depends 100% on what the mod did - some devs may not have to do anything, some may have so much work that they give up and never work on the mod again. Some mods may also not be necessary anymore. I’ve prepared for 1.13 in my mod, and it should take me less that half an hour to fully update it for 1.12.2 to 1.13, every other Modder should be (and most are) preparing the same way. ALL THESE NUMBERS ARE ESTIMATES BASED ON EXPERIENCE AND VERY FEW ACTUAL FACTS! As Lex said

Need some fish skewer? fish_cod_cooked.pdn Sorry for spamming the site, anyways. I'll try at some new ones. Here is some new ones _Cruelar_! If you want to edit them, do whatever you need. The bananas were hard so I hope they look ok for a start. You can remove the bold, black edges to add something more blending if that's better. Thanks for letting me help out on this mod. Will I get any credit or no?

I think that the actual code of mods will remain pretty much the same (except for removing getStateFromMeta & getMetaFromState). The mod loading system has changed massively though & the only thing you put in your @Mod annotation is your ModID, with everything else being put in a META.INF file. However all this should take under 10 mins. Theres also the conversion from .lang to .json

80-90% over the course of roughly 2 ½ months so maybe 1-2 more weeks until completion then maybe hopefully. Hopefully 1.13 isn't a drastic change in terms of converting mods to be compatible.

You can view the entirety of Forge 1.13 here: https://github.com/MinecraftForge/MinecraftForge/tree/1.13-pre?files=1 I think that Forge 1.13 is 80-90% done based on: - Forge Gradle 3 is finished (this was the part that unexpectedly took the longest) - I believe the MCP mappings are pretty much done for 1.13 - From what I’ve seen on the comits they’ve managed to get Forge 1.13 (without all the patches) to compile and run (I’m traveling right now so I can’t test it and confirm it myself) - I judge that the rewriting of the mod loading system is probably more than half done as they’ve already merged Minecraft and MCP into 1 “mod” with the new loading system (I think the new loading system is amazing and is a massive upgrade from the previous system) - I think that the remaining 10-20% of work is going to be going through all the patches from 1.12.x and seeing if they still need to exist and if so what changes have to be made to them because of changes to the vanilla code. Here’s the list of patches to review https://github.com/MinecraftForge/MinecraftForge/issues/5162

I agree! A percentage of completion shown on the main download page would be great! Or just something to show people how far development is. If there's anything I've learnt in my career, it's that people don't like to be kept out of the loop or uninformed about something they invest a lot of time into. People like to see progress. This would be beneficial to people so they can clearly see progress, and it would be beneficial to the devs because it would lift a weight off of their shoulders by not having to deal with people constantly asking about progress or if it's done yet.

That is also 1.7.10, which is no longer supported because it is ANCIENT. Please update to receive support.