Frequently Asked Questions - All FAQs
Please select your question category
View all frequently asked questions
View FAQ Tags
Hero Combat Manager is a Java application and is capable of running on any computer and operating system which has Java installed on it.
Hero Combat Manager requires Java 1.6.x or greater installed on the computer that will be running Hero Combat Manager. Hero Combat Manager has been tested extensively using Java 1.6.0_37 and Java 1.7.1 on Windows 7 computers. It has been tested on Macintosh running the current operating system and Java 1.7.1.
Screen resolution of 1280 x 600 is highly recommended.
A current version of Hero Designer is required to use Hero Combat Manager. Hero Combat Manager uses Combat Record files which are exported by Hero Designer.
The core combat rules found in HERO System 5th Edition and HERO System 6th Edition provide role playing gamers a wide variety of options. The 6th Edition is a rule book that is over 700 pages long, with over 100 pages devoted exclusively to combat. The goal of the initial release of Hero Combat Manager is to provide tool which assists the GM in managing the combat for most circumstances.
The following combat rules, which are described in the 6th Edition Rule Book, are not currently modeled in Hero Combat Manager
Please go to this webpage and fill out this form. This will provide me with the information I need to help debug the problem.
Once you have downloaded the installer, simply double-click on the file to run the setup.
If you are installing on a Windows Vista or Windows 7 machine DO NOT install the application in the c:\Program Files directory. This has to do with Windows Vista and Windows 7 User Access Controls.
The very first thing to do is make sure you have a working version of Java on your computer. If you go to this Java Tester website they have provided a number of ways to see if you have Java installed on your computer and that it is working correctly.
The installer that I am using requires a 32 bit version of Java to be installed on your computer. Hero Combat Manager will run with either a 32 bit or 64 bit version.
When you install the program make sure you do not install it in the C:\Program Files or C:\Program Files (x86).
If you are installing on a Mac DO NOT install in the Application folder.
And if you see an error such as:
Exception in thread "main" java.lang.AbstractMethodError: org.apache.xerces.dom.DocumentImpl.setXmlVersion(Ljava/lang/String;)V
at com.izforge.izpack.adaptator.impl.XMLElementImpl.<init>(Unknown Source)
it is likely that your system has a large number of old Java libraries that need to be cleaned out. Read this blog post about the issue http://mymaconsnow.blogspot.com/2010/01/java-problems.html
In order to uninstall Hero Combat Manager, it is necessary to locate the folder (directory) where Hero Combat Manager was installed.
Then double click on the Uninstaller.jar file
And then ...
The current version of Hero Combat Manager provides an option for Multiple attacks on Multiple targets. This implements Multiple Attacks against Multiple Targets as described in the 6e rules.
Hero Combat Manager implements this feature by allowing the GM to use the attack advantage Auto Fire.
Fatal Error trying to load either "HeroCombatManager-5e-XML.hcr" or "HeroCombatManager-6e-XML.hcr" file
Do not load these files into Hero Combat Manager. These files are used by Hero Designer to export a Combat Record.
Refer to the Hero Combat Manager User Manual, specifically the section called "Creating Combat Record".
Usually when this error has occured there is a character or set of characters in the Combat Record File (xml) which can not be read by Hero Combat Manager.
For example, the following text in the Combat Record causes this problem:
<ATTACK>Local Weather Control III (Change Environment) Change Environment (\2614 Temperature Level Adjustment), Varying Effect (heat or cool; +1/4), Area Of Effect (32m Radius; +1) ; Unified Power [END: 3]</ATTACK>
This was caused by
A quick solution is to edit the generated Combat Record file by finding pattern(s) such as "\###" and replacing them with the plain text equivalent. The long term solution is to send the Combat Record that was generated and the HDC files that were used to create the character(s) in the Combat Record using the Feedback Form. By doing this the Export Template can be fixed permanently.
NOTE: The example that has been shown is already fixed.