New Launcher Alpha Tests Hey guys, after a very long time (sorry lol), the new launcher is finally ready for alpha testing. You may be wondering, what is alpha? Does this just mean the new launcher is ready? In short, no. The new launcher is not ready for public consumption, however it is at a point where I feel that people can use it so long as they are willing to help me fix bugs and finish everything. The alpha phase will likely be the longest testing phase. New features and incompatible massive changes are all fair game. We will only move forward to beta when all features are implemented. Beta will be used specifically to eliminate outstanding bugs before our initial release. At that point, the feature set will be locked so that we can just get everything out. So, should you use alpha? The answer to that is simple. If you are competent with computers, willing to employ a few workaround methods, and are fine with a lot of client updates, then yes! Keep in mind that if you do decide to use alpha, you need to be willing to report bugs, as that's the only way we can get them fixed. Alpha Goals During the alpha phase, the launcher will be recieving both feature updates and bug fixes. In addition to this, we will be tuning functionality so that everything is intuitive and clear. There are a few things I would like you guys to pay attention to. UI Design If anything on the UI is confusing or misleading, let us know. We'll examine it and formulate better ways of displaying the information. Java Detection The launcher does not require Java to run, however it is still needed to launch Minecraft. To accomidate, the launcher has a series of Java detection functions built in. If a suitable Java installation is found, we use that to launch the game. If not, the latest version of Java 8 is downloaded directly from oracle and placed into the launcher's data folder. In an effort to reduce disk usage, we want the Java resolution functions to be as accurate as possible in identifying potential Java candidates. If any of the following happen, please report them. You know for a fact that you have a valid x64 installation of Java 8 on your computer, however the launcher has not detected it. OR You have several Java installations on your computer, and the launcher has not detected/chosen the latest version among them. In this case, I will need to ammend the detection code. The launcher has successfully detected an older version of Java 8 and is using it for launch. The launch fails because our mods require a newer version of Java. In this case, I'll bump the minimum version of Java 8. The first issue is the most likely to occur, so keep an eye out for it. Locations which are currently being scanned: Windows I scan the registry for Java entries: \SOFTWARE\JavaSoft\Java Runtime Environment \SOFTWARE\JavaSoft\Java Development Kit If none are found, I scan C:\Program Files\Java JAVA_HOME MacOS /Library/Internet Plug-Ins/JavaAppletPlugin.plugin. /Library/Java/JavaVirtualMachines JAVA_HOME Linux: /usr/lib/jvm JAVA_HOME Performance If anything feels slow or clunky, please let us know. We'll do our best to to resolve the issues. We want this launcher to have a smooth and seamless feel to it. Pitfalls and Usability At this point, the launcher is very usable but not everything may have a UI implemented. As a result, you will have to use console commands or similar workarounds to get some things done. Console The console can be opened by using the keybind CTRL + Shift + i. It should open the following window. As the text says, the console is dark and full of terrors. Do not paste anything there unless you ABSOLUTELY know what it will do. Pasting the wrong thing there could have very bad consequences. The console will be required for a few things during alpha. Settings Management The settings UI has not yet been implemented. As such, you will need to manually edit the settings. There are quite a few ways to do this, I'll go over a few here. You may directly edit the configuration file. This is located in .westeroscraft/config.json. Be mindful not to enter invalid values. You may use built in functions to edit the settings while the launcher is running. You can view every available function on GitHub. As an example, to update the maximum ram to 4 Gigabytes, you would type the fllowing into the console: Code: ConfigManager.setMaxRAM('4G') Once you've updated the values, you need to save the configuration. If you are editing the values directly in the file, simply save the file and restart the launcher. If you are editing the values from the console, type the following when you are done: Code: ConfigManager.save() Account Management Account management is a part of settings, and is therefore not implemented on the UI. To add another account, you need to get back to the login view. Type the following into the console. Code: switchView(VIEWS.landing, VIEWS.login) To log out of an account. As the text implies, place the UUID of the account inside the quotes. Code: AuthManager.removeAccount('ACCOUNT UUID HERE') To switch accounts if you are logged into more than one. Code: setSelectedAccount('ACCOUNT UUID HERE') If you try to join the server and it says invalid session, try restarting your game, type the following. If nothing pops up after a few seconds, you're good to go. If something does pop up, click "Login" and login again. Code: validateSelectedAccount() Installation Notes As this is alpha, we are not yet signing the application. As such, when you try to run it you may get security warnings. As long as you are 100% sure you have the file from the official download link, there should be nothing to worry about. Signing up for Alpha I really want Alpha users to be active on discord, as I always have it open and use it a lot for launcher development. As such, the signup for alpha is on discord. To sign up, send a message to Dan_Prime#2135 (me) on discord showing itent to sign up for alpha. From there, I'll send you the relevant links. You'll also be added to the Launcher Tester role and given access to post in #launcheralpha. Alpha is available. Signup is open.