Jump to content

1.6.2 How to get mod compatability?


Nieue

Recommended Posts

Hello, I want to be able to make my mod so that IF for example buildcraft/ic2 is installed alongside my mod that new items and recipes show up in my mod.

For example, if my mod were to add loads of pickaxes but I didn't add tin into the mod, if I also installed ic2 there would be a new item called a tin pickaxe and a recipe for it.

 

How would I go about doing this?

Link to comment
Share on other sites

Well, if you are making the items usable by these other mods, via fuel or pipe connections or EU users or whatever, you're going to need the APIs. In your question you just said you wanted to add new content using another mod's items, in which case would not require the API to make a tin pickaxe. Hopefully that makes sense.

Link to comment
Share on other sites

Well, if you are making the items usable by these other mods, via fuel or pipe connections or EU users or whatever, you're going to need the APIs. In your question you just said you wanted to add new content using another mod's items, in which case would not require the API to make a tin pickaxe. Hopefully that makes sense.

Okay, thanks.

But where do I put this line? Because in Preinit it gives me errors, or should I make the modid a string?

Link to comment
Share on other sites

The modID needs to be a String that represents the mod you are checking for. When you made your @Mod, you gave it modid = "someID". All @Mods have this, so you need to know what the ID of the mod is. You can check that mod's mcmod.info, and it should give it to you. For example, if you wanted to check and see if my mod Plunder Rummage was installed, you'd do this:

 

if(Loader.isModLoader("PR"))
{
     //do stuff
}

Link to comment
Share on other sites

The modID needs to be a String that represents the mod you are checking for. When you made your @Mod, you gave it modid = "someID". All @Mods have this, so you need to know what the ID of the mod is. You can check that mod's mcmod.info, and it should give it to you. For example, if you wanted to check and see if my mod Plunder Rummage was installed, you'd do this:

 

if(Loader.isModLoader("PR"))
{
     //do stuff
}

okay thanks :)

Link to comment
Share on other sites

Okay, so I tried that (with two of my own mods to test) and I got an error when trying to start minecraft with both installed at the same time.

There are no ID conflicts

 

Crash log:

 

---- Minecraft Crash Report ----

// Why did you do that?

 

Time: 19-7-13 21:18

Description: Initializing game

 

java.lang.NullPointerException

at net.minecraft.item.ItemStack.<init>(ItemStack.java:76)

at assets.ncombiners.common.Mainclass.PreInit(Mainclass.java:120)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:540)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)

at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)

at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)

at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)

at com.google.common.eventbus.EventBus.post(EventBus.java:267)

at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:193)

at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:173)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)

at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)

at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)

at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)

at com.google.common.eventbus.EventBus.post(EventBus.java:267)

at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:104)

at cpw.mods.fml.common.Loader.loadMods(Loader.java:521)

at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:172)

at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:470)

at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:796)

at net.minecraft.client.main.Main.main(SourceFile:101)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)

at net.minecraft.launchwrapper.Launch.main(Launch.java:18)

 

 

A detailed walkthrough of the error, its code path and all known details is as follows:

---------------------------------------------------------------------------------------

 

-- Head --

Stacktrace:

at net.minecraft.item.ItemStack.<init>(ItemStack.java:76)

at assets.ncombiners.common.Mainclass.PreInit(Mainclass.java:120)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:540)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)

at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)

at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)

at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)

at com.google.common.eventbus.EventBus.post(EventBus.java:267)

at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:193)

at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:173)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)

at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)

at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)

at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)

at com.google.common.eventbus.EventBus.post(EventBus.java:267)

at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:104)

at cpw.mods.fml.common.Loader.loadMods(Loader.java:521)

at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:172)

at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:470)

 

-- Initialization --

Details:

Stacktrace:

at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:796)

at net.minecraft.client.main.Main.main(SourceFile:101)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)

at net.minecraft.launchwrapper.Launch.main(Launch.java:18)

 

-- System Details --

Details:

Minecraft Version: 1.6.2

Operating System: Windows 8 (amd64) version 6.2

Java Version: 1.7.0_21, Oracle Corporation

Java VM Version: Java HotSpot 64-Bit Server VM (mixed mode), Oracle Corporation

Memory: 1863476128 bytes (1777 MB) / 2058027008 bytes (1962 MB) up to 2058027008 bytes (1962 MB)

JVM Flags: 2 total; -Xmx2048M -Xms2048M

AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used

Suspicious classes: FML and Forge are installed

IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0

FML: MCP v8.04 FML v6.2.19.789 Minecraft Forge 9.10.0.789 5 mods loaded, 5 mods active

mcp{8.04} [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed->Pre-initialized

FML{6.2.19.789} [Forge Mod Loader] (coremods) Unloaded->Constructed->Pre-initialized

Forge{9.10.0.789} [Minecraft Forge] (coremods) Unloaded->Constructed->Pre-initialized

amethysttools{1.0} [amethyst tools] (AmethystTools[1.6.2].zip) Unloaded->Constructed->Pre-initialized

ncombiners{dev} [Nieue's Combiners] (Ncombiners_dev.zip) Unloaded->Constructed->Errored

Launched Version: 1.6.2-Forge9.10.0.789

LWJGL: 2.9.0

OpenGL: Intel® HD Graphics 4000 GL version 4.0.0 - Build 9.17.10.2849, Intel

Is Modded: Definitely; Client brand changed to 'fml,forge'

Type: Client (map_client.txt)

Resource Pack: 1.5.2 faithful 2.0.zip

Current Language: English (US)

Profiler Position: N/A (disabled)

Vec3 Pool Size: ~~ERROR~~ NullPointerException: null

 

Where I put the line you gave me, the mod id is correct

@PreInit
public void PreInit(FMLPreInitializationEvent event)
{
	if(Loader.isModLoaded("amethysttools"))
	{
		ItemStack ame = new ItemStack(Amethyst);
		ItemStack red = new ItemStack(Item.redstone);

		GameRegistry.addRecipe(new ItemStack (AmethystBullet, 4), "  r", "aar", "  r",
				'a', ame, 'r', red);    
	}	

Link to comment
Share on other sites

hmm, i also got a question, not that everything has to be done in the pre-init, is there a way to change the load order of mods? in this case cant he simply change his itemstack creation to the init phase ?

If the job HAS to be done during the preinit, like a item that is based off another item, what can he do to make sure that the other mod is loaded before his ?

how to debug 101:http://www.minecraftforge.net/wiki/Debug_101

-hydroflame, author of the forge revolution-

Link to comment
Share on other sites

heres what happening

 

1 your mod loads

2 amethyst mod loads

 

because your mod is the first to load you get obvious problem of "well thsi doesnt exists"

 

what you WOULD like to happen is that

 

1 amethyst mod load

2 your mod loads

 

but afaik theres no way to set the mod load order

 

what you could try is move all that code in the init() phase or even postinit() this way its possible that amethyst mod will be loaded when you get there and that the item Amethyst will exists

how to debug 101:http://www.minecraftforge.net/wiki/Debug_101

-hydroflame, author of the forge revolution-

Link to comment
Share on other sites

Dependencies are:

@Mod(modid = "modid" name = "modname", version = "v0.123", dependencies = "required-after:IC2")

That'll require any version of IC2 to run and it'll always run after the dependency's loaded.

 

EDIT: And for 'specific' version:

dependencies = "required-after:IC2@[1.1.7,)")

Would require the minimum version of IC2 to be 1.1.7

Link to comment
Share on other sites

Dependencies are:

@Mod(modid = "modid" name = "modname", version = "v0.123", dependencies = "required-after:IC2")

That'll require any version of IC2 to run and it'll always run after the dependency's loaded.

 

EDIT: And for 'specific' version:

dependencies = "required-after:IC2@[1.1.7,)")

Would require the minimum version of IC2 to be 1.1.7

But then it will become an addon, so it would require IC2 to work at all, wouldn't it?

I don't want it to do that

Link to comment
Share on other sites

Dependencies are:

@Mod(modid = "modid" name = "modname", version = "v0.123", dependencies = "required-after:IC2")

That'll require any version of IC2 to run and it'll always run after the dependency's loaded.

 

EDIT: And for 'specific' version:

dependencies = "required-after:IC2@[1.1.7,)")

Would require the minimum version of IC2 to be 1.1.7

But then it will become an addon, so it would require IC2 to work at all, wouldn't it?

I don't want it to do that

 

Yeah, that's a hard dependency, as Chibill said just use 'after' rather than 'required-after' for a soft depend.

Link to comment
Share on other sites

Dependencies are:

@Mod(modid = "modid" name = "modname", version = "v0.123", dependencies = "required-after:IC2")

That'll require any version of IC2 to run and it'll always run after the dependency's loaded.

 

EDIT: And for 'specific' version:

dependencies = "required-after:IC2@[1.1.7,)")

Would require the minimum version of IC2 to be 1.1.7

But then it will become an addon, so it would require IC2 to work at all, wouldn't it?

I don't want it to do that

 

Yeah, that's a hard dependency, as Chibill said just use 'after' rather than 'required-after' for a soft depend.

So, if I want to load a new item when that other mod is loaded as well, do I just put:

@Mod(modid = "modid" name = "modname", version = "v0.123", dependencies = "required-after:IC2")

public static Item TestItem;

@PreInit
public void PreInit(FMLPreInitializationEvent event)
{
	if(Loader.isModLoaded("IC2"))
	{
	TestItem= new TestItem(5013).setUnlocalizedName("testitem");

		ItemStack test = new ItemStack(TestItem);
		ItemStack red = new ItemStack(Item.redstone);

		GameRegistry.addRecipe(new ItemStack (TestItem 4), "  r", "aar", "  r",
				'a', test, 'r', red);    
	}	

?

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

    • The future of Bitcoin recovery is a topic of great interest and excitement, particularly with the emergence of innovative companies like Dexdert Net Pro Recovery leading the charge. As the cryptocurrency market continues to evolve and face new challenges, the need for effective solutions to help users recover lost or stolen Bitcoin has become increasingly critical. Dexdert Net Pro, a specialized firm dedicated to this very purpose, has positioned itself at the forefront of this emerging field. Through their proprietary techniques and deep expertise in blockchain technology, Dexdert Net Pro has developed a comprehensive approach to tracking down and retrieving misplaced or compromised Bitcoin, providing a lifeline to individuals and businesses who have fallen victim to the inherent risks of the digital currency landscape. Their team of seasoned investigators and cryptography experts employ a meticulous, multi-pronged strategy, leveraging advanced data analysis, forensic techniques, and collaborative partnerships with law enforcement to painstakingly trace the movement of lost or stolen coins, often recovering funds that would otherwise be considered irrecoverable. This pioneering work not only restores financial assets but also helps to bolster confidence and trust in the long-term viability of Bitcoin, cementing Dexdert Net Pro role as a crucial player in shaping the future of cryptocurrency recovery and security. As the digital finance ecosystem continues to evolve, the importance of innovative solutions like those offered by Dexdert Net Pro will only grow, ensuring that users can navigate the complexities of Bitcoin with greater peace of mind and protection. Call Dexdert Net Pro now     
    • 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.