From a372ff61303e20e142c7f0a7da800e94cdf59bf5 Mon Sep 17 00:00:00 2001 From: Florian Fischer Date: Thu, 10 Apr 2025 15:22:14 -0400 Subject: fix permanent typo in push rules --- rules/en/rules.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rules/en/rules.md b/rules/en/rules.md index e2d4325f..4dbd1c99 100644 --- a/rules/en/rules.md +++ b/rules/en/rules.md @@ -399,9 +399,9 @@ Additional States a **unit** is in are represented by putting appropriate marker * If a **permanent** *pushes* another **permanent** the originating **tile** is the current **tile** of the *pushing* **permanent** * If the **push** is not caused by a **permanent** the **actions** **controller** chooses an originating **tile** * Each **step** must be in a straight line determined by the originating **tile** and the current **tile** -* If a **permenent** would be *pushed* onto a *not free* **tile** it is not *pushed* further - * A **unit** colliding in this way is dealt 1 **damage** by the other **permenent** -* If a **permenent** would be *pushed* onto a *free* but not *available* **tile** destroy the **permanent** +* If a **permanent** would be *pushed* onto a *not free* **tile** it is not *pushed* further + * A **unit** colliding in this way is dealt 1 **damage** by the other **permanent** +* If a **permanent** would be *pushed* onto a *free* but not *available* **tile** destroy the **permanent** * For example if a not *swimming* **permanent** is pushed onto **deep water** is is destroyed or vice versa # Combat -- cgit v1.2.3