混 Konsei ReiyotanStatic web edition · v1.3.3
Bookshelf Core Index Sheets KRJPEN
English edition v1.3.3 · fc-doc

#Source Badges and Module On/Off Notation

Contents

Summary. A source badge is notation that makes the source and self-containment principles of co-99-01 Authority System and co-99-03 fc Specification visible beside an NPC card. If NPC Creation and Dan Advancement Check Procedure checks numbers and choice order, this document decides what text to use for non-co data.

#Scent — Where Did This Effect Come From?

Suppose one line of school talent sits on an NPC card without a source. If the GM's table reading that line has not turned on that school module, the whole card stops there. The card did not say what must be turned on for this person to function.

The source badge fills that silence. It tells you, right beside the item, which volume an item came from, whether it is a number or commentary, and, if it is ex2, which module must be on for it to operate. "When you pull out a single name, that person should already have lived an age" — this is how that promise is received at the level of data consistency. The source badge is the surface of the use condition.

The actual shape of the badge may fit the table or editorial format. But the source code must be immediately beside the item.

#Law 1 — What Gets a Badge?

Attach a badge to mechanical-effect items from sources other than co (ex1, ex2, fcMM).

Targets: maneuvers, talents, spells, schools, training methods, equipment/props, masterworks/Divine Treasures, Livelihood, the Commoner class, alternate backgrounds, and alternate rules.

Things that do not get one:

  • co canon items. No notation = co is the default contract. Do not attach badges to skeletal terms such as attributes, check formulas, rounds, or Wounds.
  • Fiction-Only description. Atmospheric description such as backstory and relationship hooks does not get source badges (descriptive sources are handled separately in §Law 4).

No notation is canon. Excess notation that attaches [co] to every line is prohibited. Leaving no notation as canon makes non-co dependencies stand out visually and keeps the card readable.

#Law 2 — Badge Notation Format

The notation grammar is Item Name [source-code]. Write the source code as far as possible down to the document identifier level (ex1-99-06, fc05-05-02), so the item's source document can be traced later. Attach the badge immediately beside the item.

Dan 5 Commoner [ex1-99-06]
Livelihood: Blacksmithing Artisan [ex1-99-05]
Alternate Talent: Emergency Regrinding [fc05-05-02]
Spell: Soshiki Talisman [ex2-35 On]
School: Tennen Rishin-ryu [ex2-10 On]
Equipment: Drifted Noble Treasure [fc10-03-05]
Masterwork: Dojigiri [co-07-02] (anecdote and ownership genealogy commentary fc05-02-02)

The code block above is the standard the card follows literally. How to read it:

  • ex2 items attach the module On/Off state after the code (§Law 3).
  • The last line is notation for when one item uses two overlapping sources — the numerical effect is separated as [co-07-02] (square brackets), and the commentary as (... fc05-02-02) (separate parenthetical note) (§Law 4).
  • Masterworks are co canon and therefore have no notation in principle, but because ownership conditions, curses, and costs must be separately noted, writing the source together is recommended (§Law 5).

References cannot replace badges. Gathering sources at the end of the document is not enough — the badge must be attached inline, right beside the item.

No new rules. Do not let examples introduce new skill names, new resources, or new dice (observe the 36 skills, 2d10/d100, and Wounds/Energy contracts). If a ranged-shooting example is needed, write it as Archery — a school proper name such as 銃術 may be used, but its skill name is Archery.

#Law 3 — ex2 Module On/Off Notation

As ex2-00-00 declares, ex2 is optional material with independent On/Off choices by section. A section not chosen is treated as "not present at the table." Therefore ex2-source items write module number + On/Off together — [ex2-35 On], [ex2-10 On].

  • The module unit follows the two-digit sections of ex2 (01, 02, 03, 10 through 21, 25, 30, 35, 40, 45, 50, 55, 60, 80, 99). If the detail must be specified, go down to the document identifier as in [ex2-19-06 On].
  • If one NPC uses an ex2 module, place one "required module list" line at the head of the card's §Source section. Example: Required ex2 modules: 10(Swordsmanship Schools) On, 35(Spells) On. The GM should know, as soon as the card opens, "what must be turned on to use this person as written."

#ex2 Self-Contained Fallback (Required)

Each ex2 dependency also writes one line for "what happens if that module is Off." Use one of three branches:

  • (a) replace with a co canon item,
  • (b) omit that option (the person stands on co alone),
  • (c) the GM substitutes an equivalent co effect.

This self-containment contract follows the "obligation to specify a fallback when ex is absent" in co-99-03 fc Specification and the source-independence principle in co-99-02 Core Principles. fc11's self-containment holds only if the card does not break at a table where the ex2 item is turned off.

#Law 4 — Numerical Source vs Commentary Source

When one item layers several sources, separately mark the numerical source that defines the actual mechanical effect (numbers, checks, slots) and the commentary source that provides background or anecdote.

  • Grammar: put the numerical source in the front square brackets, and the commentary source in the rear parentheses. Example: Masterwork: Dojigiri [co-07-02] (anecdote and ownership genealogy commentary fc05-02-02).
  • Fiction-Only, RP Guide, and Reference Only documents cannot be numerical sources. Under co-99-01 Authority System and co-99-03 fc Specification, Fiction-Only is "staging reference only," RP Guide does not guarantee mechanical effects, and Reference Only is "setting, history, and anecdote commentary," so these three may appear only in the commentary-source field.
  • The numerical-source field only receives the grades that define actual values and mechanisms — Canon, Summary, Campaign Module, Scene Tool, Data Catalog, and Variant.

If the same line for the same person does not separate "where the rule comes from" and "where the story comes from," drift arises where staging numbers from a Fiction-Only short story are misused as mechanical effects. This section cuts that boundary at the notation stage.

#Law 5 — Source-Notation Failure Conditions

If any one of the following applies, treat it as a source-notation failure. Fix the notation before using the card.

  1. A non-co mechanical effect has no badge.
  2. An ex2 item has no On/Off notation.
  3. An ex2 dependency has no one-line self-contained fallback.
  4. Fiction-Only / RP Guide appears in the numerical-source field.
  5. Overlapping sources are not separated into numerical/commentary sources.
  6. Inline badges have been replaced with only end-of-document references.

#Masterworks and Divine Treasures Are Separately Noted Even When They Are co Canon

Masterworks and Divine Treasures are co canon and therefore have no notation in principle, but ownership conditions, curses, costs, and sources must be separately noted (linked to NPC Creation and Dan Advancement Check Procedure §Law 5). Simple free bonus equipment is stopped by the non-optimization standard.

Source rules are not "recommendations that are nice to follow," but card use requirements. These 6 conditions become the classification keys for the NPC Index by Source.

#Scent — One Sentence

"A single badge is small, but without it, a whole table cannot open a single person."