diff --git a/Classes.md b/Classes.md
new file mode 100644
index 0000000..a310875
--- /dev/null
+++ b/Classes.md
@@ -0,0 +1,4 @@
+# Hacker
+# Fighter
+# Tech
+# Cyborg
diff --git a/Entitys.md b/Entitys.md
new file mode 100644
index 0000000..93f7da7
--- /dev/null
+++ b/Entitys.md
@@ -0,0 +1,8 @@
+# Rebuilder
+# Servitor
+# Centery
+# Reclamer
+## Reclamed
+## Walker
+# Cypher
+# R.A.T
diff --git a/SSH Server.md b/SSH Server.md
new file mode 100644
index 0000000..9b46839
--- /dev/null
+++ b/SSH Server.md	
@@ -0,0 +1,35 @@
+# SSH Server
+This is what sends all of the information to the client.
+
+This is just a back bone of Skevity and SkevityCreate.
+
+There are three functions that you need to be aware of. There is `ssh_init`, 
+`ssh_run` and `ssh_stop`. Now for the user to add variables to these functions.
+there is `init_var`, `run_var` and `stop_var`.
+
+# Server Transactions
+So, doing some research on how this. The best concolusion for this is a 
+transactional server. This means that it is more about "playing cards" then 
+then like updating a game for a fps or something.
+
+## Transactions on a packet level
+I was doing some thingking about the transactional system and it's like playing
+cards. As you place a card and it gets checked if the card is possable to play.
+Then if so, then, relay that command to the other clients. And now what dose that
+look like on a packet level. 
+
+```packet
+int id, int action, int argSize, args....
+
+```
+
+So for every entity this is what the packet looks like.
+
+The packet consists of a id, action, argSize, and args. The id is refferanceing
+the **entity** id on the server. *This id is reflected on the clients*. The 
+**action** is is the action id of that entity. This could be a attack command. 
+or just a simple move command. But all the server dose is just prosses these 
+transactions see if they are valid, then, relay the transactions to the other 
+clients.
+
+---