not a patch, but IThrowableEntity and its supporting code should go. It looks like extremely old compat code, and nothing uses it.
Additionally, I also think the old BrewingRecipeRegistry (and its patches to vanilla) can go as well. Looking at the interfaces provided in IBrewingRecipe, it's superseded completely by the vanilla systems in PotionHelper, since now we have flexible Ingredients that can be extended for arbitrary matching behaviour
I think it would be a good idea to remove all the patches from TileEntityItemStackRenderer and move to a forge-owned item renderer class, preferably with more context.
Block.addLandingEffects has a duplicate IBlockState parameter, this would be good to fix for the major version update: EntityLivingBase.java.patch#L28
Hi all! I'm a dev working with an academic research team that uses Forge for modding. Soon I'll have the time and energy that I could contribute back to Forge; our work would benefit by having 1.13 support so I'd be down to help with that. Is this issue the basic roadmap for the upgrade?
The current work is extremely specialized, and mostly being done by Lex and cpw.
We will be more open to contributions once the patches have been ported and things have stabilized a little bit. Until then there is not really a way to help out.
This issue is difficult to maintain so I am not sure it reflects the current progress, you can directly see the state of patch porting progress here (updated yesterday): https://github.com/MinecraftForge/MinecraftForge/commit/b687180e12f6b8292b406e26447c6fcfd9bd7317
@mezz @LexManos @cpw
Once things are a little closer (i.e. patches ported and things stabilized as you mentioned), will there be any kind of "here's how you can help" document or issue? I'm an experienced Java developer, but something as big as Forge is so daunting that it's hard to know where to start. For as much as I have gotten from Forge and the modding community, I'd love to help out in whatever ways I can.
Keep up the good work, and thanks for everything you've done so far!
The project is too big to jump in at random, so I am starting to look for things to fix in Forge by trying to port mods. I quickly ran into things that are missing or not working. When things are more stable next month, more modders will be trying to port their mods and reporting issues in the tracker here, and there should be plenty to take a look at!
Now that this is closed, what does that mean for the 1.13 release? Any way I or the rest of my research team can help out?
It means the main patchwork has been done, forge is now currently in a stage of bugfixing and feature addition in the form of PR's. Any issues that can be reproduced with just forge should be reported to the tracker with either an accompanying PR or reproruction steps so someone else can make a PR.
Forge for 1.13.2 is released as a beta. Any further patches are on the backburner or not necessary. This part of the port is complete. As for what needs to be done, there are lots of open issues tagged "1.13" that need to be fixed, and lots of other things yet to be discovered I'm sure. Discord is a great place to communicate about what needs doing.
Most helpful comment
The project is too big to jump in at random, so I am starting to look for things to fix in Forge by trying to port mods. I quickly ran into things that are missing or not working. When things are more stable next month, more modders will be trying to port their mods and reporting issues in the tracker here, and there should be plenty to take a look at!