ViO#9rlKQ|^ T>tF=U\w0% $I!F<ۛ)蚹^1E!P*5Ӕl%qL7D2'THl.>UA]!Ɍ >^B~J:i-ο +tWOa0{ˋ Xh!c۳MǦ9+"+c7z̍JIY#oKWT$~ p++nSp )(̛*Yu@FSo!'w&>qFx u+ 3QB=Č,ŧQJ=3S: |8!,lc}&.5ҩcV^ڵF"³:< ur+_0 C FYF& OZS `ƸFꖵ,9Ybh4eBMkѴ2_cmB[N-$LM>7SNcXB69T^2%i¨jYpgK\2.JҪei b z·,p̡zyZK}L$;1h^NKAz]; RL!8ChV|>&@C 9RwEBoCF K5)нbʲPȉ65N9urH?dy@N*!OVݩ¬Xd3QtMKg^(@}9>/1F^\7Tql5Yπ{6LZQ[3cm2nVrl`ʦ4XZC" QZ!q˥>:9+j4뒵oy?p\xbD!Ż>1e{^&eiWIo]VzYze1jާؑiQkUtSpC*Mb:sh6(8Krz1>ܤkY';E/cSQ&;;DL{ ?L6x98v@Q_rw IO=|v8a݆*^z\WsU|-ʈE^Ͱ{XZyLvX&mȦZ^Shpe)n3{\4T?)];}\gWl+hP

The Travels of Mendes Pinto: Team Game

Don't Forget the Damn Index!

Sergio Mascarenhas
August 30, 2001  

Last month I explained what's the whole purpose of this ongoing column: to design the Core Rule Book in The Travels of Mendes Pinto game line which name is The Annotated Book of Mendes Pinto vol. 1, or AB01. In the previous column I mentioned what will be left out of the book: the Game Master toolkit (advice on running the game, and setting development material), special rules for specific situations, detailed setting sources, fully fledged fiction, each allowing for the design of one or more independent books. This month we will shift our attention to another issue: the overall content of the book, its general outline, and breakup into sections.

You see, it may be a personal thing but I think that it's always useful to start with a good plan. After all RPGs have been in development for almost thirty years. Today one can sort out what works and what doesn't (1). The plan laid down below will help insuring the coherence of the design process. It will allow us to see what's been finished and what's missing. And it will provide a direction to future developments of this column.

One thing is sure: We must not forget about indexes. One at least.

BUILDING LITTLE BLACK BOXES

The problem is that there are many different ways to structure a rule book. Which one to chose? I'll consider the next ones before attempting to define the plan for AB01:

SETTING VERSUS RULES

Some games separate setting information from rules into two big sections. Should I follow this approach? Yes or not? Umm, we must never forget the Cardinal Principle: Rules follow Setting, isn't it?

Yes it is. And because it is, we cannot separate rules from setting. If rules follow setting, there's no presentation of the rules that does not incorporate setting into it. Why do we have rules for melee combat? Because the setting requires it. Why are there no rules for starship traveling? Because there is no such thing in the setting (I'm speaking about TToMP here). Where there are rules, there is setting.

Conversely, where there is setting there are rules. Remember this is a game. This is not a simple description of a setting. Setting material is not produced for the sake of providing a good narrative. It's produced to be the basis of a game. It is evaluated not on itself, but on its ability to lead us to a great gaming experience. So, where there's setting there are (at least, implicit) rules (2).

The bottom line is that it makes no sense to attempt to separate setting from rules. On the contrary, they should be integrated into a perfect blend. Let's see whether this is feasible.

CONTENT DRIVES STRUCTURE

It was mentioned before. AB01 will contain the next things: Basic setting information; character definition rules; situation resolution rules; character evolution rules; reference data. How do we articulate all of this?

One way would be to just follow that order and divide the book into four chapters: 1- The world of Mendes Pinto; 2 - The Character; 3 - The Character in action; 4 - The Character in time. We will come back at this outline in a moment. Before let's look at some other alternatives.

FUNCTIONAL BREAKDOWNS

Another approach to game book structuring is based on the functionality of the book. How is it intended to be used? From my point of view RPG books can be used in 5 ways: as entertainment books; as teaching manuals; as reference books; as toolkits; as any combination of the previous usages.

RPG books as entertainment

It's like sports, really. Most people buy sports-related products (equipment, magazines, books) but don't actually play sports. They buy those things because it's entertaining, and it fosters their imaginations. It works like fiction.

The same can be said about a lot of people that buy RPG books. They can't, or don't intend to play (either because they don't have playing mates, because they don't like the ones they can get, or because they can't find the time to play). They just like to read the books.

If one is writing an RPG book to this people, one only needs to ensure that the book is consistent and makes a good reading. One needs not to worry about how the book is going to be used, because there will be no usage other than being read. In this case one basically writes the book like a piece of fiction. The only specific thing is that this fiction is complex, since it requires several levels: the setting description level; the character-in-setting level; the rules meta-setting level; and so on.

RPG books as teaching manuals

How does one learn how to play an RPG? There are two basic ways (that can be combined): either one learns by doing, usually because we are introduced into a gaming party and start playing right away; or one learns by the book. People designing RPG books must assume that the prospective players may not have a party, so that they'll have to learn the game by the book. In other words, RPG books are also teaching manuals. They work like distance learning tools. Now, designing distance learning books is a craft in itself. There are endless resources on how to do it. I'm sure that RPG designers would be well advised to learn the basics of this trade (they can check the net as a starting point). Some of the things to consider when designing a teaching manual are (3):

  1. Modularity: the content must be divided into modules which must be consistent in terms of size, and logically structured and articulated.
  2. Incremental progression: each module must build on the previous ones, going from the more intuitive, easy to grasp and basic, to the more complex, hard to understand, and advanced.
  3. Formal consistency: the formal aspects of the book, both in terms of outlook, as in terms of structure, should be consistent, so that form does not distract and does not become an obstacle to learning.
  4. Learning by repetition: one must not be afraid of introducing some redundancy in terms of repetition of concepts. Going back at the same things helps consolidate what one is learning. This means that examples are a must.
  5. Learning by doing: people should have the possibility to exercise the issues they're studying, so that they can realize whether they have grasped it correctly.

How does this translate into RPGs? If an RPG book is to help the players in learning the game, it should:

  1. Divide its content in terms of complexity, from less complex to more complex.
  2. Strive for clarity both in terms of text and look.
  3. Be consistent, avoiding contradictions in its content (including contradictions between text and art).
  4. Have clear links between the different aspects it deals with, so that the player can always refer to what's pre-supposed in what he is currently reading, or go back to something he has doubts about.
  5. Have examples that illustrate each topic.
  6. Have exercises, or offer the player the possibility to have a guided hands-on approach to the game.

The first aspect is particularly important. The player should not be required to start playing when he reaches the end of the 200th and last page of the game book. He should be able to play after each section, that way consolidating what he has just learned about the game. This is a feature that is very common in tabletop games: you often have the rules divided into, say, basic, intermediate, and advanced. You have the possibility to game at each level. After you feel confident at a certain level - and the fact that you have playtested that level contributes to that confidence - you move to the next level.

Is this feasible in RPGs? Or are RPGs "holistic", meaning that the parts are only understandable within the whole, so we need to get acquainted with the whole at the outset? Personally, I think RPGs are holistic, but that the "whole" can be looked at at different levels of granularity (do you still remember that Bachelard Concept I wrote about two columns ago?). For instance, one can have a broad, but superficial view of a character, before one moves to deeper levels of character definition. That means that we can design RPG rules by levels of complexity where each level adds to the previous ones by building on these previous levels.

If we take this two ideas - organization based on increased level of complexity, and the holistic nature of RPGs - we get a structure where each structural level covers the different aspects of an RPG, going from simple/more immediate to complex/harder to grasp. Each next structural level will cover the same issues than the previous levels, but adding something not previously covered (or at least not covered in depth).

RPG books as reference books

RPG books are to be used and reused. They are not just simply read and put aside. While playing, players will come back to their trusted game books whenever a doubt arises, or when they need to refresh their ideas. In this sense RPG books are reference books.

To fulfill this role information must be organized in a logical way, keeping together related aspects of the game so that players can easily locate what they are looking for. Detailed tables of contents, indexes, visual reference aids, all become a must.

The criteria to judge on the quality of an RPG book as reference book is how easy information is to find, and whether there are no logical inconsistencies within the book's content. Information does not even need to be organized in a linear pattern. For instance, it can be organized alphabetically, like in a dictionary.

RPG books as toolkits

RPGs are basically tools to foster imagination. Different people vary widely in their imaginative behavior. What's more, each RPG models a certain reality (more or less realistic, more or less fictional), but different people have different modeling requirements. A good rule system should allow for those variances in imagination and modeling requirements. It should allow the player to chose how he wants to model his game's reality, according to his imagination (4).

To do this, an RPG has to be designed as a toolkit where the player can pick what works best according to his tastes. Does he want a detailed combat system, covering all conceivable possibility? He gets it. Does he prefer a simple and straightforward approach to combat? He just needs to drop all the developed rules, and get back to the basics.

Such a game system would be perfect if it ensured consistency among the different levels of play: the player that wants only the basics, and the player that wants to go down the full path of increased complexity can play together and still achieve a consistent game, both in terms of in-setting consequences of the character's actions, meta-setting rules consistency, and game flow.

This is one of the hardest things to achieve. Often it's much easier to identify a given target level of complexity, and to design rules for that level. Rules for specific situations may be added in an ad hoc basis, or left for players' development as house rules. Even when a game has varying levels of rules complexity, it's easier to design it on the pre-supposition that everybody will be playing at the same level.

While structuring a game book as a toolkit the designer must understand that a player that picks the rules he wants to use doesn't want to be burdened with the ones he dropped. For instance, if he doesn't want to use body locations for combat, it should be easy to keep out those rules when the player is using the book, either physically (by putting aside the pages where these rules are presented) , or functionally (by a clear graphical discrimination of the different rules).

Mixed approaches

An RPG designer is not bound to follow only one of the approaches to game design presented above. He may attempt to reconcile several of them. Actually, most designers - or at least the best - attempt to make their books as readable as possible as stand alone products (stand alone in the sense that reading them is an end in itself, not dependent on their usage for a game); easy to learn for new players; and easy to reference.

An example: D&D3ed's Players Handbook (5)

If you open D&D's PHB in page 3 you get a global view of the book encapsulated in the table of contents. The first half of the TOC concerns the presentation of the rules, while the second half is a list of tables. You will also notice from the TOC that the book is organized into chapters (11 to be precise plus an introduction and an appendix), and the chapters into sections (varying from 3 in chapter 1 to 16 in chapter 3). Each chapter deals with a domain of the game presenting all the rules pertaining to that specific domain. There's an index, an appendix with a comprehensive glossary of terms used in the book, and a resum of character creation.

Content-wise, the game follows a mixed approach, with the primary emphasis in character creation which drives the presentation of the different aspects of the game. The general rules for action are incorporated into character creation. After this come chapters to deal with special cases of action: combat, adventuring, and magic. Character advancement is only briefly touched, since this is left to another book (the Dungeon Master's Guide).

What does this tell us? That the PHB is mainly organized with two purposes in mind: as a reference book, and as a learning book. It's not supposed to work as a toolkit. The players are not encouraged to adapt the rules they see fit their playing styles. They are not presented with alternatives, told what to drop according to their tastes, or presented with blank areas where they will have to introduce their own rules. The book tells us what a D&D character is and how to play it, and what a D&D character is and how it should be played is what's in the book. By reading it you learn how to create and play a D&D character. By going back to it you make sure that you keep creating and playing D&D characters. At least the way D&D characters were conceived by the designers of this game.

The main concern is to explain to players what is a character and how a character is developed. Also how to play a character. This is done in a way that attempts to be comprehensive so that the player will get the whole picture as he reads the book. Of course, unless he is a genius in grasping new information, he will not be able to catch it all at the first read. So he may have to come back and forth before he understands and consolidates what he is reading. There are almost no examples nor exercises (apart from the "pick a character sheet and design a character as you read" proposal). We must conclude that, while the notion that the book would serve as a tool for the players to learn the game was not forgotten by the designers, it was not their main focus.

The main driver for the structuring of the PHB was to allow players to find information when they need it. It is supposed to work as a good reference book. I must say that it delivers in this field. The book is structured in a logical way that's easy to grasp. It has many referencing aids (the tables mentioned above). I suppose that the game designers realized that D&D is a complex game. The player needs to learn many concepts, so being able to find information in the book may be a recurrent need, even for experienced gamers. That's probably why reference reigns in the PHB.

Could it be otherwise? Yes, it could. This gamebook could be based on a "teaching first" approach. How to? Maybe this way:

  1. First, by working on the principle that playing a D&D character is something that can be done incrementally, starting simple and adding more and more aspects of the game as the players feel confident about what they already know.
  2. Second, by organizing information according to those levels of complexity.
  3. Third, by exemplifying it, and by providing the players with the possibility to explore their learning as it unfolds.

For instance, the rules could be divided into two levels, basic rules and advanced rules. The basic rules could include:

  1. Chapter 1: Abilities.
  2. A simplified version of chapter 2 with less races (say, dropping gnomes, half-elves, and half-orcs).
  3. A simplified version of chapter 3 with only a selection of classes (maybe cleric, fighter, rogue and wizard).
  4. Skills and feats could be dropped at the basic level.
  5. There would be no need for a detailed list of equipment. Basic characters would have access to predefined packages.
  6. Chapter 8: combat would include only the simplest of combat actions, and would not include (or these would be highly simplified) movement and position, combat modifiers, special initiative actions, and special attacks and damage.
  7. Chapter 9: adventuring, would be included as it is.
  8. A simplified chapter 10: magic, only would include the level one spells that can be used by either clerics or wizards.

I guess that these basic rules could fit in no more than 60 pages. If we add examples and a couple of playtesting modules (maybe playable solo), it could go up to 80 or 90 pages. It would allow players to create simplified characters to learn the basics of the game. Everything else would come latter, when they moved to the advanced rules.

Actually, the game could retain its current structure, but separate in each chapter the basic rules from the advanced ones, so that the player could jump to the basic first, and explore the advanced latter.

I guess you understand where I'm going: there are different ways to organize a gamebook. Each will correspond to the things the game designer thinks need more emphasis. I presented this example only to demonstrate precisely this point.

AB01 - THE ANNOTATED BOOK OF MENDES PINTO VOL. 1 BREAKDOWN

ORGANIZATIONAL CRITERIA

I have a problem. You see, I just cannot make my mind on which is the criteria that I would put forward in terms of organizing AB01. On one hand, I just keep telling me that it must be directed at the new player, someone that wants that book to learn the game. In other words, that the main criteria should be to organize the book according to its self-teaching function. On the other hand, there's something that always reminds me that you only learn a game once, but you keep coming back to the game book afterwards. From this point of view, referencing rules. Yet, there's a third voice that whispers that it's the player that does the game, the book must allow him to adapt it to his own approach. Toolkit it the word this voice keeps whispering.

What to do? Well, I think the ideal would be to satisfy all those voices. But how? Maybe by going down the mixed approach way? Umm, trying to do all at once usually means one ends doing nothing.

In my dreams of grandeur I see a special type of gaming book, a polymorphing book. This polymorphic thing starts as a learning manual; once the player understands the game, the book turns into a toolkit where the player can select what suits his tastes, so that he can use it the way he likes; yet, all of the material is still there, ready to work as a referencing resource when need comes.

In those moments I see a book where information is organized by order of complexity, so that the player learns from the simpler to the harder, building on his gaming experience to move from level to level of complexity. Yet, I see a double system of pagination so that the player may separate the pages and reorganize them according to his will: for instance, he may put together all the rules on combat; select the rules on trade he wants to use, and discard those he does not intend to employ; separate in a binder the often used rules and sections, and put in another binder those he only seldom uses; put examples and practice stuff to one side, fiction to another, and rules to yet another.

This can be done, and I suppose it has been done. The only problem is that it's hard to do it the right way. Really hard. I'll have to stick to something simpler.

PROPOSED BREAKDOWN

Well, I suppose you guessed where I (and many, many RPGs) am going. Back to content breakdown, of course. After all, if setting drives structure, I mean, rules... The organization of AB01 will be done according to these guidelines:

  1. The major sections are based on content: presentation of the game, character creation, playing the game. This will be organized according to its order in play.
  2. A second major organizational criteria will divide the issues according to their complexity, going from basic, through standard to advanced.
  3. Care will be taken to facilitate the different usages of the gamebook, specially for learning and reference purposes.

      In conclusion, the breakdown is as this:

      1. FAST PLAY
      2. TABLE(S) OF CONTENTS
      3. INTRODUCTION
      4. The Asia of Mendes Pinto
      5. Game conventions
      6. CHARACTER CREATION
      7. A quick guideline to character creation
      8. Basic data
      9. Personality
      10. Motivation
      11. Experience
      12. PLAYING IN MENDES PINTO'S ASIA
      13. A quick guideline to action
      14. Social action
      15. Physical action
      16. Combat
      17. Faith
      18. Character evolution
      19. REFERENCE MATERIAL AND TABLES
      20. INDEX(ES)

      Some notes:

      Fast play is a subsection where the players can start to play right away with pre-generated characters. It's like the lite version of other games. Fast play introduces the "basic" rules. The idea is that the players should be able to start playing in less than half an hour after putting their hands on the book. This is to be accomplished either through a solo adventure included in AB01, or through a fast play scenario included in AB02, the GM book. A different question is whether Fast play should be located in the introduction, or whether it could be inserted in the book before the table of contents - in other words, before the game book proper. This is open to discussion, but I'm more inclined to the second solution.

      The quick guidelines in the "Character Creation" and "Playing in Mendes Pinto's Asia" sections are summaries of the standard rules. These subsections serve two purposes: to introduce the rules in terms that can be put into use (meaning, play) right away; to serve as referential condensations of what's in the section.

      Advanced rules I think I'll present the way Skyrealms of Jorune (3rd edition, if I recall correctly) deals with it: as inserts within the normal flow of text, distinguishable from the standard rules because the former are in a gray background. This way the player can read the whole right away, or skip the advanced rules for a latter reading.

      A PRIMER FOR ACTION

      So, I have a plan. But, how do I plan to implement it? The actual order I will follow does not correspond to the order of the final product. Let's see what I intend to do (I've put in italics things that are not mentioned in the above table of contents):

      1. Introduction: The Asia of Mendes Pinto
      2. Chargen: Basic data
      3. Chargen: Physical attributes
      4. Chargen: Experience - Fields of experience
      5. Chargen: Experience - Skills
      6. Chargen: Personality
      7. Chargen: Motivation
      8. Chargen: Motivation- Experience
      9. Chargen: Motivation- Physical assets and wealth
      10. Chargen: Motivation- Social status
      11. Chargen: Motivation- Culture
      12. Chargen: Motivation- Faith
      13. Introduction: Game conventions
      14. The character in action: Physical action (different columns for the different experience fields)
      15. The character in action: Social action (different columns for the different experience fields)
      16. The character in action: Combat - melee
      17. The character in action: Combat - weapons and armor
      18. The character in action: Combat - damage and healing
      19. The character in action: Combat - war
      20. The character in action: Faith
      21. Character evolution
      22. Introduction: Fast play
      23. Chargen: A quick guideline to character creation
      24. The character in action: A quick guideline to action
      25. Reference: Summing up tables
      26. Reference: Further reference material
      27. Reference: Index(es)
      28. Reference: Table(s) of contents

          Of course, I may deal with several topics in a single column, and deal with a single topic in several columns. And I may change the order as the columns unfold... It's called project management babe!

          Srgio


          NOTES

          (1) Or one should. It's incredible how even some of the more talented people in this business can shoot their feet despite years of experience. Take, for instance, Hero Wars, a game that will be referenced several times in future installments of this column: designed by Robin D. Laws (reputedly among the best designers in the New Generation) and Greg Stafford (among the best in the Elders Generation) it should be flawless. It isn't. Just the contrary.

          (2) This is specially true given the way I'm envisioning the rules. But I'll leave this for future installments of this column.

          (3) I was a professional bank trainer for 10 years in an institution that specializes in distance learning. I worked on the development of some training books. I had to learn something about that business...

          (4) you may wish to go back to column 1 where I discussed this in terms of the design matrix there presented.

          (5) Why D&D3ed? No, not because the evil powers of Hasbro/WotC are corrupting this column. It just happens that when I relocated to India I was not able to bring my RPG collection with me. Later D&D's PHB reached my home in Portugal and someone brought it here. I'm using the PHB because it's one of the few RPG books I have with me, that's all. And because, as I hope to be able to demonstrate, it makes an excellent example.

          TQo0~^DҒt< ek&Ǿ$\۵ZFȃuwݝIŃU QYir2HR2.u3MFoعq]4#A`pP5(b& )b)ⰾp7(i<[-2gL#5[f g?*rVGf8*)s'+20ϟ̑F}KB<7wSL\gbvm9WiRބYŜvd y0'p2I_Fc2>#o A )VL[Qk?3`)<У[(*W.JH ?tXCt谙 X:@ \0w ~LqĤE-rFkYœj4q 5AQ6[AxG [>w|?( fХθY䝛$c=_qNĦoǸ>O_|&/_Mi7"宥CЧk0dӷLh;TmuCGU-!Ul{ h<\bQX.~"O2*yPcz!ŠGg

          What do you think?

          Go to forum!\n"; $file = "http://www.rpg.net/$subdir/list2.php?f=$num"; if (readfile($file) == 0) { echo "(0 messages so far)
          "; } ?>

          All The Travels of Mendes Pinto columns by Sergio Mascarenhas

        1. Not Dead Yet by Sergio Mascarenhas, 18jul03
        2. Still Struggling With Section 4 by Sergio Mascarenhas, 07mar03
        3. It's Time For Combat by Sergio Mascarenhas, 31jan03
        4. The Criminal Always Comes Back to the Scene of the Crim by Sergio Mascarenhas, 31dec02
        5. Tahahahahime Is On My Sahide! Yes It Isn't! by Sergio Mascarenhas, 07nov02
        6. Character Creation for Dummies by Sergio Mascarenhas, 08aug02
        7. Thus Do We Start by Sergio Mascarenhas, 01jul02
        8. Can You Give Us a Descriptor of the Subject? (Part II) February 21, 2002
        9. Can You Give Us a Descriptor of the Subject? (Part I) December 6, 2001
        10. Time for a Hiatus October 23, 2001
        11. System as Language September 27, 2001
        12. Don't Forget the Damn Index! August 30, 2001
        13. R-O-L-E-P-L-A-Y-I-N-G  G-A-M-E  C-O-R-E  R-U-L-E-B-O-O-K.&nb\ sp; UFF! July 26, 2001
        14. Who is this Mendes Pinto, Anyway? June 28, 2001
        15. Once Upon A Time ... (How It All Started) April 25, 2001


          All Ruleslawyer For Free columns by Sergio Mascarenhas

        16. Experience: From Fiction to Roleplaying Games September 11, 2000
        17. The Applied Experience Curve Concept June 26, 2000
        18. Experience Curves May 30, 2000
        19. Trait Curves March 28, 2000
        20. A Change of Course November 28, 1999
        21. Spotlight on Alternacy, A Roleplaying System October 26, 1999
        22. Introduction September 21, 1999

          Other columns at RPGnet

          TQo0~^DҒt< ek&Ǿ$\۵ZFȃuwݝIŃU QYir2HR2.u3MFoعq]4#A`pP5(b& )b)ⰾp7(i<[-2gL#5[f g?*rVGf8*)s'+20ϟ̑F}KB<7wSL\gbvm9WiRބYŜvd y0'p2I_Fc2>#o A )VL[Qk?3`)<У[(*W.JH ?tXCt谙 X:@ \0w ~LqĤE-rFkYœj4q 5AQ6[AxG [>w|?( fХθY䝛$c=_qNĦoǸ>O_|&/_Mi7"宥CЧk0dӷLh;TmuCGU-!Ul{ h<\bQX.~"O2*yPcz!ŠGg