Added official Battlefield 4 R1 Server Documentation
With the new implemented web API it is now possible to add, remove and edit the connections within the RaptoRCon Server. This server holds all connections and manages the communication to the connected clients.

Completed Issue #11
Beginning of independent Game Infrastructure

With this type of infrastructure in mind, there will be no issues regarding the support of several games having an administration interface. You don't care about the details of the game. It's an abstraction layer on top of the game. The game will only manage it's stuff and administration starts a higher level. It will not be important how the game manages it, but that it can manage it.

Issue #8
Reading multiple Packets Handling of multiple packets in a byte-stream was not handled correctly. The reading operation was only executed on the first packet for multiple times, as long packets transfered were available. The byte-stream is now cut after reading each packet so that all packets delivered are correctly extracted from bytes. By the way, the new version 2 of xUnit.Net is not yet supported by VS Plugin. That's why xUnit 1.9.2 was restored Fixed Issue #15
Renamed Projects and Namespace

With the introduction of the abstract game layer, which should generate an independance of supported games and protocols, the current assemblies and namespaces had to be renamed, so that it is clear, they are game specific.

Issue #8
Fix UI updating problem

The UI was not updating correctly. Updates on the datasource on another thread / task only appeared on an edit within the forms. With the new Context-property in the ViewModelBase which holds the SynchronizationContext, we are now able to post the updates onto the UI-Thread. But that was not all. Some PropertyChanged-Events were missing. They are now sent correctly. UI updates as expected.

Fixed Issue #14
Added official BF4 R6 Server Administration Documents

Issue #17
Basic Game Layer Adapter for Battlefield 4

I created a basic adapter to the game layer for Battlefield 4. Through this adapter it is possible to send commands  and receive events. This Layer has to be introduced into the existing API-Controllers within the server. Afterwards the Controllers a independent from the games they support. The instance of the game is responsible for handling these commands and events.

Issue #8
Loading games implemented

All games supported by RaptoRCon must be available in the "Games"-subdirectory of the server. The IGame interface is the basic interface all game adapters have to implement. MEF is used for inspecting all assemblies within the stated directory for implementations of IGame. The IGamesContext can be used for retrieving the needed game(s).
For external use, the GamesController delivers all needed data.

Issue #8
Bound Game Layer between Client & Server

The Games Layer is now present from client to server. You have to select the game type and with this the logic how to create a RCon Connection.

Fixed Issue #8
Basic SequenceId Handling

Issue #16
Merge pull request #18 from RConDev/development

Merge Issues for v0.2