diff --git a/Predicting-the-Enemy-in-Tower-Rush.md b/Predicting-the-Enemy-in-Tower-Rush.md
new file mode 100644
index 0000000..3098264
--- /dev/null
+++ b/Predicting-the-Enemy-in-Tower-Rush.md
@@ -0,0 +1,13 @@
+
Because of the inherent server delay and the deployment time of units, playing purely 'reactively' means your defense will always be a fraction of a second too late.
+
This article will teach you how to analyze the board state, track rotation, and cast perfect predictive spells.
+Reading the Opponent
+
90% of players will place their defensive building on the exact same tile every single time they defend that specific push.
+
When you launch your final Hog Rider, you don't wait to see the Cannon; you instantly cast a predictive Fireball on the exact tile they have used all game.
+Drop your win condition and instantly roll a log to clear the swarm you know is coming.Count their rotation.If you predict a Skeleton Army and they play a Mini P.E.K.K. If you have any type of questions concerning where and the best ways to utilize [tower rush](https://gitlab.projcont.red-m.net/kristofercleve/tower-rush7188/-/issues/2), you could contact us at our webpage. A instead, you just wasted your spell completely.
+Knowing When They Will Strike
+
This requires constant, flawless tracking of their elixir bar in your head.
+
Furthermore, you can predict 'desperation' plays based on their elixir deficit.
+The TriggerYour Predictive ResponseOpponent plays a Golem in the backPredict that they will dump all their elixir into supporting it; aggressively push the opposite lane instantlyOpponent uses their only Log on your PrincessPredict that they are defenseless against swarms; instantly throw your Goblin Barrel at their tower
+The Pinnacle of Skill
+
You manipulated them into playing exactly what you wanted, exactly where you wanted it.
+
Observe the patterns, trust your math, and strike before they even know they are vulnerable.
\ No newline at end of file