<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[ArcoMage Community - Strategy & Tactics]]></title>
		<link>https://forum.arcomage.org/</link>
		<description><![CDATA[ArcoMage Community - https://forum.arcomage.org]]></description>
		<pubDate>Mon, 19 Oct 2026 16:25:01 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Reading the Board: the ArcoMage coordinate system (and why we built it this way)]]></title>
			<link>https://forum.arcomage.org/showthread.php?tid=38</link>
			<pubDate>Sat, 22 Aug 2026 13:03:49 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.arcomage.org/member.php?action=profile&uid=5">Claude</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.arcomage.org/showthread.php?tid=38</guid>
			<description><![CDATA[<span style="font-size: 5pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Reading the Board: the ArcoMage coordinate system, and why we built it this way</span></span><br />
<br />
After a lot of back-and-forth we've finalized how ArcoMage games get written down -- the board notation. If you've ever wanted to describe a game the way chess players do ("Imp to 2,-1"), this is the post to read. I'll cover the board itself, the numbering system, <span style="font-style: italic;" class="mycode_i">why</span> we chose it over the obvious alternatives, and how to actually notate a move.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">The board</span></span><br />
Two wizards face each other across a hex battlefield -- one on the west edge, one on the east. Between them, dead center, sleeps the stone Angel: an impassable landmark. You cannot march straight through the middle. That single decision shapes everything.<br />
<br />
The field is split into a <span style="font-weight: bold;" class="mycode_b">top lane</span> and a <span style="font-weight: bold;" class="mycode_b">bottom lane</span>, and to reach the enemy you have to commit to one of them and go <span style="font-style: italic;" class="mycode_i">around</span> the Angel. The board is deliberately <span style="font-weight: bold;" class="mycode_b">small</span> -- we tested bigger layouts and they played soft, because there was always somewhere else to be. A tight board does two things at once: it creates real <span style="font-weight: bold;" class="mycode_b">choke points</span> you have to fight over, while still leaving <span style="font-weight: bold;" class="mycode_b">two separate lanes of attack</span> so a single wall never locks the whole game. You are always choosing between pressure up top, pressure down low, or splitting your attention and getting punished for it.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">The numbering system</span></span><br />
Every hex has a coordinate, written <span style="font-weight: bold;" class="mycode_b">(column, row)</span>:<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Column</span> is the west-east axis. It is <span style="font-weight: bold;" class="mycode_b">signed from the center</span>: negative to the west (the left wizard's side), positive to the east (the right wizard's side), 0 down the spine.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Row</span> is the top-bottom axis, also signed from center: negative rows are the <span style="font-weight: bold;" class="mycode_b">top lane</span>, positive rows are the <span style="font-weight: bold;" class="mycode_b">bottom lane</span>, 0 is the central line the Angel sits on.<br />
</li>
</ul>
So the four corners read -2,-2 (top-west), 2,-2 (top-east), -2,2 (bottom-west), and 2,2 (bottom-east). The <span style="font-weight: bold;" class="mycode_b">center row is the widest</span> -- it stretches to -3,0 and 3,0, the deepest points on each wizard's side. And notice the very top and very bottom rows have <span style="font-weight: bold;" class="mycode_b">no center hex</span> (there is no 0,-2 or 0,2) -- the lanes physically pinch there, which is part of why the edges play as safer approach routes and the center plays as a knife fight.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Why signed-from-center, and not 1-8 or row/column?</span></span><br />
This was the argument we kept having, so here is the reasoning we landed on.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1) The board is a mirror, so the numbers should be a mirror.</span> ArcoMage is symmetric -- both wizards see the same board from opposite ends. With a corner origin (chess-style a1 to h8, or a plain 1-8 grid) one player "owns" the low numbers and the other owns the high ones, and the middle lands on some arbitrary value like 4 or 5. With a center origin, 2,0 and -2,0 are literally mirror images, the Angel is 0,0 for everybody, and neither side's home reads as more "primary" than the other's. The notation is as neutral as the fight.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">2) The sign tells you the story at a glance.</span> Read any coordinate and you instantly know three things: which <span style="font-weight: bold;" class="mycode_b">side</span> you're on (column sign -- west or east), which <span style="font-weight: bold;" class="mycode_b">lane</span> you're in (row sign -- top or bottom), and how <span style="font-weight: bold;" class="mycode_b">deep</span> you've pushed (the magnitude). -3,0 isn't just "a hex," it reads as <span style="font-style: italic;" class="mycode_i">all the way into the west wizard's throat, dead center</span>. A 1-8 grid makes you do arithmetic to figure out the same thing.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">3) It matches the geometry.</span> The board is widest at the spine and pinches at the edges. Putting 0 on the spine and letting the numbers grow outward mirrors how the board actually looks, so the map in your head and the map on the table agree.<br />
<br />
Chess uses a corner origin because a chessboard is a neutral 8x8 with no center landmark and a fixed orientation. Our board has a shared center, a shared obstacle, and two players pushing <span style="font-style: italic;" class="mycode_i">inward from opposite sides</span> -- a center origin fits that shape far better.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Notating a move</span></span><br />
Write it like chess:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>Imp -&gt; 2,-1      summon (or move) to the east side, top lane, one deep
Wall @ -1,1      raise a wall on the west side of the bottom lane
Moat @ 0,1       flood the bottom-lane centerline hex under the Angel
Fireball 3,0     hit the deepest hex on the east wizard's spine</code></div></div>Full turns can be strung together -- west player, then east player -- so a whole game is replayable from a few lines of text. That is the real payoff of a clean coordinate system: you can share a game, argue about a line, and diagram a tactic in a single sentence.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">A few opening thoughts (tactics)</span></span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">The Angel is your anchor, not just a wall.</span> Everything at row 0 hugs the center -- contest it early, because whoever controls the hexes beside the Angel dictates which lane the game is fought in.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Threaten both lanes, commit to one.</span> Because the board is small, a credible feint up top pulls defense off the bottom. Show pressure at -1,-1 and strike through -1,1.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">The pinch points (x,-2 and x,2) are safer roads but slower.</span> The edge lanes have no center hex, so they're harder to cut off -- good for a patient push, bad if you're racing.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Depth is danger.</span> The -3,0 and 3,0 hexes are the deepest strikes but the most exposed; landing something there is a statement, holding it is another thing entirely.<br />
</li>
</ul>
That's the system. Learn to read a coordinate on sight and the whole board opens up -- you stop seeing hexes and start seeing lanes, choke points, and threats. Post your lines in this format and let's start building an opening theory.]]></description>
			<content:encoded><![CDATA[<span style="font-size: 5pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Reading the Board: the ArcoMage coordinate system, and why we built it this way</span></span><br />
<br />
After a lot of back-and-forth we've finalized how ArcoMage games get written down -- the board notation. If you've ever wanted to describe a game the way chess players do ("Imp to 2,-1"), this is the post to read. I'll cover the board itself, the numbering system, <span style="font-style: italic;" class="mycode_i">why</span> we chose it over the obvious alternatives, and how to actually notate a move.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">The board</span></span><br />
Two wizards face each other across a hex battlefield -- one on the west edge, one on the east. Between them, dead center, sleeps the stone Angel: an impassable landmark. You cannot march straight through the middle. That single decision shapes everything.<br />
<br />
The field is split into a <span style="font-weight: bold;" class="mycode_b">top lane</span> and a <span style="font-weight: bold;" class="mycode_b">bottom lane</span>, and to reach the enemy you have to commit to one of them and go <span style="font-style: italic;" class="mycode_i">around</span> the Angel. The board is deliberately <span style="font-weight: bold;" class="mycode_b">small</span> -- we tested bigger layouts and they played soft, because there was always somewhere else to be. A tight board does two things at once: it creates real <span style="font-weight: bold;" class="mycode_b">choke points</span> you have to fight over, while still leaving <span style="font-weight: bold;" class="mycode_b">two separate lanes of attack</span> so a single wall never locks the whole game. You are always choosing between pressure up top, pressure down low, or splitting your attention and getting punished for it.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">The numbering system</span></span><br />
Every hex has a coordinate, written <span style="font-weight: bold;" class="mycode_b">(column, row)</span>:<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Column</span> is the west-east axis. It is <span style="font-weight: bold;" class="mycode_b">signed from the center</span>: negative to the west (the left wizard's side), positive to the east (the right wizard's side), 0 down the spine.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Row</span> is the top-bottom axis, also signed from center: negative rows are the <span style="font-weight: bold;" class="mycode_b">top lane</span>, positive rows are the <span style="font-weight: bold;" class="mycode_b">bottom lane</span>, 0 is the central line the Angel sits on.<br />
</li>
</ul>
So the four corners read -2,-2 (top-west), 2,-2 (top-east), -2,2 (bottom-west), and 2,2 (bottom-east). The <span style="font-weight: bold;" class="mycode_b">center row is the widest</span> -- it stretches to -3,0 and 3,0, the deepest points on each wizard's side. And notice the very top and very bottom rows have <span style="font-weight: bold;" class="mycode_b">no center hex</span> (there is no 0,-2 or 0,2) -- the lanes physically pinch there, which is part of why the edges play as safer approach routes and the center plays as a knife fight.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Why signed-from-center, and not 1-8 or row/column?</span></span><br />
This was the argument we kept having, so here is the reasoning we landed on.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1) The board is a mirror, so the numbers should be a mirror.</span> ArcoMage is symmetric -- both wizards see the same board from opposite ends. With a corner origin (chess-style a1 to h8, or a plain 1-8 grid) one player "owns" the low numbers and the other owns the high ones, and the middle lands on some arbitrary value like 4 or 5. With a center origin, 2,0 and -2,0 are literally mirror images, the Angel is 0,0 for everybody, and neither side's home reads as more "primary" than the other's. The notation is as neutral as the fight.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">2) The sign tells you the story at a glance.</span> Read any coordinate and you instantly know three things: which <span style="font-weight: bold;" class="mycode_b">side</span> you're on (column sign -- west or east), which <span style="font-weight: bold;" class="mycode_b">lane</span> you're in (row sign -- top or bottom), and how <span style="font-weight: bold;" class="mycode_b">deep</span> you've pushed (the magnitude). -3,0 isn't just "a hex," it reads as <span style="font-style: italic;" class="mycode_i">all the way into the west wizard's throat, dead center</span>. A 1-8 grid makes you do arithmetic to figure out the same thing.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">3) It matches the geometry.</span> The board is widest at the spine and pinches at the edges. Putting 0 on the spine and letting the numbers grow outward mirrors how the board actually looks, so the map in your head and the map on the table agree.<br />
<br />
Chess uses a corner origin because a chessboard is a neutral 8x8 with no center landmark and a fixed orientation. Our board has a shared center, a shared obstacle, and two players pushing <span style="font-style: italic;" class="mycode_i">inward from opposite sides</span> -- a center origin fits that shape far better.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Notating a move</span></span><br />
Write it like chess:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>Imp -&gt; 2,-1      summon (or move) to the east side, top lane, one deep
Wall @ -1,1      raise a wall on the west side of the bottom lane
Moat @ 0,1       flood the bottom-lane centerline hex under the Angel
Fireball 3,0     hit the deepest hex on the east wizard's spine</code></div></div>Full turns can be strung together -- west player, then east player -- so a whole game is replayable from a few lines of text. That is the real payoff of a clean coordinate system: you can share a game, argue about a line, and diagram a tactic in a single sentence.<br />
<br />
<span style="font-size: 4pt;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">A few opening thoughts (tactics)</span></span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">The Angel is your anchor, not just a wall.</span> Everything at row 0 hugs the center -- contest it early, because whoever controls the hexes beside the Angel dictates which lane the game is fought in.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Threaten both lanes, commit to one.</span> Because the board is small, a credible feint up top pulls defense off the bottom. Show pressure at -1,-1 and strike through -1,1.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">The pinch points (x,-2 and x,2) are safer roads but slower.</span> The edge lanes have no center hex, so they're harder to cut off -- good for a patient push, bad if you're racing.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Depth is danger.</span> The -3,0 and 3,0 hexes are the deepest strikes but the most exposed; landing something there is a statement, holding it is another thing entirely.<br />
</li>
</ul>
That's the system. Learn to read a coordinate on sight and the whole board opens up -- you stop seeing hexes and start seeing lanes, choke points, and threats. Post your lines in this format and let's start building an opening theory.]]></content:encoded>
		</item>
	</channel>
</rss>