Merge pull request #29 from proepkes/develop

Readme

Engine/Core/World.cs

@@ -1,5 +1,4 @@
-using System;
-using System.Collections.Generic;
+using System.Collections.Generic;
 using System.Linq;
 using Entitas;
 using Lockstep.Core.Features;
@@ -102,7 +101,7 @@ public void Simulate()
             if (Contexts.gameState.isPredicting)
             {
                 Contexts.gameState.isPredicting = false;
-            }                                                                       
+            }          
 
             Execute();
             Cleanup();

README.md

@@ -4,9 +4,9 @@
 
 Initial commit was targeting the following protocol: https://www.reddit.com/r/Unity3D/comments/aewepu/rts_networking_simulate_on_serverbeat/. It turned out that bad network conditions made the game unplayable. The project has shifted to an architecture you see below. 
 
-Currently the rollback of adding new entities is working (for 2 players). If you spawn entities in both instances the game will result in a synced state no matter how many packets drop or how high the lag is. Clientside prediction makes sure that local commands are executed under any condition.
+Currently the rollback of adding new entities should be stable. If you spawn entities in multiple instances, all simulations will have in a synced state no matter how many packets drop or how high the lag is. Clientside prediction makes sure that local commands are executed under any condition.
 
-Rollback for entity-changes is currently in progress. Using the navigation-feature in combination with rollback will lead to desync or game crashes.
+Rollback for entity-changes (e.g. position-change) is currently in progress. Using the navigation-feature in combination with rollback will lead to desync or game crashes.
 
 ![Overview](/Docs/Overview.svg "Overview")