A best solution to run HMCL (Hello Minecraft! Launcher) on flash drive
English 简体中文 Pages Github
Latest version：v1.6 (Theoretically, the full version of HMCL is supported)
Hello HMCL! Launcher（below referred to as HHML）is a command script (support Windows only now), look from the name, this is a launcher written for the launcher.
This script use to resolve the HMCL launcher (Hello Minecraft! Launcher) cannot search Java in current directory and automatically select Java in custom path. Though this script, you will never need to install Java to system, or add custom Java path manually again, only need to download a Java archive and unzip to launcher directory without installation.
in addition, the HHML can also resolve HMCL put some related config file and runtime to user directory in system, resulting in the need for reconfiguration on another system (for example, need accept the EULA again). The script will restore the downloaded runtime and global to user directory in system and back it up when exiting.
- Download a Java archive (not the installer, can be OpenJDK) of the required version of the MC version you are playing and unzip it, and download latest version of HMCL in JAR format on the HMCL official websideor the official GitHub releases, an download Latest HHML script from here：
Windows Chinese simplified editon: HHML-SC-GB2312.bat
Windows English editon: HHML-EN.bat
if you using a non-Chinese simplified Windows or UTF-8 global language support has been enabled, please select the English edition, Otherwise garbled characters will appear, even cause errors! - put the HMCL JAR file and HHML script and unzipped java archive (multiple different versions can be placed, directory structure is not limit) in the same directory (can be on a flash drive or hard disk)
- run the HHML script, the script will secrch all Java archive in current directory automatic and pick the latest Java version to launch HMCL JAR file, soon the interface of HMCL will appear, but sometime also it's download runtimes (JavaFX) automatic, it puts it in the system by default, it is very troublesome to download it again after changing computers. So HHML can back it up to current directory in preparation for restoring to the system on another computer, saving time to download again.
- With the help of HHML script, the HMCL not only can search installed Java in the system automatic, but also can search unzipped Java in current directory automatic. This mains you don't need to manually add a non-installed Java version path to custom path (unlike PCL2, only one custom Java path can be added in HMCL)
- After that, you should launch HMCL via the HHML script instead of opening the JAR file directly. To speed up the game startup, you can enable "Do not check game integrity" option in advanced settings, because the intergrity check before the game launch requires a large amount of data to be copied to the system disk, if the game is on a flash disk, it will take a lot of time to complete this step.
- If need store account data to current directory, please convert the account to portable account in "Account List", or you'll need sign in again on another device.
Create a text file under the same directory as the script and named "customPath.txt". The text content is one Java path per line (relative path can be used, directory name with spaces are also supported), like this:
C:\Users\Administrator\Desktop\jdk\archive\openlogic-openjdk-8u372-b07-windows-64
.\..\directory with space\jdk\jdk-11.0.12
\software\jdk\archive\jdk-17.0.8+7
note: The Java path is not the directory where the Java binary is located, but the directory where the "bin" folder is located, which is equivalent to the JAVA_HOME variable.
create a text file and named "config.txt" or "hhml.properties". and the format is "configuration=parameter", like this:
searchInCustPath=2
backupGlobalConfig=0
#Comments
checkJava=0
use64java=1By default, the log output will be stopped after HMCL launched by script. It make HMCL log not visible.
Configuration name: showHMCLlog
Parameter:
0: Not output HMCL log (still output HHML log during loading)
1: Output HMCL log under the current command line window
Default parameter: 0
Note: runtime here refers to AuthLib-Injector (external login dependencies) and Java FX (graphic interface dependencies), while global config here refers to config.json (user license).
If you want to use HHML script in hard disk, you definitely don't want HHML auto backup/restore/remove the runtime and the globel configuration. They are all located at user directory in system, since it's all on the hard drive, and don't have to change computers, is it still need to backup?
So I provided some option about backup/restore/remove (they all parameter is 1):
Restore runtime
Configuration name: restoreRunTime
Parameter:
0: Never restore
1: Restore AuthLib，restore JavaFX if Java version is 11 or later and HMCL version is 3.3.183 or later
2: Always restore authlib and JavaFX (ignore the Java and HMCL version)
Backup runtime
Configuration name: backupRunTime
Parameter:
0: Never backup
1: backup when "restoreRunTime" is enabled and need download runtime by HMCL.
2: Always backup (even if it has been backed up)
Remove runtime
Configuration name: removeRunTime
Parameter:
0: Never remove
1: Remove if they are both restored
2: Always remove (even if they are not restored)
Restore global config
Configuration name: restoreRunTime
Parameter:
0: Never restore
1: Restore if they are both found in user directory in system
2: Always restore (even if it already exists before launch)
Backup global config
Configuration name: backupRunTime
Parameter:
0: Never backup
1: Will backup automatically if it is not exist before launch
2: Always backup without user confirm (even if it already exists before launch)
Remove global config
Configuration name: removeRunTime
Parameter:
0: Never remove
1: Remove if it already restore
2: Always remove (even if it already exists before launch)
You can set up script search in some range through this configuration, all parameter are follow:
0: Never search in this range
1: Search this range if Java are not found at previous range
2: Always search (even if Java has been found)
Search custom path
Each line of Java path searched in "customPath.txt" under the same directory as the script.
Configuration name: searchInCustPath
Default parameter: 2
Java found in this range will add to temporary environment variable so that HMCL to detect it.
Search current directory
Search Java directory under the same directory as the script.
Configuration name: searchInCD
Default parameter: 2
Java found in this range will add to temporary environment variable so that HMCL to detect it.
Search %PATH% environment variable
Configuration name: searchInSysPath
Default parameter: 1
If you installed Java that can't be detected by HMCL, you can set the parameter of this configuration to 2.
Search JavaSoft registry
Configuration name: searchInSysPath
Default parameter: 1
Note: This is specific registry item of Oricle official Java, so OpenJDK may can't be found in this range.
If you installed Java that can't be detected by HMCL, you can set the parameter of this configuration to 2, Java found in this range will add to temporary environment variable so that HMCL to detect it.
Search list of installed application
Configuration name: searchInInstApp
Default parameter: 1
Note: by default, search Java this range is only because it is not found at previous range, because it need traverse a lot of registry, it is too slow.
If you installed Java that can't be detected by HMCL, you can set the parameter of this configuration to 2, Java found in this range will add to temporary environment variable so that HMCL to detect it.
You can set the Java detection rules with this option:
Detect Java version
Configuration name: checkJava
Default parameter: 2
Parameter:
0: Select last Java in the file order, not check Java version and bitness (Not recommended, you need set bitness through "use64Java" configuration, the Java version will be proposed as 11)
1: Select last Java in the file order, and check its version and bitness
2: detect version and bitness of any founded Java and pick the latest version
Use Java 8 preferred (only valid when parameter of checkJava is 2)
Default parameter: 0
Configuration name: useJava8First
Parameter:
0: pick latest version Java by version order
1: pick Java 8 preferred by version order, pick latest version if its not found
Set Java bitness (only valid when parameter of checkJava is 0)
Configuration name: use64java
No default parameter have
Parameter:
0: 32 Bit Java（X86）
1: 64 Bit Java（X64）
Exclude some versions of Java (only valid when parameter of checkJava is 2)
Configuration name: verBlackList
Usage: enter unwanted version number in the parameter (can be multiple, use comma "," to separated between each version), HMCL will not be launched through the corresponding version.
Default parameter: none
Parameter demo:
verBlackList=1.8.0_272,17.0.1,11.0.2