Update README.

ko4life-net · May 19, 2020 · 242dbf4 · 242dbf4
1 parent 8fe6408
commit 242dbf4
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 4 deletions.
diff --git a/README.md b/README.md
@@ -1,20 +1,20 @@
 # Knight Online Table Crypto Editor
 
-This tool will allow targeting any version KnightOnLine.exe and change/update continuously their encryption keys. If you are looking into cheats, you're probably in the wrong place, as this tool is meant to be used for people that are into KO development.
+This tool will allow targeting any version of KnightOnLine executables and change/update continuously their encryption keys. If you are looking into cheats, you are probably in the wrong place, as this tool is meant to be used for people that are into KO development.
 
 Loading the target executable into the tool will parse all the bytes in the binary that have similar pattern for the encryption algorithm, so when it comes to patching, it knows exactly the right offsets to be patched.
 
 For more information, please visit [ko4life.net](https://www.ko4life.net/).
 
 ### Getting Started
 
-You can decide whether you want to build this project from source or download the binary from the Releases [here](https://github.com/ko4life-net/KO-TBLCryptoEditor/releases).
+You can decide whether you want to build this project from source or download the binary from the [releases here](https://github.com/ko4life-net/KO-TBLCryptoEditor/releases).
 
-It is recommended that the target exe you load into this tool, will be in the root directory where the client is, so it would automatically detect the Data folder where the tbls are and update their encryption to match with the new keys as well.
+It is recommended that the target exe you load into this tool, will be in the root directory where the client is, so it would automatically detect the Data folder where the tbls are and update their encryption to match with the new keys as well, otherwise the file dialog will ask you to select the right path.
 
 Note that if you cannot update Key2, it is because the parser detected that the compiler inlined some of the functions, which made the compiler generate multiple instructions to create the second key dynamically. Therefore, it would only be enabled for executables that do not have inlined functions.
 
-After generating new random keys and clicking the `Update Client Encryption`, make sure the next step you do, is update your TBLs as well by clicking `Update Data Encryption`.
+After generating new random keys, click the `Update Client Encryption` button to apply the new keys into the executeable and then you also to want make sure you update your TBLs as well by clicking `Update Data Encryption`.
 
 ### Preview
 
@@ -28,6 +28,10 @@ Also note that it detects the encryption algorithm used for the tbls:
 
 ![](/media/view_offsets_window2.png)
 
+After patching, It is recommeneded to save the report seen in the previous pictures, or you could also save the log file generated that has more technical details:
+
+![](/media/logs.png)
+
 ## Contributing
 
 Pull-Requests are greatly appreciated should you like to contribute to the project. 

diff --git a/media/logs.png b/media/logs.png
diff --git a/media/main_window.png b/media/main_window.png
diff --git a/media/view_offsets_window.png b/media/view_offsets_window.png
diff --git a/media/view_offsets_window2.png b/media/view_offsets_window2.png