Player Resource Consortium

 

Author Topic: prc cc bombs out  (Read 5412 times)

0 Members and 1 Guest are viewing this topic.

September 24, 2009, 02:12:05 PM

hi,

i'm trying to use the character creator to build a character and it stops when i reach the feats.  if i run it from a dos window, i get the following:

Code: [Select]

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
        at CharacterCreator.FeatMenu.calcSkill(FeatMenu.java:225)
        at CharacterCreator.FeatMenu.CheckFeatRequirements(FeatMenu.java:322)
        at CharacterCreator.FeatMenu.isValidFeat(FeatMenu.java:268)
        at CharacterCreator.FeatMenu.RefreshFeatAvailable(FeatMenu.java:203)
        at CharacterCreator.FeatMenu.<init>(FeatMenu.java:169)
        at CharacterCreator.SkillMenu.OKButtonActionPerformed(SkillMenu.java:827)
        at CharacterCreator.SkillMenu.access$9(SkillMenu.java:813)
        at CharacterCreator.SkillMenu$4.actionPerformed(SkillMenu.java:643)
        at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
        at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
        at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
        at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
        at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
        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.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)


can anyone tell me what this means and how i can work around it?

thanks


September 24, 2009, 04:31:28 PM
Reply #1

Operating System/Java version?


September 25, 2009, 04:32:21 AM
Reply #2

Quote from: Onisuzume

Operating System/Java version?

Windows XP SP2
java v.6 update 16


September 25, 2009, 08:35:03 AM
Reply #3

also which prc version, which haks are you using in settings?

edit: also when running it form the commandline are you running the batch file or the character creator directly?
« Last Edit: September 25, 2009, 08:42:40 AM by fluffyamoeba »


September 25, 2009, 11:24:17 AM
Reply #4

well, the 'about' info tells me it's version 1.6r3, even though the number on the package says 1.7...  ;-)

the haks are custom, based off of cep 2.2.

i've run it both directly from the .exe and also from the command line.  when i run it from the .exe, it just hangs -- there are no error msgs or pop-ups.  when i run it from a dos window with 'java -jar', then i get the output i pasted above.


September 25, 2009, 03:13:49 PM
Reply #5
  • Associate
  • ***
  • Posts: 228
  • Karma: +2/-0
    • View Profile

Quote from: xorbaxian

well, the 'about' info tells me it's version 1.6r3, even though the number on the package says 1.7...  ;-)

the haks are custom, based off of cep 2.2.

i've run it both directly from the .exe and also from the command line.  when i run it from the .exe, it just hangs -- there are no error msgs or pop-ups.  when i run it from a dos window with 'java -jar', then i get the output i pasted above.


I'm far from being an expert, but the custom haks and the presence of CEP content could well be the problem.  The cc is designed to work the standard haks.  In my experience using different haks, particularly having it check CEP haks, does not work.

If I were you, I would test with the standard haks and see if that solves the problem.


September 26, 2009, 07:00:52 PM
Reply #6

yep, it was the haks.  one of the 2da's had some invalid data and that caused the c.c. to blow a fuse.

that being said, it would've been helpful if the c.c. had actually indicated there was an error in a 2da rather than just sorta stopping.  maybe a "wish-list" item for sometime in the future?

anyway, it seems to work now.  thanks for the help, guys.  :)


September 26, 2009, 07:41:31 PM
Reply #7
  • Jr. Associate
  • **
  • Posts: 62
  • Karma: +0/-0
    • View Profile

Well, it kind of did.

Quote
       at CharacterCreator.FeatMenu.calcSkill(FeatMenu.java:225)
        at CharacterCreator.FeatMenu.CheckFeatRequirements(FeatMenu.java:322)

Am I missing my guess or was the invalid data in one of the skill rows for a feat entry?

With that said, it is kind of useless knowledge without a stack dump.


September 28, 2009, 08:46:40 AM
Reply #8

Quote from: xorbaxian

yep, it was the haks.  one of the 2da's had some invalid data and that caused the c.c. to blow a fuse.

that being said, it would've been helpful if the c.c. had actually indicated there was an error in a 2da rather than just sorta stopping.  maybe a "wish-list" item for sometime in the future?

anyway, it seems to work now.  thanks for the help, guys.  :)


That's the least of its issues. Sorting out its response to bad data would be very low priority given it has other bugs, like not actually showing the buttons on some windows for some people. But as no-one has ever shown an interest in rewriting it once they saw the source code, it's unlikely to get fixed.