<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ReferenceSheet on emsenn.net</title>
    <link>https://emsenn.net/tags/referencesheet/</link>
    <description>Recent content in ReferenceSheet on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 09 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/referencesheet/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>reference sheet</title>
      <link>https://emsenn.net/library/domains/engineering/domains/games/domains/role-playing-games/domains/tabletop-role-playing-games/terms/reference-sheet/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/games/domains/role-playing-games/domains/tabletop-role-playing-games/terms/reference-sheet/</guid>
      <description>&lt;p&gt;A reference sheet is a compact player-facing or GM-facing artifact that summarizes rules, procedures, names, or recurring options for fast use at the table. Unlike a full rulebook, a reference sheet is designed for retrieval during play rather than for first-time learning.&lt;/p&gt;&#xA;&lt;p&gt;Good reference sheets reduce page-flipping and free attention for the fiction. They work best when they collect only the procedures that recur often enough to interrupt play if the table has to keep searching for them. In practice, this usually means action summaries, result bands, turn structure, status reminders, or a short list of common moves and costs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
