Jump to content

Modifying Jar Classes


BlueSpud

Recommended Posts

I want to modify some of the functions in the jar, but I know installing modified class files is a haste. I thought ASM transformers were what I needed, but I haven't had any luck. If someone could point me in the right direction, that would be greatly appreciated. Thanks.

Link to comment
Share on other sites

EDIT: I was able to make the coremod load by adding a command line load in Eclipse, but I still don't know how I would override functions, so I can change them completely.

 

 

I do need base edits, I'm modifying several functions that Forge can't change. My problem is that the coremod won't load. I'm in eclipse, and here is all my code:

 

Transformer

package DHNCore.asm;
import java.io.IOException;
import java.lang.reflect.Method;
import java.util.Iterator;
import java.util.LinkedList;
import java.util.List;

import cpw.mods.fml.common.asm.transformers.AccessTransformer;
import cpw.mods.fml.relauncher.IFMLLoadingPlugin.TransformerExclusions;


public class DHNAccessTransformer extends AccessTransformer {
  private static DHNAccessTransformer instance;
      private static List mapFiles = new LinkedList();
      public DHNAccessTransformer() throws IOException {
              super();
              instance = this;
              // add your access transformers here!
              mapFiles.add("DHN_at.cfg");
              Iterator it = mapFiles.iterator();
              while (it.hasNext()) {
                      String file = (String)it.next();
                      this.readMapFile(file);
              }
              
      }
      public static void addTransformerMap(String mapFileName) {
              if (instance == null) {
                      mapFiles.add(mapFileName);
              }
              else {
                      instance.readMapFile(mapFileName);
              }
      }
      private void readMapFile(String name) {
              System.out.println("Adding transformer map: " + name);
              try {
                      // get a method from AccessTransformer
                      Method e = AccessTransformer.class.getDeclaredMethod("readMapFile", new Class[]{String.class});
                      e.setAccessible(true);
                      // run it with the file given.
                      e.invoke(this, new Object[]{name});
                      
              }
              catch (Exception ex) {
                      throw new RuntimeException(ex);
              }
      }
      
}

Loader

package DHNCore.asm;

import java.util.Map;

import cpw.mods.fml.relauncher.IFMLLoadingPlugin;
import cpw.mods.fml.relauncher.IFMLLoadingPlugin.TransformerExclusions;

@TransformerExclusions({"DHNCore.asm"})
public class DHNLoadingPlugin implements IFMLLoadingPlugin {

@Override
public String[] getLibraryRequestClass() {
	// TODO Auto-generated method stub
	return null;
}

@Override
public String[] getASMTransformerClass() {
	// TODO Auto-generated method stub
	return new String[] {"DHNCore.asm.DHNAccessTransformer"};
}

@Override
public String getModContainerClass() {
	// TODO Auto-generated method stub
	return "DHNCore.asm.DHNModContainer";
}

@Override
public String getSetupClass() {
	// TODO Auto-generated method stub
	return null;
}

@Override
public void injectData(Map<String, Object> data) {
	// TODO Auto-generated method stub

}

}

Mod Container

package DHNCore.asm;

import cpw.mods.fml.common.DummyModContainer;


import java.util.Arrays;
import java.util.Random;


import com.google.common.eventbus.EventBus;
import com.google.common.eventbus.Subscribe;

import cpw.mods.fml.common.DummyModContainer;
import cpw.mods.fml.common.LoadController;
import cpw.mods.fml.common.ModMetadata;
import cpw.mods.fml.common.event.FMLServerStartingEvent;

public class DHNModContainer extends DummyModContainer {
        public DHNModContainer() {
                super(new ModMetadata());
                /* ModMetadata is the same as mcmod.info */
                ModMetadata myMeta = super.getMetadata();
                myMeta.authorList = Arrays.asList(new String[] { "BlueSpud" });
                myMeta.description = "Dishonored Core Mod";
                myMeta.modId = "DHNCORE";
                myMeta.version = "1.6.1";
                myMeta.name = "Dishonored Core";
                myMeta.url = "";
        }
        
        public boolean registerBus(EventBus bus, LoadController controller) {
        bus.register(this);
        return true;
        }
        /* 
         * Use this in place of @Init, @Preinit, @Postinit in the file.
         */
        @Subscribe                 /* Remember to use the right event! */
        public void onServerStarting(FMLServerStartingEvent ev) {
                ev.getServer().worldServerForDimension(0).spawnHostileMobs = false;
                System.out.printf("DHNCore has Loaded%n");
        }
        
}

for the config I just copied the tutorial on the wiki

 

# Tutorial Access Transformers.
########### THESE ARE DIFFERENT IN 1.4 ################
# Lines starting with a '#' are comments and aren't needed, although it's a good idea to label them so you know what changes what.

# World
# So to make a field public, put something like this:
public abr.E # spawnHostileMobs
# In 1.4, the above line would be "public xe.F"

Manifest

Manifest-Version: 1.0
FMLCorePlugin: DHNCORE.asm.DHNLoadingPlugin

Link to comment
Share on other sites

1) ASM should ALWAYS be a last resort, so what are you trying to do?

2) Your transformer is a lot more cplicated then it needs to be...

This is Forge's

public class ForgeAccessTransformer extends AccessTransformer
{
    public ForgeAccessTransformer() throws IOException
    {
        super("forge_at.cfg");
    }
}

And for as to why your coremod isnt loading, you need to pass in the proper environment parameters. fml.coreMods.load

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

Link to comment
Share on other sites

1) ASM should ALWAYS be a last resort, so what are you trying to do?

2) Your transformer is a lot more cplicated then it needs to be...

This is Forge's

public class ForgeAccessTransformer extends AccessTransformer
{
    public ForgeAccessTransformer() throws IOException
    {
        super("forge_at.cfg");
    }
}

And for as to why your coremod isnt loading, you need to pass in the proper environment parameters. fml.coreMods.load

 

After looking around more, I found I needed to add the environment parameters. I also found a tutorial, but I'm having trouble replacing the instructions. Here is the link: http://www.minecraftforum.net/topic/1854988-tutorial-152161-changing-vanilla-without-editing-base-classes-coremods-and-events-very-advanced/ If you could help, that would still be great. (PS I downloaded the bytecode addon for eclipse, but after a bit of trying, I haven't' had any luck :( )

I also changed my code from above, and here it is:

package DHNCore.asm;

import static org.objectweb.asm.Opcodes.FDIV;

import java.io.IOException;
import java.util.Iterator;

import org.objectweb.asm.ClassReader;
import org.objectweb.asm.ClassWriter;
import org.objectweb.asm.tree.AbstractInsnNode;
import org.objectweb.asm.tree.ClassNode;
import org.objectweb.asm.tree.MethodNode;
import org.omg.CORBA.portable.InputStream;


public class DHNTransformer implements net.minecraft.launchwrapper.IClassTransformer {
public byte[] patch (String name, byte[] bytes, String obfname, String iFile, String rname) throws IOException
{
	ClassNode cn = new ClassNode();
	ClassReader cr = new ClassReader(bytes);

	java.io.InputStream in = DHNTransformer.class.getResourceAsStream("/DHNCore/asm/Methods.class");
	ClassNode cnr = new ClassNode();
	ClassReader crr = new ClassReader(in);
	crr.accept(cnr, 0);
	cr.accept(cn, 0);
	Iterator<MethodNode> methods = cn.methods.iterator();
	Iterator<MethodNode> methodsr = cnr.methods.iterator();
	MethodNode mnr = null;
	while (methodsr.hasNext())
	{
		MethodNode temp = methodsr.next();
		System.out.printf("Methods that can be used to replaced are: %s %n", temp.name);
		if (temp.name.equals("rname"))
		{
			mnr = temp;
		}
	}

	while(methods.hasNext())
	{
		MethodNode mn = methods.next();
		System.out.printf("METHOD FOUND: %s %n",mn.name);
		if (mn.name.equals(name) || mn.name.equals(obfname))
			{
			//begin patching
			System.out.printf("Beginning the patching of the method %s %n",name);
			//patching jargin here
			mn.instructions = mnr.instructions;
			System.out.printf("Pathcing has been completed %n");
			}
	}
	ClassWriter cw = new ClassWriter(ClassWriter.COMPUTE_MAXS | ClassWriter.COMPUTE_FRAMES);
	cn.accept(cw);

	return cw.toByteArray();

}
@Override
public byte[] transform(String arg0, String arg1, byte[] arg2) 
{
	if (arg0.equals("bgy")) {
		System.out.println("Doing RenderPlayer transformers in a obfuscated environment");

		}

		if (arg0.equals("net.minecraft.client.renderer.entity.RenderPlayer")) {
		System.out.println("Doing RenderPlayer transformers in a de-obfuscated environment");
		try {
			return patch("renderFirstPersonArm", arg2, "","","renderFirstPersonArm");
		} catch (IOException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}
		}
	return arg2;

}


}

 

Link to comment
Share on other sites

I did some reading up, and I figured out the problem. My end goal was to replace a function in the jar with a function I can write anywhere in the rest of my mod. I achieved exactly what I needed to, thank you for all your help.

Link to comment
Share on other sites

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.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
  • Topics

×
×
  • Create New...

Important Information

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