Main Page: Difference between revisions

Content deleted Content added

Inline

Latest revision as of 18:03, 9 May 2025

This wiki documents a system for converting Teriock FanWar LARP to a tabletop or online system. The basic philosophy is to not simulate live action FanWar at all. Rather, it's to design a system for tabletop from the ground up, redefining every relevant keyword and ability in the process. Some things in Teriock Online work very similarly to live action FanWar, others are completely different. For more information, see the design goals below.

Progress So Far / How Many Pages Are Done
Everything	Abilities	Classes	Conditions	Core Rules	Creatures	Damage Types	Drain Types	Equipment	Keywords	Properties	Specializations	Tradecrafts
2,035	570	15	44	88	13	16	3	53	25	39	0	29

There is also a Foundry VTT system in development.

What to Read

During play testing, I've assumed anyone looking at this site is familiar with live action FanWar and has access to me to ask questions. With that in mind, I recommend reading the rules in roughly the following order.

How to Use this Wiki

This website is built using MediaWiki (same engine as Wikipedia). This allows for detailed templates, "transclusion" (repeating text on different pages), previews, page tags/categories, etc. It means I can have a detailed system that constantly refers back to other parts but that is easy to maintain. It should mean it's easy to pull up abilities, mechanics, and interactions and also that changes should propagate through everything smoothly. For example, if I change how being frozen works, then it will update everywhere it's referenced. Basically what I'm saying is this site works like Archives of Nethys.

If you are ever lost on where to find something, every rule in Teriock Online can be found in this master index.

Namespaces

In case you ever get confused, know that this wiki is divided into several "namespaces". These are akin to chapters in a book and allows for several pages to have the same name without getting confused with each other. For instance, this lets us distinguish the ability Duel from the condition of being in a duel. Some locations might at first seem counter intuitive. An example would be that there's no page called "Fire Damage" but there is one called "Damage:Fire" which defines the "Fire" damage type in the "Damage" namespace. The front end namespaces and what they contain are as follows.

Ability: All abilities in the game. This includes every type of action a creature can do (from Snare, to Opportunity Attack, to Catch Item, to Drop Prone).
Class: The game's base 15 classes.
Condition: Static conditions that affect creatures.
Core: Any core rules that relate to Teriock Online itself and aren't just keyword from live action FanWar that's been redefined.
Creature: The statistics for all the creature types in the game. This namespace is currently a work in progress.
Damage: Any damage type. Think of this as types of harm that reduce HP and related effects.
Drain: Any drain type. Think of this as types of harm that reduce MP and related effects. This means we can have mana drain and memory drain listed separately. It is also where things like wither are located.
Equipment: Any type of standard equipment in the game.
Keyword: Any miscellaneous keywords from live action FanWar that have been redefined for Teriock Online.
Property: Static properties than an item could have.
Spec: All the prestige specializations in the game. This namespace is currently empty.
Tradecraft: All the tradecrafts in the game.

Design Goals

These were the main principles that influenced the design of the system.

Be built first and foremost for online and tabletop gameplay.
Keep consistent keywords with live action FanWar so as to make system conversion smooth.
It should, in principle, also be possible to convert from this system back to live action FanWar for when Teriock officially returns to Chris.
Be built for small parties with long adventuring days (D&D or Pathfinder style, not live action MMO style).
Mechanics (especially combat mechanics) should be "crisp" and well defined (much better defined than in live action FanWar).
There should be a robust (if simple) system for non-combat mechanics as well.
Resource management, including HP and MP should matter.
Combat should be dynamic, interesting, and not entirely predictable.
For now, I've retained the "junior league" rank system and added some items at intermediate levels. This is for conversion and playtest purposes. However, leveling up will not operate on a "set" or "three hour" basis. It will be more milestone style (up to GM discretion). I've added additional level up bonuses between ranks to accommodate for this.
It'd be nice if the classes are balanced.

And these were things that were not goals of the design process.

No regard was given to simulating live action FanWar.
No regard was given to replicating the precise balance of live action FanWar. This means some of the live action design goals were not important here. For instance, FanWar LARP requires that baddies be quick to setup and play and must operate more-or-less consistently no matter who is playing them. This means they operate very similarly to player characters (some simple base stats, slap a standard class on there, give them a magic item, and go). That's not required for an online system. So, while I have some rules describing how to convert existing baddies, this system is asymmetrically designed around player characters.
The game engine doesn't need to operate in real time. In live action combat, you can't have dice rolling or arithmetic beyond adding/subtracting ones and fives. This makes a lot of abilities essentially turn into "no effect" mechanics. But online systems can have more nuance. So I've changed how resistances work, removed "20 count" timers, etc.

Random Patch Notes

These reflect a few of the major changes from live action FanWar. They're presented in no particular order.

Most 20 count timers have been turned into "exploding" d4s.
There's no concept of "called" abilities, since that's something that descends from having to physically call out the names of abilities that you use.
I've just completely axed the keyword "prevention" from the game. It's redundant. Everything's been rewritten without it and it wsa easy.
Reaction/resistance meta will likely be substantially less powerful due to limited reaction economy and resistances not being absolute.
I've removed all references to levels/ranks in something (ranks in Flame Mage, levels in Historian, and so on). Things scale off absolute factors like your total level, your proficiency, etc. This will make some things much better defined. ("How many ranks in nature mage do I have for polymorph if I got the ability as a blessing from my deity? Does it use ranks in paladin instead???") And in other cases, it will keep the "scope" of things clearer (What does 1025 levels in Blacksmith even mean? Am I 51.3 × better at blacksmithing than a level 20 adventurer that put all their levels in Blacksmith? What?)
There's lots of "hidden" rituals/abilities that exist in FanWar that are referenced, but for which it's not clear how they work. How does one study an area for teleporting? Does the oracle happen during the ritual or after? Is it a ritual to get a familiar? What about for a divine gift? A pact?
Although "encounters" will still happen in gameplay, there's no reference to encounters in the rules themselves. Everything is "10 minutes" or "during a short rest" or "1 minute without combat" and whatnot. This gets rid of all the "are we in a new encounter yet?" ambiguity that we have in live action FanWar.
Currently knockout doesn't exist. It might just add it back in as non-lethal damage.

Playtest Priorities

I'm very interested in seeing how warriors/semis feel compared to mages, how the core blocking mechanic feels, and how all of the various numbers stack up against each other. Some things that I thought were giga strong/weak when designing will certainly be the opposite. The good news is that it's very easy to refine numbers, tweak things, and change rules. Much easier than in live action FanWar. I'm open to lots of changes.

That being said, please don't give feedback on the Elder Sorcery creation system. (Scaling with rotators, number of "slots", and whatnot is fair game. It's the mechanics of making a spell that I don't want to hear about.) I 've received so many suggestions for people's pet spell creation procedures and that's an entirely different kettle of worms that's fundamentally outside of the actual rules of the game. What I have written here at the moment isn't something that I'm definitive about or confident in. It's literally just random words on a page to put something out there so that I could get the core game done. It's not anything more than that. Basically just treat ES creation as more-or-less unwritten.

@@ Line 1: / Line 1: @@
+This wiki documents a system for converting Teriock FanWar LARP to a tabletop or online system. The basic philosophy is to ''not'' simulate {{LARP}} at all. Rather, it's to design a system for tabletop from the ground up, redefining every relevant keyword and ability in the process. Some things in {{Online}} work very similarly to {{LARP}}, others are completely different. For more information, see the [[#Design Goals|design goals]] below.
-== Introduction ==
+{| class="wikitable"
-This wiki documents a system for converting Teriock FanWar LARP to an online system.
+|+ Progress So Far / How Many Pages Are Done
+| '''{{L|Category|Rules|Everything|u=1}}''' || {{L|Category|Abilities|u=1}} || {{L|Category|Classes|u=1}} || {{L|Category|Conditions|u=1}} || {{L|Category|Core rules|Core Rules|u=1}} || {{L|Category|Creatures|u=1}} || {{L|Category|Damage types|Damage Types|u=1}} || {{L|Category|Drain types|Drain Types|u=1}} || {{L|Category|Equipment|u=1}} || {{L|Category|Keywords|u=1}} || {{L|Category|Properties|u=1}} || {{L|Category|Specializations|u=1}} || {{L|Category|Tradecrafts|u=1}}
+|-
+| '''{{NUMBEROFPAGES}}''' || {{PAGESINCATEGORY:Abilities|pages}} || {{PAGESINCATEGORY:Classes|pages}} || {{PAGESINCATEGORY:Conditions|pages}} || {{PAGESINCATEGORY:Core rules|pages}} || {{PAGESINCATEGORY:Creatures|pages}} || {{PAGESINCATEGORY:Damage types|pages}} || {{PAGESINCATEGORY:Drain types|pages}} || {{PAGESINCATEGORY:Equipment|pages}} || {{PAGESINCATEGORY:Keywords|pages}} || {{PAGESINCATEGORY:Properties|pages}} || {{PAGESINCATEGORY:Specializations|pages}} || {{PAGESINCATEGORY:Tradecrafts|pages}}
+|}
+There is also a [https://github.com/GabePoel/Teriock-FoundryVTT Foundry VTT system] in development.
 == What to Read ==
+During play testing, I've assumed anyone looking at this site is familiar with {{LARP}} and has access to me to ask questions. With that in mind, I recommend reading the rules in roughly the following order.
-Start with the following:
 # Playing the Game
-## {{L|Core|Combat}}
+## {{L|Core|Combat|u=1}}
-## {{L|Core|Interactions}}
+## {{L|Core|Interactions|u=1}}
-## {{L|Core|Resting}}
+## {{L|Core|Tradecrafts|u=1}}
+## {{L|Core|Resting|u=1}}
 # Converting or Building a Character
-## {{L|Core|Leveling Up}}
+## {{L|Core|Leveling Up|u=1}}
-## {{L|Core|Size}}
+## {{L|Core|Size|u=1}}
-## {{L|Core|Attributes}}
+## {{L|Core|Attributes|u=1}}
-## {{L|Core|Presence}}
+## {{L|Core|Presence|u=1}}
-## {{L|Core|Proficiency Bonus}}
+## {{L|Core|Proficiency Bonus|u=1}}
-## {{L|Core|Fluency Bonus}}
+## {{L|Core|Fluency Bonus|u=1}}
 # References
-## {{L|Category|Equipment}}
+## {{L|Category|Equipment|u=1}}
-## {{L|Category|Classes}}
+## {{L|Category|Classes|u=1}}
-## {{L|Category|Abilities}}
+## {{L|Category|Abilities|u=1}}
-## {{L|Category|Conditions|Creature conditions}}
+## {{L|Category|Conditions|u=1}}
-## {{L|Category|Properties|Item properties}}
+## {{L|Category|Properties|Item properties|u=1}}
-## {{L|Category|Damage types}}
+## {{L|Category|Damage types|u=1}}
-## {{L|Category|Keywords|Other keywords}}
+## {{L|Category|Keywords|Other keywords|u=1}}
-If you are ever lost on where to find something, every rule in {{Online}} can be found in this {{L|Category|Rules|master index}}.
-=== Desiderata ===
+== How to Use this Wiki ==
+This website is built using [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] (same engine as [https://www.wikipedia.org/ Wikipedia]). This allows for detailed templates, "[https://www.mediawiki.org/wiki/Transclusion transclusion]" (repeating text on different pages), previews, page tags/categories, etc. It means I can have a detailed system that constantly refers back to other parts but that is easy to maintain. It should mean it's easy to pull up abilities, mechanics, and interactions and also that changes should propagate through everything smoothly. For example, if I change how being {{L|Condition|Frozen}} works, then it will update everywhere it's referenced. Basically what I'm saying is this site works like [https://2e.aonprd.com/PlayersGuide.aspx Archives of Nethys].
+If you are ever lost on where to find something, every rule in {{Online}} can be found in this {{L|Category|Rules|master index}}.
+=== Namespaces ===
+In case you ever get confused, know that this wiki is divided into several "namespaces". These are akin to chapters in a book and allows for several pages to have the same name without getting confused with each other. For instance, this lets us distinguish the ability {{L|Ability|Duel}} from the condition of being in a {{L|Condition|Dueling|Duel}}. Some locations might at first seem counter intuitive. An example would be that there's no page called "Fire Damage" but there is one called "[[Damage:Fire]]" which defines the "Fire" damage type in the "Damage" namespace. The front end namespaces and what they contain are as follows.
+; {{L|Category|Abilities|Ability|u=1}}
+: All abilities in the game. This includes every type of action a creature can do (from {{L|Ability|Snare}}, to {{L|Ability|Opportunity Attack}}, to {{L|Ability|Catch Item}}, to {{L|Ability|Drop Prone}}).
+; {{L|Category|Classes|Class|u=1}}
+: The game's base 15 classes.
+; {{L|Category|Conditions|Condition|u=1}}
+: Static conditions that affect creatures.
+; {{L|Category|Core rules|Core|u=1}}
+: Any core rules that relate to {{Online}} itself and aren't just keyword from {{LARP}} that's been redefined.
+; {{L|Category|Creatures|Creature|u=1}}
+: The statistics for all the creature types in the game. This namespace is currently a work in progress.
+; {{L|Category|Damage types|Damage|u=1}}
+: Any damage type. Think of this as types of harm that reduce {{L|Core|HP}} and related effects.
+; {{L|Category|Drain types|Drain|u=1}}
+: Any drain type. Think of this as types of harm that reduce {{L|Core|MP}} and related effects. This means we can have {{L|Drain|Mana|Mana Drain}} and {{L|Drain|Memory|Memory Drain}} listed separately. It is also where things like {{L|Drain|Wither|Wither}} are located.
+; {{L|Category|Equipment|u=1}}
+: Any type of standard equipment in the game.
+; {{L|Category|Keywords|Keyword|u=1}}
+: Any miscellaneous keywords from {{LARP}} that have been redefined for {{Online}}.
+; {{L|Category|Properties|Property|u=1}}
+: Static properties than an item could have.
+; {{L|Category|Specializations|Spec|u=1}}
+: All the prestige specializations in the game. This namespace is currently empty.
+; {{L|Category|Tradecrafts|Tradecraft|u=1}}
+: All the tradecrafts in the game.
+== Design Goals ==
 These were the main principles that influenced the design of the system.
 * Be built first and foremost for online and tabletop gameplay.
-* Keep consistent keywords with live action FanWar so as to make system conversion smooth.
+* Keep consistent keywords with {{LARP}} so as to make system conversion smooth.
-* It should also be possible to convert from this system ''back'' to live action for when Teriock officially returns to Chris.
+* It should, in principle, also be possible to convert from this system ''back'' to {{LARP}} for when Teriock officially returns to Chris.
 * Be built for small parties with long adventuring days (D&D or Pathfinder style, not live action MMO style).
-* Mechanics (especially combat mechanics) should be "crisp" and well defined.
+* Mechanics (especially combat mechanics) should be "crisp" and well defined (''much'' better defined than in {{LARP}}).
 * There should be a robust (if simple) system for non-combat mechanics as well.
-* Resource management should matter.
+* Resource management, including {{L|Core|HP}} and {{L|Core|MP}} should matter.
 * Combat should be dynamic, interesting, and not entirely predictable.
-* For now, I've retained the "junior league" rank system and added some items at intermediate levels. This is for conversion and playtest purposes. However, leveling up will not operate on a "set" or "three hour" basis. It will be more milestone style (up to GM discretion). I've added additional level up bonuses between ranks to accommodate for this.
+* For now, I've retained the "junior league" rank system and added some items at intermediate levels. This is for conversion and playtest purposes. However, {{L|Core|Leveling Up|leveling up}} will not operate on a "set" or "three hour" basis. It will be more milestone style (up to {{GM}} discretion). I've added additional level up bonuses between ranks to accommodate for this.
 * It'd be nice if the classes are balanced.
@@ Line 42: / Line 78: @@
 * No regard was given to replicating the precise balance of {{LARP}}. This means some of the live action design goals were not important here. For instance, FanWar LARP requires that baddies be quick to setup and play and must operate more-or-less consistently no matter who is playing them. This means they operate very similarly to player characters (some simple base stats, slap a standard class on there, give them a magic item, and go). That's not required for an online system. So, while I have some rules describing how to convert existing baddies, this system is asymmetrically designed around ''player characters''.
 * The game engine doesn't need to operate in real time. In live action combat, you can't have dice rolling or arithmetic beyond adding/subtracting ones and fives. This makes a lot of abilities essentially turn into "no effect" mechanics. But online systems can have more nuance. So I've changed how resistances work, removed "20 count" timers, etc.
+== Random Patch Notes ==
+These reflect a few of the major changes from {{LARP}}. They're presented in no particular order.
+* Most 20 count timers have been turned into "exploding" {{Dice|d4}}s.
+* There's no concept of "called" abilities, since that's something that descends from having to physically call out the names of abilities that you use.
+* I've just completely axed the keyword "prevention" from the game. It's redundant. Everything's been rewritten without it and it wsa easy.
+* Reaction/resistance meta will likely be ''substantially'' less powerful due to limited {{L|Category|Reaction abilities|reaction economy}} and {{L|Keyword|Resistance|resistances}} not being absolute.
+* I've removed all references to levels/ranks ''in'' something (ranks in Flame Mage, levels in Historian, and so on). Things scale off absolute factors like your total level, your {{L|Core|Proficiency Bonus|Proficiency}}, etc. This will make some things much better defined. ("How many ranks in nature mage do I have for polymorph if I got the ability as a blessing from my deity? Does it use ranks in paladin instead???") And in other cases, it will keep the "scope" of things clearer (What does 1025 levels in Blacksmith even mean? Am I 51.3 {{Times}} better at blacksmithing than a level 20 adventurer that put all their levels in Blacksmith? What?)
+* There's lots of "hidden" rituals/abilities that exist in FanWar that are referenced, but for which it's not clear how they work. How does one study an area for {{L|Ability|Teleport|teleporting}}? Does the {{L|Ability|oracle}} happen during the ritual or after? Is it a ritual to get a {{L|Ability|Familiar Bond|familiar}}? What about for a {{L|Ability|Divine Gift|divine gift}}? A {{L|Ability|Spirit Pact|pact}}?
+* Although "encounters" will still happen in gameplay, there's no reference to encounters in the rules themselves. Everything is "10 minutes" or "during a short rest" or "1 minute without combat" and whatnot. This gets rid of all the "are we in a new encounter yet?" ambiguity that we have in {{LARP}}.
+* Currently knockout doesn't exist. It might just add it back in as non-lethal damage.
+== Playtest Priorities ==
-=== How to Use This Wiki ===
+I'm very interested in seeing how warriors/semis feel compared to mages, how the core blocking mechanic feels, and how all of the various numbers stack up against each other. Some things that I thought were giga strong/weak when designing will certainly be the opposite. The good news is that it's very easy to refine numbers, tweak things, and change rules. Much easier than in {{LARP}}. I'm open to lots of changes.
+That being said, please don't give feedback on the Elder Sorcery creation system. (Scaling with rotators, number of "slots", and whatnot is fair game. It's the mechanics of making a spell that I don't want to hear about.) I 've received ''so'' many suggestions for people's pet spell creation procedures and that's an entirely different kettle of worms that's fundamentally outside of the actual rules of the game. What I have written here at the moment isn't something that I'm definitive about or confident in. It's literally just random words on a page to put ''something'' out there so that I could get the core game done. It's not anything more than that. Basically just treat ES creation as more-or-less unwritten.
-This website is built using MediaWiki (same engine as Wikipedia). This allows for detailed templates, "transclusion" (repeating text on different pages), previews, page tags/categories, etc. It means I can have a detailed system that constantly refers back to other parts but that is easy to maintain. It should mean it's easy to pull up abilities, mechanics, and interactions and also that changes should propagate through everything smoothly. For example, if I change how being {{L|Condition|Frozen]}} works, then it will update everywhere it's referenced. Basically what I'm saying is this site works like [https://2e.aonprd.com/PlayersGuide.aspx Archives of Nethys].
-=== One Last Note ===
-While designing this system, I've typically leaned on the ''more experimental'' side. Not everything I've come up with will work out. I've flagged mechanics I'm particularly unsure about. Feedback (preferably after playtesting) would be very much appreciated.