Launching of Instances

[Dessix]

As of now, launching instances is up for grabs as to how the implementation will occur, and no implementations exist. A solution must be found which allows launching of arbitrary package structures- possibly similar to npm's scripts (npm run/test)- but with the possibility for arguments. As examples, these arguments must allow for specification of an address to which the client must connect upon successful launch, on which ports to launch a server, or from which load balancer a server should accept connections.

[Dessix]

As part of this issue, we must figure out how to actually launch the various versions of Minecraft in particular, preferably without necessitating the existence of a Java-based launch-wrapper. Primarily, focus should be placed on the latest versions created by Mojang or supported by Forge. When Sponge arrives, support should also be added for any special considerations it may require.

[Dessix]

The least-dependent package in the configuration which possesses a "launcher" attribute will specify the launcher as a string. For now, launchers will be hard-coded, but they will be moved to packages eventually. The string for Minecraft's launcher will be Launcher/Minecraft/<Version>. The Launcher/ and <Username>/Launcher/ prefixes will be reserved on the package repository until soft-cored launching is available, and afterward, the <Username>/Launcher/' prefix will become available on a per-user basis. Officially supported launchers will be available at theLauncher/` prefix.