Our latest beta build can be found on HockeyApp.
Join our Discord channel here to meet other players and the dev team.
Since the game is not yet released, there are some steps that are required to get the game running on your device. At this time, we can only run on Windows 10 and later PCs. We can occasionally build .EXE files for older versions, but that is not what we want to test. If you do not have access to Window 10, you can grab an evaluation VM from Microsoft directly: here.
The process to run our game app is called Side-loading and it requires some extra steps the first time you do it. Here are the steps you need to follow.
Installing the game
- Grab the latest build from HockeyApp.
- Extract to a local folder on you device.
- Right-click on “Add-AppDevPackage.ps1” and choose “Run with PowerShell” (See troubleshooting below if you don’t see that option)
- If you haven’t set the PS execution policy previously, it will prompt you to change it. Go ahead and accept the change.
If this is your first time to side-load, you may be prompted to acquire a dev license. This is free and all you need to do is provide your credentials and follow the link that says “settings for developers” which should take you to the “Updates & Security Settings page” at the section titled “For Developers” where you should set “Use Developer Settings” to “Developer Mode”.
- If you have a previous version, it may sometimes be necessary to uninstall it first before installing a private build.
- Once installed you should find the app on your start menu ready to run.
Starting the game
To start the game on Window 8.1 or Windows 10, simply click the tile from the Start menu.
When the game starts, you need to select a server to connect to. If you are part of the development team or are testing something that is being worked on choose the “Thunder Power” server. This is the most up to date (and buggiest) server you can connect to. It will go down frequently without warning. If you want to test the latest stable version, then connect to the “Production” server. Finally, if you are testing a new feature that didn’t make it to production yet then choose “Staging.” In most cases, if you are doing private testing, then Staging would be your best bet.
Once you’re authenticated, you should be able to login to the lobby, invite players to a new battle and start playing. Note that you can only start a battle if you have at least one opponent. If you want to find someone to join you for a test session, you can grab interested testers from our Discord channel or Facebook group.
Sending game logs
To help us find bugs and fix them, you may need to send us log files. The easiest way to do this is by clicking on the feedback icon in the game and selecting to include logs. Alternatively you can send it manually by following these steps:
- If you are running the Windows standalone version (i.e. not the app), you’ll also need to create an empty folder called “C:\Temp” on the root of your C: drive where logs will be saved.
- Sending your logs:
The game will save a log file that you can send directly to the devs after a test session.
Open this path in file explorer “%AppData%\..\Local\Packages\” and look for the ForgottenMines.WartotheCore package then navigate to LocalState and locate the log file(s). Note: If you’re running the stand alone version, then the log files will be in C:\Temp instead.
If you don’t see a “Run with PowerShell option” in the context menu, you might have changed the file associations or don’t have PS installed (in the latter case just install it by going to “Programs and Featues” and selecging “Turn Windows features on or off” and enabling PowerShell).
If PowerShell is installed and you’re still not getting the option, then run PowerShell ISE as administrator (this is important if it’s the first time). If this is the first time, then type “Set-ExecutionPolicy RemoteSigned” in the lower (blue) part of the editor and press enter then accept the prompt. After that you can open the Add-AppDevPackage.ps1 file (from File menu->Open) then hit the green “Play” arrow in the toolbar to start the execution.
If PowerShell fails to acquire developer license. Ensure that you have enabled developer mode as per the instructions above. You can also try running this command “Show-WindowsDeveloperLicenseRegistration” in PowerShell.
If you get a PowerShell shell error saying that “running scripts is disabled on this system” then run this command as admin: “Set-ExecutionPolicy RemoteSigned”
If you get an error like “DEPLOYMENT FAILED WITH HRESULT: 0X800B0109, A CERTIFICATE CHAIN PROCESSED, BUT TERMINATED IN A ROOT CERTIFICATE WHICH IS NOT TRUSTED BY THE TRUST PROVIDER” then locate the .cer file in the folder you unzipped and open it. If you get a warning, click open then install the certificate to Local Machine (this will require admin rights). Select “Place all certificates in the following store” and then hit “Browse” then select “Trusted Root Certification Authorities.” and finish the prompts. Once you are done try re-running the ps1 file again.