Leaderboard
Popular Content
Showing content with the highest reputation since 02/19/24 in all areas
-
This has already been the de-facto standard for quite a while now, but figured it would be a good idea to properly formalise it and make it clear for everyone. TL;DR: You can ask and offer support for Forge on any MC version, as long as you're not demanding it from staff and can accept that older versions may receive less attention due to people moving on to newer, shinier things. Tiered support policy There are now essentially three tiers of support: full, legacy and minimal. Full support This tier has dedicated channels for help on the Discord, gets priority for documentation, new features and bugfixes, and is generally considered the main focus for Forge development and support. Triage actively ports and backports things as needed for versions within this tier where time allows. The MC versions covered by this follows the existing "LTS" system. In other words, the latest MC version and select versions before it are covered by this tier. We recommend people consider using the newest version possible, as it's likely to be fully supported for longer. Legacy support This tier is for older versions of MC that are no longer covered by the full support tier. This tier gets less attention, but is still supported to some extent. To be clear, this is not a "no support" tier, but it is not the main focus. You're welcome to ask for help, submit PRs and help out, but please be aware that you may not get a response as quickly as these versions are generally not as popular anymore and may not have as many people around to help. Staff may still choose to work on these legacy versions and help people, but please don't demand it from them. Please note that due to the nature of the old toolchains used for building legacy versions, developing mods using the default MDK may not work. We also cannot easily publish updates to some of these old versions without your help - if you're interested in fixing this, please reach out to us. Minimal support This is rare and usually only applies to versions of MC where there's no legitimate reason to be using them. A real-world example of this is 1.20.3, which had a data loss bug that was fixed in 1.20.4 shortly after. All mods made for 1.20.3 work on 1.20.4, so there's no reason to use 1.20.3. We will help you update to the fixed version instead, but that's about it.2 points
-
I would like to display the distance of the player from the center of a filled map or from map decorations if present. I have found that the world coordinates of decorations are in the item's tag. However, for banners or maps without decorations, they are not present in the tag. I found in the MapItemSavedData class the coordinates of the center: "centerX" and "centerZ," which would be perfect for my case. However, this class seems to be updated only on the server side. How can I determine the absolute coordinates of banners or the map center on the client side? Thank you very much!1 point
-
1 point
-
1 point
-
I think I can go without for now, hopefully a future update fixes it. Thanks for the help, though!1 point
-
Nevermind! Apparently I forgot to increase the RAM allocation for Minecraft on curseforge after I reinstalled it and it now works just fine. Thank you again for the help!1 point
-
Use a custom Launcher like FTB App, MultiMC or At Launcher and import this modpack1 point
-
[09:49:55] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker [09:49:55] [main/INFO]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker [09:49:55] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLTweaker [09:49:55] [main/INFO]: Forge Mod Loader version 14.23.5.2860 for Minecraft 1.12.2 loading [09:49:55] [main/INFO]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_51, running on Windows 10:amd64:10.0, installed at C:\Users\diego\curseforge\minecraft\Install\runtime\jre-legacy\windows-x64\jre-legacy [09:49:56] [main/INFO]: Searching C:\Users\diego\curseforge\minecraft\Instances\Enigmatica 2 Expert - E2E\mods for mods [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in AdvancedRocketry-1.12.2-2.0.0-13.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod AdvancedRocketryPlugin (zmaster587.advancedRocketry.asm.AdvancedRocketryPlugin) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in AppleCore-mc1.12.2-3.4.0.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod AppleCore (squeek.applecore.AppleCore) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in astralsorcery-1.12.2-1.10.27.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod hellfirepvp.astralsorcery.core.AstralCore does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/INFO]: [AstralCore] Initialized. [09:49:56] [main/INFO]: Loading tweaker guichaguri.betterfps.tweaker.BetterFpsTweaker from BetterFps-1.4.8.jar [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in colytra-1.12.2-1.2.0.4.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod c4.colytra.asm.ColytraLoadingPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in CTM-MC1.12.2-1.0.2.31.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod team.chisel.ctm.client.asm.CTMCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: The coremod CTMCorePlugin (team.chisel.ctm.client.asm.CTMCorePlugin) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in engineers_doors-1.12.2-0.9.1.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod EngineersDoorsLoadingPlugin (nihiltres.engineersdoors.common.asm.EngineersDoorsLoadingPlugin) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in foamfix-0.10.15-1.12.2.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod pl.asie.foamfix.coremod.FoamFixCore does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: The coremod Do not report to Forge! (If you haven't disabled the FoamFix coremod, try disabling it in the config! Note that this bit of text will still appear.) (pl.asie.foamfix.coremod.FoamFixCore) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in Forgelin-1.8.4.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod net.shadowfacts.forgelin.preloader.ForgelinPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: The coremod ForgelinPlugin (net.shadowfacts.forgelin.preloader.ForgelinPlugin) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in give-me-back-my-hp-1.12.2-1.0.0.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod xyz.phanta.givemebackmyhp.GiveMeBackMyHpCore does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: The coremod GiveMeBackMyHpCore (xyz.phanta.givemebackmyhp.GiveMeBackMyHpCore) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in iceandfire-1.9.1-1.12.2.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod iceandfire (com.github.alexthe666.iceandfire.asm.IceAndFirePlugin) is not signed! [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in InventoryTweaks-1.64+dev.151.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod invtweaks.forge.asm.FMLPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: The coremod ivorius.ivtoolkit.IvToolkitLoadingPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: The coremod IvToolkit (ivorius.ivtoolkit.IvToolkitLoadingPlugin) is not signed! [09:49:56] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from LagGoggles-FAT-1.12.2-4.11-92.jar [09:49:56] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in Mekanism-1.12.2-9.8.3.390.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:56] [main/WARN]: The coremod mekanism.coremod.MekanismCoremod does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:56] [main/WARN]: The coremod MekanismCoremod (mekanism.coremod.MekanismCoremod) is not signed! [09:49:56] [main/WARN]: The coremod PluginLoader (kaptainwutax.memorytester.utility.PluginLoader) is not signed! [09:49:56] [MemoryTesterThread/INFO]: [kaptainwutax.memorytester.init.InitData:initializeConfigs:29]: DataConfig{MemoryTesterVersion, RecommendedMemoryAllocation, UseMenu, CrashWhenNotEnoughMemory, WindowIconDir} at config/MemoryTester/General.txt [09:49:56] [MemoryTesterThread/INFO]: [kaptainwutax.memorytester.init.InitData:initializeConfigs:29]: DataConfig{Header, Line1WhenOptimalMemory, Line1WhenNonoptimalMemory, ButtonStartText, ButtonStartBgColor, ButtonQuitText, ButtonQuitBgColor, BackgroundImageDir} at config/MemoryTester/Menu.txt [09:49:56] [MemoryTesterThread/INFO]: [kaptainwutax.memorytester.init.InitData:initializeConfigs:29]: DataConfig{InfoHeader, InfoLine1, InfoLine2, InfoFooter, RedirectLink, RedirectBgColor, BackgroundImageDir} at config/MemoryTester/Crash.txt [09:49:57] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in NotEnoughIDs-1.5.4.4.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:57] [main/WARN]: The coremod ru.fewizz.neid.asm.Plugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:57] [main/WARN]: The coremod Plugin (ru.fewizz.neid.asm.Plugin) is not signed! [09:49:57] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in OpenComputers-MC1.12.2-1.8.3+274990f.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:57] [main/WARN]: The coremod li.cil.oc.common.launch.TransformerLoader does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:57] [main/WARN]: The coremod TransformerLoader (li.cil.oc.common.launch.TransformerLoader) is not signed! [09:49:57] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in OpenModsLib-1.12.2-0.12.2.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:57] [main/WARN]: The coremod openmods.core.OpenModsCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:57] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in Quark-r1.6-179.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:57] [main/WARN]: The coremod Quark Plugin (vazkii.quark.base.asm.LoadingPlugin) is not signed! [09:49:57] [main/WARN]: The coremod com.therandomlabs.randompatches.core.RPCore does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:57] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in RandomThings-MC1.12.2-4.2.7.4.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:57] [main/WARN]: The coremod lumien.randomthings.asm.LoadingPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:57] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in ResourceLoader-MC1.12.1-1.5.3.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [09:49:57] [main/WARN]: The coremod lumien.resourceloader.asm.LoadingPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:57] [main/WARN]: The coremod io.dogboy.serializationisbad.legacyforge.SerializationIsBadCoreMod does not have a MCVersion annotation, it may cause issues with this version of Minecraft [09:49:57] [main/WARN]: The coremod serializationisbad (io.dogboy.serializationisbad.legacyforge.SerializationIsBadCoreMod) is not signed! [09:49:57] [main/INFO]: Initializing SerializationIsBad, implementation type: legacyforge [09:49:57] [main/ERROR]: Failed to load remote config file javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) ~[?:1.8.0_51] at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949) ~[?:1.8.0_51] at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) ~[?:1.8.0_51] at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296) ~[?:1.8.0_51] at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1497) ~[?:1.8.0_51] at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:212) ~[?:1.8.0_51] at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) ~[?:1.8.0_51] at sun.security.ssl.Handshaker.process_record(Handshaker.java:914) ~[?:1.8.0_51] at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) ~[?:1.8.0_51] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) ~[?:1.8.0_51] at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) ~[?:1.8.0_51] at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) ~[?:1.8.0_51] at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563) ~[?:1.8.0_51] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) ~[?:1.8.0_51] at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512) ~[?:1.8.0_51] at sun.net.www.protocol.http.HttpURLConnection.access$200(HttpURLConnection.java:90) ~[?:1.8.0_51] at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1432) ~[?:1.8.0_51] at sun.net.www.protocol.http.HttpURLConnection$9.run(HttpURLConnection.java:1430) ~[?:1.8.0_51] at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_51] at java.security.AccessController.doPrivileged(AccessController.java:713) ~[?:1.8.0_51] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1429) ~[?:1.8.0_51] at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) ~[?:1.8.0_51] at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) ~[?:1.8.0_51] at io.dogboy.serializationisbad.core.SerializationIsBad.readRemoteConfig(SerializationIsBad.java:121) [serializationisbad-1.4.jar:1.4] at io.dogboy.serializationisbad.core.SerializationIsBad.readConfig(SerializationIsBad.java:101) [serializationisbad-1.4.jar:1.4] at io.dogboy.serializationisbad.core.SerializationIsBad.<init>(SerializationIsBad.java:61) [serializationisbad-1.4.jar:1.4] at io.dogboy.serializationisbad.core.SerializationIsBad.init(SerializationIsBad.java:43) [serializationisbad-1.4.jar:1.4] at io.dogboy.serializationisbad.legacyforge.SerializationIsBadCoreMod.<init>(SerializationIsBadCoreMod.java:19) [serializationisbad-1.4.jar:1.4] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_51] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [?:1.8.0_51] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [?:1.8.0_51] at java.lang.reflect.Constructor.newInstance(Constructor.java:422) [?:1.8.0_51] at java.lang.Class.newInstance(Class.java:442) [?:1.8.0_51] at net.minecraftforge.fml.relauncher.CoreModManager.loadCoreMod(CoreModManager.java:594) [forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.CoreModManager.discoverCoreMods(CoreModManager.java:451) [forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.CoreModManager.handleLaunch(CoreModManager.java:265) [forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupHome(FMLLaunchHandler.java:107) [forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupClient(FMLLaunchHandler.java:81) [forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.FMLLaunchHandler.configureForClientLaunch(FMLLaunchHandler.java:42) [forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.common.launcher.FMLTweaker.injectIntoClassLoader(FMLTweaker.java:141) [forge-1.12.2-14.23.5.2860.jar:?] at net.minecraft.launchwrapper.Launch.launch(Launch.java:115) [launchwrapper-1.12.jar:?] at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.12.jar:?] Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:387) ~[?:1.8.0_51] at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292) ~[?:1.8.0_51] at sun.security.validator.Validator.validate(Validator.java:260) ~[?:1.8.0_51] at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[?:1.8.0_51] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[?:1.8.0_51] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[?:1.8.0_51] at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1479) ~[?:1.8.0_51] ... 37 more Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:145) ~[?:1.8.0_51] at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:131) ~[?:1.8.0_51] at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) ~[?:1.8.0_51] at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382) ~[?:1.8.0_51] at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292) ~[?:1.8.0_51] at sun.security.validator.Validator.validate(Validator.java:260) ~[?:1.8.0_51] at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) ~[?:1.8.0_51] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) ~[?:1.8.0_51] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) ~[?:1.8.0_51] at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1479) ~[?:1.8.0_51] ... 37 more [09:49:57] [main/INFO]: Using local config file as a fallback [09:49:57] [main/ERROR]: Unable to launch java.lang.RuntimeException: An error occurred trying to configure the Minecraft home at C:\Users\diego\curseforge\minecraft\Instances\Enigmatica 2 Expert - E2E for Forge Mod Loader at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupHome(FMLLaunchHandler.java:111) ~[forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupClient(FMLLaunchHandler.java:81) ~[forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.FMLLaunchHandler.configureForClientLaunch(FMLLaunchHandler.java:42) ~[forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.common.launcher.FMLTweaker.injectIntoClassLoader(FMLTweaker.java:141) ~[forge-1.12.2-14.23.5.2860.jar:?] at net.minecraft.launchwrapper.Launch.launch(Launch.java:115) [launchwrapper-1.12.jar:?] at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.12.jar:?] Caused by: java.lang.RuntimeException: You are currently using SerializationIsBad without any patch modules configured. The mod on its own doesn't do anything so please install a config file patching the vulnerabilities at io.dogboy.serializationisbad.core.SerializationIsBad.<init>(SerializationIsBad.java:63) ~[serializationisbad-1.4.jar:1.4] at io.dogboy.serializationisbad.core.SerializationIsBad.init(SerializationIsBad.java:43) ~[serializationisbad-1.4.jar:1.4] at io.dogboy.serializationisbad.legacyforge.SerializationIsBadCoreMod.<init>(SerializationIsBadCoreMod.java:19) ~[serializationisbad-1.4.jar:1.4] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_51] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_51] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_51] at java.lang.reflect.Constructor.newInstance(Constructor.java:422) ~[?:1.8.0_51] at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_51] at net.minecraftforge.fml.relauncher.CoreModManager.loadCoreMod(CoreModManager.java:594) ~[forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.CoreModManager.discoverCoreMods(CoreModManager.java:451) ~[forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.CoreModManager.handleLaunch(CoreModManager.java:265) ~[forge-1.12.2-14.23.5.2860.jar:?] at net.minecraftforge.fml.relauncher.FMLLaunchHandler.setupHome(FMLLaunchHandler.java:107) ~[forge-1.12.2-14.23.5.2860.jar:?] ... 5 more [09:49:57] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: net.minecraftforge.fml.relauncher.FMLSecurityManager$ExitTrappedException [09:49:57] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraftforge.fml.relauncher.FMLSecurityManager.checkPermission(FMLSecurityManager.java:49) [09:49:57] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: at java.lang.SecurityManager.checkExit(SecurityManager.java:761) [09:49:57] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: at java.lang.Runtime.exit(Runtime.java:107) [09:49:57] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: at java.lang.System.exit(System.java:971) [09:49:57] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraft.launchwrapper.Launch.launch(Launch.java:138) [09:49:57] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: at net.minecraft.launchwrapper.Launch.main(Launch.java:28)1 point
-
Thanks for the help, I was hoping it was something I could fix on my end, but after a bit more testing it seems the mod won’t run in a server at all 🥲 just have to hope it gets fixed1 point
-
1 point
-
Remove DamageIndicatorsMod from the server - you can keep it in your client This mod is a client-side-only mod1 point
-
I update the supplementaries mod and the problem fixed, thank you for your help.1 point
-
1 point
-
1 point
-
1 point
-
Add the full crash-report or latest.log (logs-folder) with sites like https://paste.ee/ and paste the link to it here1 point
-
It's going to take up a hell of a lot of my time, a lot of mods are incompatible on this version, I'll just do without the shader this time... thanks for the help though.1 point
-
1 point
-
Just figured it out. I had to update my AMD integrated graphics. I didn't realize you needed to update that as well.1 point
-
1 point
-
for information: I had to remove the two mods: valkyrien skies and shimmer. rubidium and oculus doesn't work with these two mods1 point
-
Still crashed, gonna check my mods folder. Log: https://paste.ee/p/XxI90 I found it! the source of the problem! I looked in the mods folder, and for some reason, a few mods had duplicates. They don't show up in the logs, or the mod loader, so that's weird. Edit: I realize that I probably coulda just checked my mods folder from the start. Sorry if I wasted your time in any way. Thanks for the help though, you helped me narrow it down until I had no other choice but to comb through the game files.1 point
-
1 point
-
1 point
-
1 point
-
turns out it was the varied village sizes mod its working now1 point
-
1 point
-
disregard this post, i've fixed the issue. normally i add all my mods first and then the requirements like libraries, since it shows what i need on launch without crashing. this time it was different i guess. i added the requirements and it runs fine!1 point
-
1 point
-
Sorry it took me a while to realize someone responded to this. The separate directory thing worked! Thanks for the help!1 point
-
Of course not - like I said: there is no support Save for money and get the original one - with legit Custom Launchers, you will have access to a huge variety of pre-configured modpacks and servers The download of cracked launchers often link to malicious sites and similar - or the launcher itself contains malware etc1 point
-
that is not what I need I need, I need the drinks to act like water bottles But thanks1 point
-
In case anyone happens on this with the same issue, I was able to overcome it. After re-reading @Paint_Ninja's last post numerous time, it finally dawned on me that he was referring wholly to the forge installer, which has nothing to do with the packaged modpack installer. As such, I downloaded the new copy of the forge installer and copied it to my linux host, then opened a second ssh session and prepared a cp command to move the new (correct) installer over to the install directory where I was installing the modpack. After the modpack installer had just about finished retrieving files, I overwrote the installer.jar file with the correct one in a seperate ssh session. The modpack (packaged) installer then used that jar to install forge with the included files, and the install finished as I would have expected. Thanks all!1 point
-
This is a known issue caused by Mojang abruptly removing one of their domain names. Download a fresh copy of the installer and it should be fixed. More details in the announcements channel of the new Forge Discord server: https://discord.com/channels/1129059589325852724/1129077934330744882/1212091927038533662 https://discord.com/channels/1129059589325852724/1129077934330744882/1212138871907684382 Invite link: https://discord.minecraftforge.net1 point
-
1 point
-
at the use method of the block you must check if the block above or below is a furnace whit the same facing // ########## ########## ########## ########## // On right click @Override public InteractionResult use(BlockState blkstate, Level warudo, BlockPos pos, Player pe, InteractionHand hand, BlockHitResult hit) { //System.out.println("use()"); ItemStack helditem = pe.getItemInHand(hand); int age = blkstate.getValue(AGE); if( !warudo.isClientSide() ){ BlockState blockabove = warudo.getBlockState( pos.above() ); BlockState blockbelow = warudo.getBlockState( pos.below() ); //stuff //stuff //stuff1 point
-
1 point
-
tysm, ur a life saver,, its weird immersive portals became the issue because I play-tested the mod pack once and everything ran, it only started crashing when I tried playing it a second time.1 point
-
Hello, I hope you doing well. I didn't know I still could do it. And it worked. Thanks a lot. Have a wonderfull day!1 point
-
> But you have to use a forked repo of forge and gradle to do that. Thats the toolchain im referring to. You need to make changes to make the toolchain working in the modern world. some people have hacked the old versions of the tools to function. But the better option is to build the tools to use the old version's data. Specifically updating https://github.com/MinecraftForge/ForgeGradle to be better.1 point
-
1 point
-
Your drivers are in a broken state, follow the guide in the FAQ: https://forums.minecraftforge.net/topic/125488-rules-and-frequently-asked-questions-faq/#:~:text=How do I update my drivers%3F1 point
-
Solved by first importing it into the IDE, then running genEclipseRuns1 point
-
As part of stricter anti-spam measures, new posts that have large amounts of content similar to many other posts are automatically hidden. You'll know this because your entire post will be highlighted in red and only visible to you. Unfortunately, this means dumping crash reports or logs directly in your support thread will trigger it. To avoid this, please read the FAQ before posting and provide a link to your log or crash report on an external paste site (such as pastebin) instead. If your thread is automatically hidden, you'll need to create a new one or wait for a moderator to manually approve it and remove the log from your post. When creating a new thread, make sure you only provide a link to an external paste site and do not dump logs directly in your post again as doing so could risk your account getting banned.1 point
-
In more recent versions of the API, your code may look look this: String message = "You picked up this item!"; ITextComponent msg = new StringTextComponent(message); PlayerEntity player = Minecraft.getInstance().player; player.sendMessage(msg, player.getUUID()); It kinda seems a little worse to me to have to put in the UUID like that even you you have access to the player, but I'm sure they had a good reason to change it up.1 point
-
you can use ItemStack#getItem to get the Item, then check if the Item an instance of ArmorItem. then use ArmorItem#getDefense to get the Armor value1 point
-
I am glad you solved the issue by yourself. You may want to share your solution, so other people seeing this post in the future may find it helpful1 point
-
I know this topic is a bit old, but I just had the same issue and a Google search points here. If your packet is working correctly, and its just the warning in the log, you've likely made the same mistake as me. Inside the "messageConsumer" you provided when registering your packet, you need to set the packet handled flag to true. "context.get().setPacketHandled(true);" If it isn't set to true, NetworkHooks.onCustomPayload will return false, and ClientPlayNetHandler.handleCustomPayload will post the warning1 point