From 9981360f1ee543ad487185ffddcc6a24f9aa09d2 Mon Sep 17 00:00:00 2001
From: Ori Damari <35385002+repnz@users.noreply.github.com>
Date: Tue, 25 Jun 2019 22:27:06 +0300
Subject: [PATCH] Update README.md

---
 README.md | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 8f2573f..fc321d4 100644
--- a/README.md
+++ b/README.md
@@ -5,6 +5,9 @@
 This project is currently on-going. The purpose of this is to reconstruct the full source code
 of the original windows xp Minesweeper. (sha256: bcff89311d792f6428468e813ac6929a346a979f907071c302f418d128eaaf41)
 
+I finished reconstructing the full minesweeper source:) The only thing that I don't have time to do is to order variables
+in one module.. Looking in the assembly code and variable layout it looks like most of the variables were global variables declared in one source file.
+
 The artifacts of the reverse engineering process:
 
 - Design document explaining the full design and implementation of MineSweeper
@@ -17,10 +20,7 @@ Most of the process is done using static analysis without using a decompiler. I
 
 - Create documentation
 - Test code 
-- Create a remote Minesweeper Hacking Tool (in Rust)
-  - Configure bombs
-  - Configure timer
-  - Remove some constraints
+- Create remote hacking tool
 
 ## Nt 4.0 Leak
 
@@ -33,3 +33,14 @@ been leaked - So we have a peek at the original source back then.
 
 After I finished the project, I compared the source code from my reversing to the leaked source, you can see it's almost identical,
 so yay.
+
+## Minesweeper Game Controller
+
+The purpose of this tool is to allow full control over a remote minesweeper process. Some ideas I had:
+- Create a remote Minesweeper Hacking Tool (in Rust)
+  - Configure bombs
+  - Configure timer
+  - Configure board size beyond the usual limits
+  - Configure game state - end game, win game, lose game
+
+