1. Unzip the hcm-package.zip into a temporary directory
2. You should have two files:

• ReadMe.txt - This file
• hcminstaller-#.##.zip - This zip file contains a version of Hero Combat Manager. The version number is based on #.## in the file name.

1. Unzip the hcminstaller-#.##.zip so that the HeroCombatManager folder (directory) is unzipped in a folder (directory) to which you have full rights. For Windows systems, I recommend installing it into a C: Applications folder that you create. I can't make similar recommendations for Mac or Linux systems because I don't own those systems.
2. Once unzipped, the folder HeroCombatManager has the following items:

• export folder - This folder contains the custom Hero Designer combat record export files needed to export characters from Hero Designer to be used by Hero Combat Manager.
• hcm.jar - This is the actual Hero Combat Manager Java program. Double-clicking the jar file does not work anymore.
  • hcm.bat - If you have Windows PC, use this is the batch file to start hcm.jar.
  • hcm.sh - If you are running a MAC or Linux Operating System, use this shell file to start hcm.jar. You will also have to change the permissions of the shell script, by using chmod u+x {/path/to/file.sh} or chmod 755 {/path/to/file.sh}. This has been tested on a Linux Operating System. It has not been tested on a MAC.
• HCM_UserManual.pdf - This is the user manual
• HeroCombatManager.gif - part of the icon that shows up when Hero Combat Manager is running
• HeroCombatManager.ico - The desktop icon for Hero Combat Manager
• ReleaseNotes-#.##.txt - A list of bug fixes and new features in this release
• You will need to manually create a short cut to your desktop. If you don't know how to do this use your favorite search engine to look it up on the Internet.

NOTE:

Java 21 or higher is required. You can't use the version found on java.com. Oracle has changed its licensing process. I recommend downloading the current JDK from https://www.openlogic.com/openjdk-downloads . Select the following:
JAVA VERSION: 21.0.x or higher
OPERATING SYSTEM: Select your operating system
ARCHITECTURE: 64-bit
JAVA PACKAGE: JDK
FILE TYPE:

• Windows Systems: Pick .MSI, the standard installer for Windows applications.
• Linux: The flavor of your Linux distribution will determine which installer types you should pick.
• macOS: I am guessing you want .pkg.  I don't own a Mac so I don't know.

Again, using the JRE found at java.com will not work. However, downloading and installing the JDK (version 21.0. x or higher) will work on Windows, macOS, and Linux systems.    

Why has this changed?

Here is some technical background (as best as I understand it) concerning Java, specifically JREs and JDKs.

JRE = Java Runtime Environment: "runs on top of a computer’s operating system software and provides the class libraries and other resources a Java program needs."  In the past, Oracle would provide up-to-date JRE that stayed in sync with the latest JDK (see below).  Now, Oracle expects developers to bundle all the libraries they need into their Java application or have users download the version of the JDK on which the Java application was built.  The current JRE at java.com is version 8.  The current JDK is version 22.  That is a big gap.

JDK = Java Developer Kit: "tools for developing Java applications. ... Every JDK always includes a compatible JRE because running a Java program is part of developing a Java program." There is a way to bundle what is needed from a specific version of the JDK into a Java application. However, after over a month of trying to figure out how to do that with the Eclipse IDE (integrated development environment), I went with this approach.