Forge Release 07/19/2021 ver 1.6.43
by mtgrares
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
Re: Forge Release 07/19/2021 ver 1.6.43
by LoganDungeon » 05 Aug 2021, 16:51
I get the following error when trying to start this version (or the snapshot, same thing happens):
I played a snapshot version a few months back, which when i start it right now, produces the same error.
So it is probably my java version that is somehow not viable anymore.
I have a Windows 10 System with the following Java version:
- Code: Select all
java.lang.ExceptionInInitializerError
at com.thoughtworks.xstream.XStream.setupConverters(XStream.java:832)
at com.thoughtworks.xstream.XStream.<init>(XStream.java:574)
at com.thoughtworks.xstream.XStream.<init>(XStream.java:496)
at com.thoughtworks.xstream.XStream.<init>(XStream.java:465)
at com.thoughtworks.xstream.XStream.<init>(XStream.java:411)
at com.thoughtworks.xstream.XStream.<init>(XStream.java:350)
at forge.util.IgnoringXStream.<init>(IgnoringXStream.java:18)
at forge.gamemodes.quest.bazaar.QuestBazaarManager.load(QuestBazaarManager.java:74)
at forge.gamemodes.quest.bazaar.QuestBazaarManager.getStallNames(QuestBazaarManager.java:202)
at forge.screens.bazaar.VBazaarUI.populateStalls(VBazaarUI.java:44)
at forge.screens.bazaar.CBazaarUI.initBazaar(CBazaarUI.java:26)
at forge.screens.bazaar.VBazaarUI.instantiate(VBazaarUI.java:105)
at forge.view.FView.cacheUIStates(FView.java:553)
at forge.view.FView.initialize(FView.java:150)
at forge.control.FControl$3.run(FControl.java:269)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:316)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field private final java.util.Comparator java.util.TreeMap.comparator accessible: module java.base does not "opens java.util" to unnamed module @3c72f59f
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357)
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:177)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:171)
at com.thoughtworks.xstream.core.util.Fields.locate(Fields.java:40)
at com.thoughtworks.xstream.converters.collections.TreeMapConverter.<clinit>(TreeMapConverter.java:50)
... 28 more
I played a snapshot version a few months back, which when i start it right now, produces the same error.
So it is probably my java version that is somehow not viable anymore.
I have a Windows 10 System with the following Java version:
- Code: Select all
java version "16.0.1" 2021-04-20
Java(TM) SE Runtime Environment (build 16.0.1+9-24)
Java HotSpot(TM) 64-Bit Server VM (build 16.0.1+9-24, mixed mode, sharing)
- LoganDungeon
- Posts: 1
- Joined: 05 Aug 2021, 16:21
- Has thanked: 0 time
- Been thanked: 0 time
Re: Forge Release 07/19/2021 ver 1.6.43
by Fregnor » 06 Aug 2021, 19:14
@ LoganDungeon
A quick and dirty way to fix your problem, after a fashion, would be to delete, move, or rename-to-disable the new bad version of Forge that will not work on your system. This would prevent the computer from finding and using the bad files. Then you could completely reinstall the old version of Forge that worked on your system. (If you just try to go play the old version that is still on your system, it will have been corrupted and altered by the new versions partially installed on top of it. I have experienced this before with a different bug in a new version.)
Reinstallation of an old version known to work is not the ideal solution, because the newest cards would not be available, but it could get you playing again until the bugs are fixed in an upcoming version.
A quick and dirty way to fix your problem, after a fashion, would be to delete, move, or rename-to-disable the new bad version of Forge that will not work on your system. This would prevent the computer from finding and using the bad files. Then you could completely reinstall the old version of Forge that worked on your system. (If you just try to go play the old version that is still on your system, it will have been corrupted and altered by the new versions partially installed on top of it. I have experienced this before with a different bug in a new version.)
Reinstallation of an old version known to work is not the ideal solution, because the newest cards would not be available, but it could get you playing again until the bugs are fixed in an upcoming version.
17 posts
• Page 2 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 20 guests