Collectible Card Game Headquarters

Actually, I can confirm, that for me MobileForgeLauncher.jar is not working as well (and I am on Windows 10 too).
It just shows the first window, where display settings can be changed, but it is not launching Forge afterwards.
So the only possibility to run it is through forge-mobile-1.6.21.jar (in any case, there were no problems observed so far running it that way, so it is not a major issue).

Maybe you can post your log file and see if it's the same error as mine (for the developers of Forge)

[deleted]

UPDATE (03/10/19): Forge Mobile Backport v1.6.22.001 has been released. It's a release based on Forge for Android v1.6.22.001 and desktop Forge v1.6.22. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

For everyone who is currently experiencing issues with launching the game through the launcher on Windows 10 (possibly on other versions too?) - unfortunately, I can't reproduce this issue, and I don't really have a Windows machine to test it on, so it's difficult for me to fix. I haven't yet pushed the source code for the launcher upstream (I'm yet to figure out how to do it and also where to best put it), so for everyone interested, here's the source code attached for the time being. Testing and suggestions for fixes on Windows (10?) are welcome.

- Agetian

UPDATE (04/09/19): Forge Mobile Backport v1.6.23.001 has been released. It's a release based on Forge for Android v1.6.23.001 and desktop Forge v1.6.23. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian

UPDATE (05/02/19): Forge Mobile Backport v1.6.24.001 has been released. It's a release based on Forge for Android v1.6.24.001 and desktop Forge v1.6.24. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian

UPDATE (05/20/19): Forge Mobile Backport v1.6.25.001 has been released. It's a release based on Forge for Android v1.6.25.001 and desktop Forge v1.6.25. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian

UPDATE ON THE REPORTED WINDOWS 10 ISSUE (POSSIBLE FIX):
Some people have reported being unable to start Forge through the launcher on Windows 10. I worked with a friend of mine to narrow this problem down and fix it, and we came to a conclusion that this most likely has to do with the fact that most automated online installs of Java on Windows are 32-bit, not 64-bit. While mobile Forge backport can work on 32-bit systems (as proven by the fact that running the main .jar directly, bypassing the launcher, works), it can't allocate the necessary amount of memory and may be more prone to out of memory crashes, especially in longer duels with considerable amount of cards and tokens.

I have updated the launcher to warn the user if they're running mobile Forge backport on a 32-bit JVM. The launcher will then proceed to launching the game with a smaller memory footprint, which should work (however, as I said, this is suboptimal and may lead to out of memory crashes to desktop). There is a download link below. The source code for this version of the mobile Forge launcher is also provided for everyone interested.

If you receive a warning about using 32-bit Java, you are encouraged to update to a 64-bit Java installation if at all possible. The default installer "Online Windows Installer" picks 32 bit, possibly in case someone has a 32 bit browser (which wouldn't work with a 64 bit JVM). You have to pick the little link on the side to see all downloads and then pick Windows x64.

If you're unable or unwilling to install 64-bit Java on your Windows machine for any reason, you may try to play the game as is, but please keep in mind that in this case we can't provide any support if you receive an out of memory crash.

Please let me know if this fixes the issue for you in case you were experiencing it.

- Agetian

UPDATE (06/13/19): Forge Mobile Backport v1.6.26.001 has been released. It's a release based on Forge for Android v1.6.26.001 and desktop Forge v1.6.26. It also comes with the updated mobile Forge launcher v1.0 which should hopefully resolve issues for people running Windows (check the post above). Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian

UPDATE (07/08/19): Forge Mobile Backport v1.6.27.001 has been released. It's a release based on Forge for Android v1.6.27.001 and desktop Forge v1.6.27. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian

UPDATE (09/06/19): Forge Mobile Backport v1.6.28.001 has been released. It's a release based on Forge for Android v1.6.28.001 and desktop Forge v1.6.28. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian

UPDATE (09/29/19): Forge Mobile Backport v1.6.29.001 has been released. It's a release based on Forge for Android v1.6.29.001 and desktop Forge v1.6.29. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian

I try to download this new update and it loads all the way as if it's downloaded it, then closes the app and when I reopen it, says I need to still download it.

My old request came through in a big way! Thanks for doing this for me! Works on Windows 10 tablet with 32-bit java. The internet play crashed though on startup.

UPDATE (11/11/19): Forge Mobile Backport v1.6.30.001 has been released. It's a release based on Forge for Android v1.6.30.001 and desktop Forge v1.6.30. Enjoy!

IMPORTANT UPGRADE REMINDER: When upgrading from the previous version of the mobile backport, please remember that it's always best to start with a fresh empty folder, unpack the new version there, then move the profile folder from your previous version to the new folder. This will help avoid mixing executables and resources from the old and the new versions of the game.

- Agetian