Entry 20: Team Spirit!

19. November 2009 by admin.

.::: Entry 20, 2009/11/19 :::.
Roleplaying is a team sport. Yes, there are options for one-player-one-GM adventures out there, and there are even experiments with solitary games (in the spirit of the old Fighting Fantasy books, often). But the intent with the game being created here is fun for the whole group.Oddly enough, while this idea of characters working as teams (typically called a ‘party’) is fairly old, the focus is still very much on individual characters. Most parties quickly become plug’n'play, in that new party members are simply snapped into the group and function with no greater change over time. This always felt odd to me, and I have been paying close attention whenever articles or game mechanics have dealt with the idea of the characters as a coherent group. I want that to be a part of my game, and have experimented a lot with it.

:: The Party Sheet ::

An idea that has popped up its head over and over through the decades I have known this hobby is the idea of having a Party Sheet, which serves the same function for the party as a Character Sheet does for each individual character. Various games have tried various angles on it, but the ones that succeed best are (sadly, in my opinion) the ones that are almost entirely focused on combat; it is simply a powerful and game-compelling gimmick to provide tag-team tactics in combat, allowing special weapons bonuses or unique attacks or defenses when acting as a group. Moreover, it’s logical, because history has shown an unbridled creativity in military units for applying the advantages of numbers in a fight.

The combat angle is thus a no-brainer. Advanced combat will have special tricks and maneuvers, and having some of those require multiple participants is only sensible. That will be included. But I want the team aspects to reach far beyond combat, since combat is not central to the game.

What becomes the next question is what a group has going for it that is not immediately derived from individual members. The combat maneuver concept can theoretically be expanded very broadly, from courtroom assistance (why else would someone have a legal team instead of just a good lawyer?) and research teams to the classic ‘wing man’ approach to everything from dating to elaborate cons. The notion of two or more characters being able to rely on each other to such a degree that they are each stronger in the group is very fundamental, and should be taken advantage of.

But even beyond this idea of two heads being better than one, there are several collective advantages a group might have, which does not require everyone to be doing the same thing. Good leaders and planners only require the group to pay attention to gain from them, certain kinds of gear depends on multiple users to be truly efficient (”yeah, the mainframe is ridiculously big for a computer, but when you have two dozen users on, it’s a fraction of the cost and ten times more powerful than the best computers on the market!”), and complex lay-ups between different positions can make for impressive results (one car knocking the target into the scope of the sniper who can slow it down for the second car to powder it, for example).

A party sheet could hold the maneuvers the characters use as a team, putting the complex interactions together in one place rather than on every single character sheet. The base abilities and such used by each character would still be on that character sheet, but the greater whole is hard to see without a central description.

:: Unified Image ::

Other than what is going on in the party itself, the surrounding world might also have something to say on the matter. Many teams are known as teams, not as individual characters. This goes from legendary law enforcement units to rock bands to acrobats. Meeting one member is interesting, but for the full effect to work, all or most members must be present. A company might not hire individual members, wanting the entire team. Or a gang of criminals might not even be recognized one by one in the streets!

To further cement this, there are plenty of official teams that are required to be collectively present to be accepted. Many military, legal or similar teams cannot be admitted to resources or be given orders or even assistance without proper presence. In some cases, it is a matter of individual team members being formal representation for the team; one member is responsible for strategic communications, one is the equipment acquisitions officer, and so on. A full team has all the access they need, an incomplete team does not. If there are special skills involved, this is even more profound; nobody in their right mind issues heavy explosives to anyone but the demolitions expert, for example.

There are a lot of interesting options beyond that. A team might be known in a certain way by some people, in another by others. This need not be a matter of secret identities (rock band by day, crimefighters by night, for example), but being seen as one team in one place and another elsewhere is possible. Inside city limits, a military unit might have the role of search and rescue, and the functions of team members can be turned around greatly. A team of technical experts may likewise changed greatly in roles when negotiating with potential clients. In this fashion, one team can be many different teams, and not all members need to be on every version of the team; the new member might be part of the adventuring team, but he has no actual role in the guild enforcement team that the others have been with for a long time. People in general will recognize him as part of the legendary adventuring team, but the guild will not accept him, not yet at least.

:: Team Resources ::

For whatever reason, a team might only have access to certain resources as a team. Joint accounts, split passwords, and other methods can make it impossible for one member to grab gear without the others. When the gear is out of this restriction, it might work like any other, or passwords etc. may be continually required.

One type of team resource is the kind that actually requires multiple operators. The traditional example is a giant robot or advanced spaceship. The usual idea is that the skills required are fairly unique, and collective timing is of the essence. In other words, this exact team is needed to operate it.

More exotic versions include magical rituals that take multiple participants, psionic mass-mind gestalts, robots joining up, or even complicated weapons (or other gadgets!) capable of being merged. The idea is that multiple team members are needed to tap into these things; with only one or even just too few members, the act is either not living up to its full potential, or it simply won’t work at all.

There are plenty of ways to simulate all these things in a game, depending on what exactly is simulated (someone giving a team access, things being used as a group, etc.). What is important is that the abilities or other things involved explain this, making it not just a ‘random requirement’, but letting players build this team cohesion into their characters from the start or along the road. The point is to make the team possibilities a part of the characters, not just something that happens to show up along the adventure.

:: Teamwork Abilities ::

There are already several game mechanics in the second draft that can be used to build team concepts into characters, perhaps even create the foundation of a ‘party sheet’ (or several, depending on how the concept is used; different situations may mean they form a different team, as already mentioned). The most immediate option is to make other team members a Specific, perhaps so that it depends on which team members; too many is a problem, as are the wrong! Some method of defining the advantageous team structures will be needed, to make it work well.

Also, there is plenty of opportunity to make Abilities team-dependent. Some will be only part of a major job, like the character who is an ace at making the spaceship engines work at maximum capacity, or the one who acts as the energy conduit of a large ritual. These abilities may well function only or mainly (or just most dramatically) when the character is handling a certain position in the team. For advanced topics, position-specific abilities (and disabilities, gear, etc.!) can be commonplace, opening whole new frontiers in that field. Some combat only works in groups, as do certain social situations, business negotiations, technical work, and so on.

:: No I In Team ::

Of course, one of the chief tasks of teamwork is still to make the players work together. Even if the game is built on dramatic scheming and infighting, roleplaying is a team sport, and methods of making the group want to play together are very valuable. Having a ‘team personality’ set from the start can make the game much more enjoyable and preempt some problems. The players may be friends, but how are the characters as a group? How do their mentalities match up? Having this in writing gives a way to play the game and stick together through drama and challenges.

This is what I want. The mechanics may be little more than a few guidelines on that angle, but making sure playing together increases the fun makes the game a better collective experience. Players wanting to play together makes everything better for everybody, after all!

Posted in Robots, Teams, Reputations, 'Party Sheet', Old blog, Magic, Combat, Conflict, Vehicles, Weapons | 1 Comment »