Jump to content

1.10.2 Forge 2221 - All The Mods


Easter

Recommended Posts

I'm getting a weird crash report lately, last time I ran it this morning it was fine. I hope someone could help me with this

 

2017-01-26 13:09:19,362 WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream

2017-01-26 13:09:19,363 WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream

[13:09:19] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker

[13:09:19] [main/INFO] [LaunchWrapper]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker

[13:09:19] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLTweaker

[13:09:19] [main/INFO] [FML]: Forge Mod Loader version 12.18.3.2221 for Minecraft 1.10.2 loading

[13:09:19] [main/INFO] [FML]: Java is Java HotSpot 64-Bit Server VM, version 1.8.0_121, running on Windows 10:amd64:10.0, installed at C:\Program Files\Java\jre1.8.0_121

[13:09:19] [main/INFO] [FML]: Failed to find the specified repository root C:/Users/Matt/Documents/atm/forge/libraries

2017-01-26 13:09:19,547 WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream

2017-01-26 13:09:19,559 WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream

2017-01-26 13:09:19,561 WARN Unable to instantiate org.fusesource.jansi.WindowsAnsiOutputStream

[13:09:19] [main/INFO] [FML]: [AppEng] Core Init

[13:09:19] [main/WARN] [FML]: The coremod lumien.bloodmoon.asm.LoadingPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:19] [main/WARN] [FML]: The coremod team.chisel.common.asm.ChiselCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:19] [main/WARN] [FML]: The coremod codechicken.lib.asm.CCLCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:20] [main/WARN] [FML]: The coremod pl.asie.foamfix.coremod.FoamFixCore does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:20] [main/WARN] [FML]: The coremod net.shadowfacts.forgelin.ForgelinPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:20] [main/WARN] [FML]: The coremod ic2.core.coremod.IC2core does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:20] [main/WARN] [FML]: The coremod invtweaks.forge.asm.FMLPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:20] [main/WARN] [FML]: The coremod net.malisis.core.asm.MalisisCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:09:20] [main/WARN] [FML]: The coremod mekanism.common.launch.LoadingHook does not have a MCVersion annotation, it may cause issues with this version of Minecraft

 

 

Link to comment
Share on other sites

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in deepresonance-1.1x-1.4.3.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy DefaultOptions_1.10.2-6.1.5.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in DefaultOptions_1.10.2-6.1.5.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class DefaultOptionsLoadingPlugin

[13:45:39] [main/TRACE] [FML/]: coremod named Default Options is loading

[13:45:39] [main/DEBUG] [FML/]: The coremod net.blay09.mods.defaultoptions.coremod.DefaultOptionsLoadingPlugin requested minecraft version 1.10.2 and minecraft is 1.10.2. It will be loaded.

[13:45:39] [main/DEBUG] [FML/]: Enqueued coremod Default Options

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy Draconic-Evolution-1.10.2-2.0.7.168-universal.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in Draconic-Evolution-1.10.2-2.0.7.168-universal.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy ElecCore-1.10.2-1.6.379.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in ElecCore-1.10.2-1.6.379.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy embers-0.104.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in embers-0.104.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy EnderBags-1.9.4-2.0.0.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in EnderBags-1.9.4-2.0.0.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy EnderCore-1.10.2-0.4.1.64-beta.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in EnderCore-1.10.2-0.4.1.64-beta.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class EnderCorePlugin

[13:45:39] [main/DEBUG] [FML/]: The coremod com.enderio.core.common.transform.EnderCorePlugin requested minecraft version 1.10.2 and minecraft is 1.10.2. It will be loaded.

[13:45:39] [main/DEBUG] [FML/]: Enqueued coremod EnderCorePlugin

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy EnderIO-1.10.2-3.1.161.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in EnderIO-1.10.2-3.1.161.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy EnderStorage-1.10.2-2.2.0.96-universal.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in EnderStorage-1.10.2-2.2.0.96-universal.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy endertanks-1.10.0-1.4.9.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in endertanks-1.10.0-1.4.9.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy enderthing-1.10.2-0.7.3.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in enderthing-1.10.2-0.7.3.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy EnderZoo-1.10-1.2.3.43.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in EnderZoo-1.10-1.2.3.43.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy EndMetals_1.9-1.0.4.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in EndMetals_1.9-1.0.4.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy EngineersWorkshop-1.1.4-1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in EngineersWorkshop-1.1.4-1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy environmentaltech-1.10.2-0.10.5i.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in environmentaltech-1.10.2-0.10.5i.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy ExtraRails-1.10.2-1.1.1.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in ExtraRails-1.10.2-1.1.1.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy extrautils2-1.10.2-1.1.3d.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in extrautils2-1.10.2-1.1.3d.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy ExtremeReactors-1.10.2-0.4.5.24.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in ExtremeReactors-1.10.2-0.4.5.24.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy FastLeafDecay-v11.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in FastLeafDecay-v11.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy flatcoloredblocks-mc1.10-v4.4.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in flatcoloredblocks-mc1.10-v4.4.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy FluxNetworks-1.10.2-1.1.1.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in FluxNetworks-1.10.2-1.1.1.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy foamfix-0.5.2-anarchy.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in foamfix-0.5.2-anarchy.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class FoamFixCore

[13:45:39] [main/TRACE] [FML/]: coremod named Do not report to Forge! Remove FoamFixAPI (or replace with FoamFixAPI-Lawful) and try again. is loading

[13:45:39] [main/WARN] [FML/]: The coremod pl.asie.foamfix.coremod.FoamFixCore does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:45:39] [main/DEBUG] [FML/]: Enqueued coremod Do not report to Forge! Remove FoamFixAPI (or replace with FoamFixAPI-Lawful) and try again.

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy forestry_1.10.2-5.2.17.354.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in forestry_1.10.2-5.2.17.354.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy Forgelin-1.2.0.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in Forgelin-1.2.0.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class ForgelinPlugin

[13:45:39] [main/WARN] [FML/]: The coremod net.shadowfacts.forgelin.ForgelinPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:45:39] [main/DEBUG] [FML/]: Enqueued coremod ForgelinPlugin

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy FTBLib-1.10.2-3.2.3.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in FTBLib-1.10.2-3.2.3.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy FTBUtilities-1.10.2-3.2.4.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in FTBUtilities-1.10.2-3.2.4.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy funky-locomotion-1.10.2-alpha-0.0.3.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in funky-locomotion-1.10.2-alpha-0.0.3.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy gendustry-1.6.5.27-mc1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in gendustry-1.6.5.27-mc1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy generators-0.9.20.19-mc1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in generators-0.9.20.19-mc1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy GiacomosFishingNet1.10.2-1.4.4.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in GiacomosFishingNet1.10.2-1.4.4.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy Grapple-Hooks-1.10.2-1.0.8.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in Grapple-Hooks-1.10.2-1.0.8.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy Gravitation Suite-3.0.1.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in Gravitation Suite-3.0.1.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy Guide-API-1.10.2-2.0.2-45.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in Guide-API-1.10.2-2.0.2-45.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy ImmersiveEngineering-0.10-55.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in ImmersiveEngineering-0.10-55.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy industrialcraft-2-2.6.142-ex110.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in industrialcraft-2-2.6.142-ex110.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class IC2core

[13:45:39] [main/WARN] [FML/]: The coremod ic2.core.coremod.IC2core does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:45:39] [main/DEBUG] [FML/]: Enqueued coremod IC2core

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy InfernalMobs-1.10.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in InfernalMobs-1.10.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy InventoryTweaks-1.62-dev-66.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in InventoryTweaks-1.62-dev-66.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class FMLPlugin

[13:45:39] [main/WARN] [FML/]: The coremod invtweaks.forge.asm.FMLPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:45:39] [main/DEBUG] [FML/]: Added access transformer class invtweaks.forge.asm.ITAccessTransformer to enqueued access transformers

[13:45:39] [main/DEBUG] [FML/]: Enqueued coremod FMLPlugin

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy IronBackpacks-1.10.2-2.2.22.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in IronBackpacks-1.10.2-2.2.22.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy ironchest-1.10.2-7.0.11.797.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in ironchest-1.10.2-7.0.11.797.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy itemscroller-1.10.2-0.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in itemscroller-1.10.2-0.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy jei_1.10.2-3.14.3.403.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in jei_1.10.2-3.14.3.403.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy jeibees-0.9.0.4-mc1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in jeibees-0.9.0.4-mc1.10.2.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy journeymap-1.10.2-5.4.3.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in journeymap-1.10.2-5.4.3.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy JustEnoughCalculation-1.10.2-2.3.2.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in JustEnoughCalculation-1.10.2-2.3.2.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy JustEnoughResources-1.10.2-0.5.8.98.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in JustEnoughResources-1.10.2-0.5.8.98.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy librarianlib-1.8.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in librarianlib-1.8.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy malisiscore-1.10.2-4.2.10.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in malisiscore-1.10.2-4.2.10.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class MalisisCorePlugin

[13:45:39] [main/WARN] [FML/]: The coremod net.malisis.core.asm.MalisisCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[13:45:39] [main/DEBUG] [FML/]: Enqueued coremod MalisisCorePlugin

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy malisisdoors-1.10.2-5.1.7.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in malisisdoors-1.10.2-5.1.7.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy Mantle-1.10.2-1.1.4.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in Mantle-1.10.2-1.1.4.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy mcjtylib-1.1x-2.3.4.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in mcjtylib-1.1x-2.3.4.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy MCMultiPart-experimental-2.0.0_88-universal.jar

[13:45:39] [main/DEBUG] [FML/]: Not found coremod data in MCMultiPart-experimental-2.0.0_88-universal.jar

[13:45:39] [main/DEBUG] [FML/]: Examining for coremod candidacy Mekanism-1.10.2-9.2.1.298.jar

[13:45:39] [main/TRACE] [FML/]: Found FMLCorePluginContainsFMLMod marker in Mekanism-1.10.2-9.2.1.298.jar, it will be examined later for regular @Mod instances

[13:45:39] [main/DEBUG] [FML/]: Instantiating coremod class LoadingHook

[13:45:39] [main/WARN] [FML/]: The coremod mekanism.common.launch.LoadingHook does not have a MCVersion annotation, it may cause issues with this version of Minecraft

 

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.