Jump to content

[SOLVED/Workaround]How to use the Applied Energistics Materials API?


BrozzSama

Recommended Posts

Hi!

 

I'm an happy FTB Ultimate user however i saw that Quartz from Applied Energistics mod can't be crafted with UU-Matter, so i wanted to create a mod for it and i read some tutorials on how to create a mod and i installed both forge and eclipse. Then i looked for the IC2 API and Applied energistics API however when i add the first one it adds an Items class and by checking it i can discover items name but whenever i try to declare matter or any IC2 item it just says that the value doesn't exist, when i add the second one the Applied energistics API (which isn't in the original AE package like it's said on the website so i took it from: https://bitbucket.org/SeargeDP/modularforcefieldsystem/src/0e1a7ca4d4f1d421d5ab6664901751dacd1400c8/src/minecraft/appeng/api?at=default) it doesn't create any item class or something that can be used as an item class.

 

Can somebody give me a hint i looked for tutorials and info's for two whole days but i can't find anything! :'(

 

Link to comment
Share on other sites

 

Thanks for support, i will surely look a little harder next time. So i deobfuscated the two mod jars with BON and by importing them into eclipse i was able to get the matter item stack using

ItemStack MatterItemStack =  ic2.api.Items.getItem("matter");

  but i can't find a way to create a Quartz item stack! I tried everything but it always end up with an error  :-[ .

 

Somebody knows how to do it?

Link to comment
Share on other sites

I'm not familiar with the specifics of the ic2 api, and in my experience there's not too many regulars here who are. I'd recommend that you ask on the API's forums or related channels as there are more likely to be people there whom are more familiar with the API.

 

If you successfully imported the API and it seems fine, then you should read the source code of it and try to understand how it works. See if you can find any documentation for that specific API.

 

Futher more:

I tried everything but it always end up with an error

Sounds more like a problem with java/syntax and not with the API, sadly I'm unable to read your mind at the moment and therefore can't see the error message with my inner eye. Could you perhaps share that here instead unless you prefer to wait until my psychic pew pew return? :)

If you guys dont get it.. then well ya.. try harder...

Link to comment
Share on other sites

I'm not familiar with the specifics of the ic2 api, and in my experience there's not too many regulars here who are. I'd recommend that you ask on the API's forums or related channels as there are more likely to be people there whom are more familiar with the API.

 

If you successfully imported the API and it seems fine, then you should read the source code of it and try to understand how it works. See if you can find any documentation for that specific API.

 

Futher more:

I tried everything but it always end up with an error

Sounds more like a problem with java/syntax and not with the API, sadly I'm unable to read your mind at the moment and therefore can't see the error message with my inner eye. Could you perhaps share that here instead unless you prefer to wait until my psychic pew pew return? :)

 

For the Ic2 part i resolved everything because the forum/wiki is well documented. The problem is currently the applied energistics, i can't find the syntax to create an item stack of Quartz.

Link to comment
Share on other sites

UP.

 

I did some more research and tries and i found out that Applied energistics item stack must be copied however the result is the same. This is the mod code:

 

    @Init
    public void load (FMLInitializationEvent event) {
        proxy.registerRenderers();

        ItemStack matterStack = ic2.api.Items.getItem("matter");
        ItemStack QuartzStack = Materials.matQuartzDust.copy();
        QuartzStack.stackSize=32;

        GameRegistry.addRecipe(QuartzStack, new Object[] { "XX ", "XX ", "  X", Character.valueOf('X'), matterStack });

    }

 

Can someone tell me where's the wrong part? If it's useful the log is here: http://pastebin.com/erHwLGrt

 

Thanks in advance  :)

Link to comment
Share on other sites

I would help us if we can see your main class...

Don't PM me with questions. They will be ignored! Make a thread on the appropriate board for support.

 

1.12 -> 1.13 primer by williewillus.

 

1.7.10 and older versions of Minecraft are no longer supported due to it's age! Update to the latest version for support.

 

http://www.howoldisminecraft1710.today/

Link to comment
Share on other sites

The line:

ItemStack QuartzStack = Materials.matQuartzDust.copy();

causes the crash... But I can't figure out why...

Don't PM me with questions. They will be ignored! Make a thread on the appropriate board for support.

 

1.12 -> 1.13 primer by williewillus.

 

1.7.10 and older versions of Minecraft are no longer supported due to it's age! Update to the latest version for support.

 

http://www.howoldisminecraft1710.today/

Link to comment
Share on other sites

The line:

ItemStack QuartzStack = Materials.matQuartzDust.copy();

causes the crash... But I can't figure out why...

 

Me neither, i also checked a decompiled and deobfuscated version of Applied Energistics and it uses the same syntax but i can't figure out why it doesn't crashes and this does. If you want to check out go here.

Link to comment
Share on other sites

UP

 

I got it working by declaring the ItemStack using the ID!

 

ItemStack QuartzStack = new ItemStack(4362,1,0).copy();

 

However this ID is the conversion Matrix, the Quartz ID is 4362:6, how can i declare it in the ItemStack function? If i type 4362:6 or 4362/6 it crashes when i try the crafting.

 

EDIT: That was a really easy question, you need to use the third value for example

 

ItemStack QuartzStack = new ItemStack(4362,1,6).copy();

 

Remember that if you're using a modpack with custom IDs after mod testing you have to change all of them with the modpack custom ID so when you recompile it works fine with it. For example i tested with 4362:6 because it's the default ID for Applied Energistics but if you're writing a mod for FTB you need to use the ID 4462:6 that doesn't work in the testing environment!

 

I think i can mark the thread as solved thanks to who gave me support :D , the Forge community is pure awesomeness.

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

    • rp.crazyheal.xyz mods  
    • 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.