<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rts on Coyote Time</title>
    <link>https://blog.jonmikeys.com/tags/rts/</link>
    <description>Recent content in Rts on Coyote Time</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.jonmikeys.com/tags/rts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Part 1: What Tactical Terrain Actually Means</title>
      <link>https://blog.jonmikeys.com/posts/what-tactical-terrain-actually-means/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.jonmikeys.com/posts/what-tactical-terrain-actually-means/</guid>
      <description>Tactical terrain analysis is the practice of asking what the map makes possible.&#xA;A hill, wall, chokepoint, or dark corner is not automatically useful. It becomes useful when it changes movement, visibility, or risk. That is why terrain analysis matters: it turns the map into data that an AI can evaluate.&#xA;The basic question The core question is simple:&#xA;Which parts of this map give one side an advantage?&#xA;That question is more useful than a hand-authored list of “important” spots.</description>
    </item>
  </channel>
</rss>
