Crash Report - Quest Mode Start Up

[maglomanic]

Description: When I start up Forge this crash report pops up saying to post this on the forum. I've come to the conclusion is my quest that causes the bug because I put the quest in my recycle bin and then forge started working. I put it back in, crash back. The last thing I did on my quest mode was that I got the zeppelin. Anything I should do besides permanently deleting my quest?

NullPointerException | Open

Code: Select all

Forge Version:    1.4.1-r22075
Operating System: Windows Vista 6.0 x86
Java Version:     1.7.0_21 Oracle Corporation

java.lang.NullPointerException
   at forge.quest.QuestEventDifficulty.fromString(QuestEventDifficulty.java:25)
   at forge.quest.io.QuestDuelReader.read(QuestDuelReader.java:33)
   at forge.quest.io.QuestDuelReader.read(QuestDuelReader.java:1)
   at forge.util.storage.StorageReaderFolder.readAll(StorageReaderFolder.java:99)
   at forge.util.storage.StorageView.<init>(StorageView.java:51)
   at forge.quest.QuestEventDuelManager.<init>(QuestEventDuelManager.java:52)
   at forge.quest.QuestController.resetDuelsManager(QuestController.java:384)
   at forge.quest.QuestController.load(QuestController.java:198)
   at forge.gui.home.quest.CSubmenuQuestData.changeQuest(CSubmenuQuestData.java:274)
   at forge.gui.home.quest.CSubmenuQuestData.access$2(CSubmenuQuestData.java:273)
   at forge.gui.home.quest.CSubmenuQuestData$1.run(CSubmenuQuestData.java:51)
   at forge.gui.home.quest.QuestFileLister.selectHandler(QuestFileLister.java:292)
   at forge.gui.home.quest.QuestFileLister.access$9(QuestFileLister.java:285)
   at forge.gui.home.quest.QuestFileLister$RowPanel$1.mousePressed(QuestFileLister.java:218)
   at java.awt.Component.processMouseEvent(Unknown Source)
   at javax.swing.JComponent.processMouseEvent(Unknown Source)
   at java.awt.Component.processEvent(Unknown Source)
   at java.awt.Container.processEvent(Unknown Source)
   at java.awt.Component.dispatchEventImpl(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Window.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
   at java.awt.EventQueue.access$200(Unknown Source)
   at java.awt.EventQueue$3.run(Unknown Source)
   at java.awt.EventQueue$3.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
   at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
   at java.awt.EventQueue$4.run(Unknown Source)
   at java.awt.EventQueue$4.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
   at java.awt.EventQueue.dispatchEvent(Unknown Source)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.run(Unknown Source)


[Max mtg]

This is related to some custom Quest events you are using

[Chris H.]

- Adding additional opponent decks to your /res/quest/duels/ directory -
Some people are adding additional opponent decks to their /res/quest/duels/ directory in an attempt to increase the number of opponents they will face while playing a quest.

The decks located in your /res/quest/duels/ directory are text files that have a file extension of ".dck" rather than the file extension ".txt". These deck files can be loaded into a basic text editor. You can view the contents of the deck files this way.

There is a metadata line for the deck's difficulty setting. Normal decks do not contain this metadata line for the deck's difficulty setting. Starting with Forge version 1.4.3 any deck file that does not include the deck's difficulty setting will be automatically assigned a value of "medium".

You can add a line for the deck's difficulty setting using a text editor and then saving the deck file. Currently, Forge will recognize the following settings:

Difficulty=easy
Difficulty=medium
Difficulty=hard
Difficulty=very hard

At the start of a new quest you will only face opponent decks that have an easy difficulty setting. After you have won a number of matches you will then face the opponent decks that have a medium difficulty setting. After you have won an additional number of matches you will then face the opponent decks that have a hard difficulty setting. Opponent decks that have a very hard difficulty setting may occassionally appear as a possible opponent instead of a opponent deck that has a hard difficulty setting.

[Max mtg]

BTW, I have patched code to assign medium difficulty by default.