Frequently Asked Questions - Hero Combat Manager
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 are not modeled directly in Hero Combat Manager.
Abort: If a character decides to abort their next action, it is necessary for the GM and/or player (as applicable) to track that information outside of Hero Combat Manager.
- Minimum Damage from Injuries: The GM can do this manually by using the GM Adjust button to adjust the Stun of the target character. (This is an identified bug in the software which may be corrected in subsequent releases.)
- Optional Effects of Damage: The only optional effects of damage which has been implemented is bleeding. Future releases of Hero Combat Manager will implement the Optional Effects of Damage rules
- Other Damage Effects – Hero Combat Manager does not implement any of the Other Damage Effects rules. The GM can use the GM Adjust button to simulate the “STUNNED – DEAD” and “ONE-HIT WONDERS”
- Penalty Skill Levels – Due to the way Hero Designer stores this information and the lack of support in the export capabilities, it is not possible to export the Penalty Skill Levels into the Combat Record File. A work around for this is to convert Penalty Skill Levels into regular combat skill levels with the appropriate modifiers and names.
The following combat rules, which are described in the 6th Edition Rule Book, are not currently modeled in Hero Combat Manager
- Being Attacked While Taking A Recovery, 6th Edition Rule Book, volume 2, page 130, is not implemented. As a work around the GM Adjust can be used to adjust the results if this situation occurs.
- Multiple Attacks are modeled using the same mechanism as Area of Effect for purposes of applying damage. After the attacking character has determined which target character(s) have been hit, either the player or GM will roll the appropriate damage dice. The damage will be then applied to all of the targets the GM selects. Individual target(s) will have their individual defenses applied against the damage. A GM who needs to follow the 6th Edition rules more accurately can use the GM Attack dialog to handle each individual damage roll.
- Auto Fire is modeled using the same mechanism as Area of Effect for purposes of applying damage. After the attacking character has determined which target character(s) have been hit, either the player or GM will roll the appropriate damage dice. The damage will be then applied to all of the targets the GM selects. Individual target(s) will have their individual defenses applied against the damage. A GM who needs to follow the 6th Edition rules more accurately can use the GM Attack dialog to handle each individual damage roll.
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 experience any problems running the downloaded file, make sure that you are loading the file with Java 6 (or better).
Note: on some systems, an archive utility (WinZip, etc.) may have been set as the default application for JAR files. While JAR files are (in essence) zip archives, they should not be associated with a compression utility such as WinZip. Windows users should right-click on the file and select "Open With...", choosing your Java installation from the resulting menu (typically C:\Program Files\Java\jre1.X.0\bin\javaw.exe).
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.
I recommend installing the program in c:\HeroCombatManager
If you are installing on a Mac DO NOT install in the Application folder.
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.
Do not load these files into Hero Combat Manager. These files are used by Hero Designer to export a Combat Record.
- A link to the Hero Combat Manager FAQ (this set of pages
- A link to the Hero Combat Manager Website so you can submit a error
- Typically the error message associated with trying to open either "HeroCombatManager-5e-XML.hcr" or "HeroCombatManager-6e-XML.hcr" files.
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.