Basic featureset planning

[kiwidoggie]

Initial Planning

Foreward

Attention all @AnvilOnline/developers and @AnvilOnline/web-developers we will have to lay out every minor detail of what we want in the game client. The client should be built to the highest quality and allow for maximum ease of installing and running. The user shouldn't have any crashes, unexplained glitches other than ones that we have already acknowledged. Bugs slip through, but we are hoping that our @AnvilOnline/testers will catch many bugs, and various things that just don't feel "quite right".

Initial user experiance

So far, we have a very basic base, this will allow us to provide the user with a 1-click solution. They just download the launcher/updater and it will download Anvil for them. The launcher does not make any modification to ANY of the game files because we want the user to be able to play on 4game's servers, or ours. The user should be able to click and run the game, no if's and's or but's about it.

Feel free just to tack on any features that should be included below, we will sort them, order by priority or if we are not tackling an issue's scope and add them to the various projects.

[camden-smallwood-zz]

Here are a few quick things I can think of for the launcher/updater:

1. Allow the user to specify the root directory of the game files. It'd be nice to not require the launcher/updater to reside in the same directory as the game.
2. The launcher/updater should be able to keep track of individual modifications. Assuming the game modification code is going to be part of the core C++, allow the launcher/updater to hook into those functions or send a message to the game to load specified modifications at startup.
3. If it's going to be Halo: Online specific and we eventually get a proper editor in development, it would be nice to incorporate it with the launcher/updater in some way.

[kiwidoggie]

1. The launcher already supports launching from any directory, as you can set the bin path, module path, and executable path in the settings.
2. This should be planned to be implemented asap once we have the modifications system finalized.
3. This.