Jump to content

Recommended Posts

Posted

I've successfully created and tested a mod with Gradle, but when it comes time to deploy I'm coming up stupid here.

 

Everything I've read has vaguely referenced editing build.gradle... I've done that (http://pastebin.com/N5WcAx8m), and ran gradlew build.

 

The problem I'm having is that the contents of bin are still accessing unobfuscated objects in Minecraft.

 

I found a folder build\tmp\reobf that has jars named reobfed###########.jar, but those too are unobfuscated.

 

What am I missing here?

Posted

Thanks GotoLink, unfortunately I seem to be having the same problem with the jars found there. Namely, the bytecode in one of those jars runs:

 

ldc <Class net.minecraft.block.Block>

 

To spin up a new Block instance... which of course throws a ClassNotFound exception, and kills the minecraft. Pretty sure this should be along the lines of:

 

ldc <Class ahu>

 

Now, in /build/libs I have:

 

PaneInTheGlass-1.0.jar

PaneInTheGlass-deobf-1.0.jar

PaneInTheGlass-javadoc-1.0.jar

PaneInTheGlass-src-1.0.jar

 

I am assuming PaneInTheGlass-1.0.jar is the one I want to use.

 

(For those curious, I'm grabbing the type of the Block class to see if I should use obfuscated names in my transform class. If I bypass this check and force my obfuscation flag to true, my mod still blows up later when my mod code tries to test against Block.air... I get a field not found exception. Therefore I can only conclude that my mod isn't being reobfuscated.)

 

I feel like I'm missing a concept here.

Edit: Added logs: http://pastebin.com/vgUWQpJG

Posted
  On 3/3/2014 at 4:58 PM, diesieben07 said:

ForgeGradle obfuscates to SRG names (which are func_*** / field_***). Also it doesn't change class names. Why? FML deobfuscates at runtime. That means: even though the minecraft jar contains classes like

bhv

or whatever they are transformed on the fly while being loaded to something like

net.minecraft.entity.Entity

. The method and field names are changed as well. That helps to preserve compatibility between minor versions (mods for Minecraft 1.6.2 still run on 1.6.4).

 

Oh, so my class transformer is getting in before this. I'm trying to be too clever with my obfuscation detector.

 

Mod is working now. Thanks!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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

×
×
  • Create New...

Important Information

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