Tags in Drive·10 make up all the cool traits, powers, skills and features a character can have. When I set out to design the framework, I decided that instead of trying to make a large, encompassing list like we’ve done with other games, to instead create a simple guide to how Tags operate at the meta level. I took inspiration from systems like Fate and Savage Worlds in that I wanted someone to easily skin and translate whatever it is they’re wanting for their character into a game mechanic in a moment’s notice.

A quick recap of how Tags function in Drive·10

• Tags come in two categories: Character and Equipment. Character will remain on them, Equipment can be lost, traded, bought, stolen, etc.
  
• There are three styles of Tags: Functions, Edges, and Boosts.
  
• A Function establishes something the character can do that normally they cannot. Wings allow them to fly, Telepathy lets them read minds, a Grappling Hook lets them climb walls, etc. Most functions are always available to use, but more Powerful Functions will require limits on their use.
  
• An Edge enhances or improves a character’s odds performing certain actions. Muscle Augmentation gives an Edge towards any checks of physical strength; a Charming character may have an Edge socializing.
  
• Lastly, a Boost is a straight up modifier on specific action rolls. These were implemented as a form of character skill (like Intensive Marksman Training) or aid from equipment (a High-Powered Laser Sight would assist aiming on firearm attacks.)

Arbitrating Functions

Although Functions can be simple in theory, they can sometimes be complex in practice — it’s easy to say, “My Wings let me Fly!” or “I can shoot lasers from my eyes” but in game terms WHAT DOES THAT MEAN? The GM and Player will need a dialogue to discuss limitations, based on the themes and scale of the campaign. The GM will need to draw the line between where a standard function and a Powerful Function (one that needs a limitation added to it) exists.

What follows is my default guidelines for what a “standard” Character Function may do in my games:

• Movement: Any function that affects movement by allowing the character to traverse in ways that others normally can’t — flight, wall crawling, instant teleportation, natural swimming — does so at a normal pace (so, moving to a Near location, or a Far one as a full action.) Alternately, allowing faster naturalmovement (allowing twice the distance covered in a Turn) can be a standard Function.
  
• Attacks: Features like natural weapons (spikes or claws), spells (magic missiles and lightning bolts), or any other crazy attack that a character wants attached to them I gauge like any other weapon: one-handed attacks are Light damage, two-handed are Medium. If no hands are used, I judge it by any gestures or body motions that need to be done to activate it. Ranged attacks are almost always Light; Medium ranged attacks may be limited in requiring the character to not move on their Turn. Heavy Attacks, or any attacks that target multiple foes in an area, I treat as Powerful Functions.  
  
• Armor: Much like Attacks, I arbitrate any armor tags on a character much like I would equipment: Light Armor is easily hidden (thick skin that other wise looks normal? Subdermal plating?) Medium Armor is spotted immediately (thick scales? Bulky external bone plating? Glowing Force Aura?). Heavy Armor is not only bulky, but cumbersome (huge tortoise shell or exoskeleton? Steel body?) and makes all movement and stealth checks Challenging.
  
• Cool Tricks: A Character Tag makes them stand out, and a lot of times I just let my players come up with cool features or tricks without enforcing limitation.  I’ve allowed characters with tags like “High Reaction” or “Danger Sense” that allowed them to act first in combat (acting at the same time as any others with similar tags, of course.) Enhanced senses like Night Vision, or Improved Hearing affect how they interact with their surroundings, but don’t necessarily need a mechanical change.
  
• Background Titles & Resources: Some Functions are simply to establish an important fact that gives the character a leg up in the setting. Titles like “Born of Nobility”, “Renowned Hero of the Village” or even “Bar Owner” can do a lot for the character. You can establish resources like “Rich Uncle’s Inheritance” or “Stockpiled Arsenal”, as well important NPC connections: “Friends with the Mayor”, “Black Market Contact” or even a Sidekick NPC (usually treated as a Mook or Minion.)

Powerful Functions are more amped up, and the GM is encouraged to restrict them as they see fit. The easiest way to do so is limit it either per scene (or per episode). There may be other quantifications, such as “between full rests” or by spending a resource of some kind like Mana or Energy.

• Attacks: Heavy attacks, or attacks that can affect an area, I usually declare as a Powerful function. 1/Scene is my base limitation, but if the area is larger than those Near the target point,
  
• Movement: Anything that beefs movement beyond the standard scale (such as individual moving as fast as an automobile or plane) either should be assigned a resource pool or a maximum number of uses a day (assume 1 use = 1 scene). Also, any ability that transports a group of characters a great distance should have limitations.
  
• Automatic Attacks & Defenses: CarPG (which Drive·10 is forked from) had a lot of circumstantial tags that allowed a free successful attack or defense once per combat/scene, and I’d allow these at those limits. You would have to specify the type of attack (melee, ranged, magic, etc) that you inflicted/defended, and were usually given in addition to your action on a turn.
  
• Background Resources: It’s one thing to say you stockpiled an arsenal of personal arms… it’s another to say you have access to a tank and rocket launchers in a suburban setting. All because you can call for back up from an allied street gang doesn’t mean they’d drop everything to come help in every combat encounter. Don’t be afraid to limit these to 1/day or 1/Chapter or Episode.  

Edges vs Boosts

I’ve been asked about how to arbitrate between labeling a Tag as either an Edge or a Boost. Although the operate differently, they both result in providing a bonus towards succeeding a task. The big thing to remember is that Edges can be advantageous towards several actions, while Boosts were meant to hone a specific action in the form of specialized training or equipment for a task.

• Edges allow the character to roll two dice, take the better result.
  
• Boosts are a flat +1 Modifier (+10% odds).
  
• Both can be applied to the same roll.
  
• Edges technically have the better odds overall; average characters (Attribute + Vocation = +5) have a 14% better chance of a normal success (vs 10) than just applying a Boost, but those odds diminish on higher results.
  
• Boosts do have a few pros, however: for starters, opposing Edges cancel each other out. Boosts are static modifiers. They also raise the maximum result of a roll — on tasks that depend on the Degree of Success like combat or opposed tasks, every +1 helps. Not to mention, Boosts can stack — you’re allowed +1 from both a Character Tag and Equipment! So, our example above of the Marksman Training and a High-Powered Laser Sight would be a cumulative +2 to the roll.

In short: take an Edge if you’re wanting to perform better in an particular area or field, take a Boost if you want to be better at a specific action or skillset — especially one tied to your Vocational statement. And by all means, do both!

Linking Tags: Anchors & Tethers

Running such a free-form, arbitrary system can leave new players feeling overwhelmed when it comes to deciding what kind of Tags they want for their character. One practice I’ve mused on for some time is the approach of “Anchors and Tethers”. In short: use established traits as “anchors” and tether off new ones from them. During character creation, you already have a strong anchor: your core Vocation statement.

There’s a brief mention in the D·10 core that was much longer in the original draft, stating that tags can be linked together. The example I gave was equipment based: a rifle with a high-powered scope. In game terms you could break that down as a Medium-Ranged Attack function (the Rifle) with a Boost (the scope). This can also work for character tags — those Wings of yours establish flight, but you may tether another tag to them, one like Dive Bomb that says you have an Edge when attacking a ground target from above! Or Escalated Speed to give you an Edge in flight-based chases.

Setbacks

All talk of Tags so far has been positive features, but what about “disadvantages” or negative traits? I primarily kept those out of the core because I feel systems that offer the exchange of negative traits for positive ones wind up being gamed for ridiculous builds instead of interesting character developments.

But that said, we’ve always house ruled an exchange of benefits for Setbacks. A Setback is a negative tag, which may or may not have a penalty effect in terms of game mechanics but will always provide an obstacle to the character. Like any other tag, a dialogue between the GM and Player to gauge severity and the degree trade in will be important. Some Setback ideas:

• Cybernetic Aversion: Characters in a cyberpunk setting have a hardcore phobia of being augmented, even when it comes to things like nanite treatment for faster healing. Characters with cybernetic aversion may gain two extra Boosts.

• Allergic to Silver: A character born of a Werewolf bloodline, who is slowly developing their powers, has inherited the supernatural weakness against Silver. Any weapons or attacks made with pure silver are treated as Heavy damage. These wounds cannot be healed with supernatural healing of any kind. In exchange, the character may take an extra paranormal Tag related to their heritage.

• WANTED: Someone, either a powerful individual or organization, wants the character found (and possibly killed). Flyers and advertisements are posted everywhere, and there’s a big reward. The character may be able to function under the radar but it’s a constant nuisance that interferes with the entire party at inopportune times. The GM and Player agree that at any time, the GM can randomly have NPCs recognize the character, or be in a position where they may be in danger because of the wanted status. In exchange, the player may earn a “luck” token from the encounter, which they can use to re-roll after failing an action test.

+++

I hope this article was helpful in the further explanation of Tags, and gave some inspiration on how to approach them in Drive·10. Even if you’re not a fan of the arbitrary nature of the game, you could use this as a framework to create a list of tags appropriate to your campaign.

Remember that the Drive·10 framework is released under Creative Commons BY-SA 4.0, meaning you are free to take these ideas and use them in your own work (so long as you credit us and share alike.)

Haven’t checked DRIVE·10 out yet? Grab it on Itch.io!