Jump to content

Recommended Posts

Posted

Forge Version: 1.11-13.19.1.2189

Minecraft Version: 1.11

Downloads:

 

Here it is, our first Recomended Build for 1.11. There is still a lot to get done but most of the breaking changes are done.

We need modders and user feedback to find and fix all the holes/bugs.

A note to modders, and users about world migrations.

There WILL be world migration issues. With Vanilla changing how registries and assets work, forcing lowercase names, modders will need to adapt. Forge has hooks in place that modders can use to properly convert their old data to the new names such as the missing mappings event. However I expect that modder will need/want more help so I eagerly await people's input. And it is HIGHLY recomended that you BACKUP YOUR WORLDS.

 

Minecraft Forge 13.19.1 Changelog:

============================================================================

New:

  • Rewrite of quite a bit of the Fuild capabilities for ItemStack immutability
  • Added EnumHand parameter to Block.getStateForPlacement
  • Provided access to ShapedOreRecipe width and height
  • Performance improvements to IVertexConsumers
  • New hooks to allow better management of modded GUIs
  • New hooks for entity trampeling
  • New slot limit function in IItemHandlers
  • New hooks to allow modders to creat and manage their own DataFixers for help in migration
  • New Forge Loading Icon/Logo Yay new branding assets!
  • New EquipmentChangeEvent hooks
  • New hooks in armor materials
  • New hooks for 'connectable' blocks such as fences, and glass panes
  • Expanded the Biome Dictionary

 

Bug Fix:

  • Fixed AbstractMethodException in FML Registries
  • Fixed issue with modders sending custom packets to vanilla clients
  • Fixed custom packet payload size
  • Fixed ItemCraftedEvent returning AIR incorrectly
  • Fixed Hopper and Dropper item movement mechanics
  • Fixed problem with server not closing compleetly when client exits unexpectidly
  • Fixed world leak related to Redstone
  • Fixed sky color blending not working for render distances >16
  • Fixed issues with some modders custom Texture Sprites
  • Fixed issue reading chunk data when the server and client disagree on block count

 

Just wanted to reiterate this again, BACKUP your worlds!

  • Like 1

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • "I want to understand how complex mods with ASM transformation and coremods work, such as Xray or AntiXray. Why do they break when you simply rename packages? What features of their architecture make refactoring difficult? And what techniques are used to protect these mods? I am interested in technical aspects in order to better understand the bytecode and Forge loader system."
    • I can't figure out if you're looking for help trying to steal someone elses work, or cheat at the game....
    • Title: Why Is It So Hard to Rename and Restructure Mods Like Xray or AntiXray? 🤔 Post text: Hey everyone! I’ve been digging into Minecraft modding for a while and have one big question that I can’t figure out on my own. Maybe someone with more experience could help or give me some advice. Here’s the issue: When I take a “normal” Minecraft mod — for example, one that just adds some blocks or new items — I can easily change its structure, package names, or even rebrand it entirely. It’s straightforward. But as soon as I try this with cheat-type mods like XrayMod or AntiXray, everything falls apart. Even if I just rename the classes, refactor the packages, or hide its identity somehow, the mod either breaks or stops working properly. XrayMod in particular is proving to be a nightmare to modify without losing its core function. So my question is — why is this so much harder with cheat mods like Xray? Is there something fundamentally different about how they’re coded, loaded, or protected that prevents simple renaming or restructuring? And if so, how can I actually learn to understand someone else’s cheat mod enough to safely refactor it without breaking the core features? I’ve already been spending over two months trying to figure this out and haven’t gotten anywhere. It feels like there must be some trick or knowledge I’m missing. Would really appreciate any thoughts, tips, or references — maybe there are guides or techniques for understanding cheat-mod internals? Or if you’ve successfully “disguised” a cheat mod like Xray before, I’d love to hear how you did it. Thanks in advance for any help or discussion. ✌️
    • just started making cinamatic contect check it out on my channel or check out my facebook page    Humbug City Minecraft Youtube https://www.youtube.com/watch?v=v2N6OveKwno https://www.facebook.com/profile.php?id=61575866982337  
    • Where did you get the schematic? Source/Link? And do use an own modpack or a pre-configured from curseforge? If yes, which one On a later time, I can make some tests on my own - but I need the schematic and the modpack name
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.