<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Handout on emsenn.net</title>
    <link>https://emsenn.net/tags/handout/</link>
    <description>Recent content in Handout 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/handout/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>handout</title>
      <link>https://emsenn.net/library/domains/engineering/domains/games/domains/role-playing-games/domains/tabletop-role-playing-games/terms/handout/</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/handout/</guid>
      <description>&lt;p&gt;A handout is a player-facing artifact used in a &lt;a href=&#34;../index.md&#34; class=&#34;link-internal&#34;&gt;tabletop role-playing game&lt;/a&gt; to externalize information from the fiction. A handout might be a letter, map fragment, rumor sheet, wanted poster, rules summary, portrait, or inventory list. Its purpose is to give the table a durable object they can point to, reread, and reason from during play.&lt;/p&gt;&#xA;&lt;p&gt;Handouts matter because tabletop play depends on shared memory and shared attention. A spoken description disappears unless someone writes it down. A handout keeps names, clues, symbols, and stakes available after the moment of narration has passed. Good handouts therefore do two jobs at once: they help players track the fiction, and they help the GM present information cleanly without repeating it from scratch.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
