User Tools

Site Tools


boards:knight_s_tour:knight_s_tour

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
boards:knight_s_tour:knight_s_tour [2014/10/02 23:17]
Ozyman
boards:knight_s_tour:knight_s_tour [2017/04/18 23:49] (current)
Ozyman
Line 3: Line 3:
 {{:boards:knight_s_tour:screenshot-2.png|}} {{:boards:knight_s_tour:screenshot-2.png|}}
  
-The same basic rules can be applied to boards of various shapes, sizes and layouts, so rules are given in a general form.+The same basic rules can be applied to boards of various shapes, sizes and layouts, so rules are given in a general form.  Specific differences between scenarios are outlined in the Scenarios section below.
  
 You play by jumping from knight to knight.  Some squares are 'dead' on the board, and cannot be occupied. You play by jumping from knight to knight.  Some squares are 'dead' on the board, and cannot be occupied.
  
 +**If you like the concept, but don't like any of the scenarios, you can design your own.  Take a look at this thread:**
 +http://www.wargear.net/forum/showthread/4165/Create_your_own_Knights_Tour_scenario
  
 ====== Borders ====== ====== Borders ======
Line 13: Line 15:
  
 {{:boards:knight_s_tour:knights_moves.jpg|The knight can attack any of the squares with an 'X' in it (assuming it is a valid move) }} {{:boards:knight_s_tour:knights_moves.jpg|The knight can attack any of the squares with an 'X' in it (assuming it is a valid move) }}
- 
-You do not need to leave any units behind, but if you abandon a square it will revert to neutral.  This also provides great freedom traveling around the board in the attack phase. 
- 
-The # of attacks allowed is the sqrt(length*width) rounded up. 
  
  
Line 23: Line 21:
 You may fortify between any two connected territories.  You may return to attack from fortify.   You may fortify between any two connected territories.  You may return to attack from fortify.  
  
-The # of fortifications allowed is the sqrt(sqrt(length*width)) rounded up.  +The # of fortifications allowed is the sqrt(size of the board) rounded up (i.e. width or height for squares).  
  
 ====== Continents ====== ====== Continents ======
Line 36: Line 34:
  
 ====== Scenarios ====== ====== Scenarios ======
-===8x8 Random=== +===8x8 Random - 2 players===
-  * 8 Attacks+
   * 3 Fortifies   * 3 Fortifies
   * No extra vision borders   * No extra vision borders
-  * Cards: 8,10,12,14,...+  * Cards: 4,8,10,12,14,... 
 + 
 +===8x8 Random - 3 player=== 
 +  * 3 Fortifies 
 +  * No extra vision borders 
 +  * Cards: 4,5,6,7,8,... 
  
-===12x12 Random=== 
-  * 12 Attacks 
-  * 4 Fortifies 
-  * Vision borders for one extra hop 
-  * Cards: 8,9,10,11,... 
  
-===Big Islands=== +===Stripes===
-  * 15 attacks+
   * 4 Fortifies   * 4 Fortifies
   * Vision Borders for one extra hop   * Vision Borders for one extra hop
Line 66: Line 63:
 ====== Board Creation ====== ====== Board Creation ======
  
-This board (territories, borders, continents, images, etc.) was programmatically generated in python.  The board size and number of squares occupied by knights is set. Then the placement is done randomly with heuristics.  Finally XML and PNG files are created.  ([[:boards:knight_s_tour:python|More details]])+This board (territories, borders, continents, images, etc.) was programmatically generated in python.  The board size and number of squares occupied by knights is set. Then the placement is done randomly with heuristics or deterministically.  Finally XML and PNG files are created.  ([[:boards:knight_s_tour:python|More details]])
  
  
boards/knight_s_tour/knight_s_tour.1412306270.txt.gz · Last modified: 2014/10/02 23:17 by Ozyman