diff --git a/Predicting-the-Enemy-in-Tower-Rush.md b/Predicting-the-Enemy-in-Tower-Rush.md
new file mode 100644
index 0000000..7d3b533
--- /dev/null
+++ b/Predicting-the-Enemy-in-Tower-Rush.md
@@ -0,0 +1,13 @@
+
In the chaotic, hyper-fast environment of an arena battler, relying entirely on your physical reaction time is a guaranteed path to mediocrity.
+
Predictive gameplay looks like pure magic to a casual observer; it appears as though the player is reading the opponent's mind and dropping spells on empty tiles.
+Exploiting Habits
+
90% of players will place their defensive building on the exact same tile every single time they defend that specific push.
+
Once you identify this habit during the first two minutes of the match, you can exploit it ruthlessly in the final minute.
+The 'Predictive Log' is the most common execution.Watch their card cycle.If you predict a Skeleton Army and they play a Mini P.E.K. If you enjoyed this article and you would certainly like to obtain additional info concerning [tower rush](https://git.coastit.co.za/hildegardehart) kindly visit the web page. K.A instead, you just wasted your spell completely.
+Tracking Elixir and Predicting Aggression
+
This requires constant, flawless tracking of their elixir bar in your head.
+
If they just over-committed 9 elixir on a failed push, you can predict that they will be completely unable to defend a sudden Bridge Spam attack in the opposite lane.
+What They DoWhat You DoOpponent 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 didn't just beat their cards; you beat their mind.
+
Start small; try predicting simple swarm placements with cheap spells before attempting predictive heavy spells.
\ No newline at end of file