Jump to content

Recommended Posts

Posted

Hi! I have some troubles with my gradle. I installed shadow into it, and tried shading the netty package by doing:
 

dependencies {
    compile group: 'io.netty', name: 'netty-all', version: '4.1.29.Final'

}

shadowJar{
    configurations = [project.configurations.compile]
    relocate 'io.netty', 'com.hofill.netty'
}

 

 

This is the only shadow related thing I have in my build.gradle.

After I did this, I reimported the gradle packages, and then went in my code to do :

 

new com.hofill.netty.handler.proxy.Socks5ProxyHandler()

 

Which resulted in the program telling me:

  • package com.hofill.netty.handler.proxy does not exist

 

What did I do wrong? I tried the srgExtra() but that didn't work out for me either. Could you guys please help me? Thanks a ton

Posted (edited)

I want 4.1.29 because it has better DNS redirects, how can I make it work? (not the DNS redirects, the netty shading)

Edited by Chormi
clarify
Posted

so what stepts do I have to take to make it work? I tried building it from the terminal but that didn't work either. The code is done.

Posted

Can I just git clone from github and just rename the packages? Or what do you mean by create my own version of the netty library?

Posted

Yep, truth is I still do need it for 1.8.9, but I don't see why I couldn't ask about it since it isn't really about the version (I don't want to get my thread locked). The netty version in 1.8.9 doesn't support Socks5ProxyHandler or Socks4ProxyHandler, and I have a mod for 1.12 that does that uses these functions (seeing as how in 1.12.1 the minecraft netty version does support it). I want to port the 1.12.1 mod to 1.8.9. That's the reason i'm doing this. (sorry for lying first of all lol)

Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Back then there was a number which determined the tier of an item and block. If the block tier is lower or equal to the item number, the block would be mined. this however, has changed and now it goes by "needs_netherite_tool" which is fine, until you realized that some mods had items and blocks that exceeded these values. You can make you own "needs_mod_tool" but I feel that this is more limiting(and just more work) than before. So is there anyway to use something similar to the old tier system while also still being compatible with a lot of other mod tools?
    • Well, when I log in to the server, sometimes within an hour, sometimes within a minute, the server closes and informs me that there was a Ticking entity error. Below is the crash report
    • This forum is for Forge, not NeoForge. Please go to them for support.
    • Forge version: 55.0.0 Minecraft version: 1.21.5 Downloads: As this is the start of a new version, it is recommended that you check the downloads page and use the latest version to receive any bug fixes. Downloads page Intro: Good evening! Today, we have released our initial build of Forge 55.0 for Minecraft 1.21.5. 1.21.5 is the newest member of the 1.21 family of versions, which was released yesterday on March 25, 2025. As a reminder, the first minor (X.0) of a Forge version is a beta. Forge betas are marked as such on the bottom left of the title screen and are candidates for any breaking changes. Additionally, there are a couple of important things to note about this update, which I've made sure to mention in this post as well. Feel free to chat with us about bugs or these implementation changes on GitHub and in our Discord server. As always, we will continue to keep all versions of 1.21 and 1.20 in active support as covered by our tiered support policy. Cheers, happy modding, and good luck porting! Rendering Refactor For those who tuned in to Minecraft Live on March 22, 2025, you may already know that Mojang have announced their intention to bring their new Vibrant Visuals overhaul to Java in the future. They've taken the first steps toward this by refactoring how rendering pipelines and render types are handled internally. This has, in turn, made many of Forge's rendering APIs that have existed for years obsolete, as they (for the most part) can be done directly in vanilla. If there was a rendering API that was provided by Forge which you believe should be re-implemented, we're happy to discuss on GitHub through an issue or a pull request. Deprecation of weapon-like ToolActions In 1.21.5, Minecraft added new data components for defining the characteristics of weapons in data. This includes attack speed, block tags which define efficient blocks, and more. As such, we will begin marking our ToolActions solution for this as deprecated. ToolActions were originally added to address the problem of creating modded tools that needed to perform the same actions as vanilla tools. There are still a few tool actions that will continue to be used, such as the shears tool action for example. There are some existing Forge tool actions that are currently obsolete and have no effect given the way the new data components are implemented. We will continue to work on these deprecations and invite you to chat with us on GitHub or Discord if you have any questions.
  • Topics

×
×
  • Create New...

Important Information

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