I'll talk in this article about the content of the cards, and how years of compromise and trial and errors have led to a wording jungle.
Genesis
Jyhad was the third CCG created, and the second CCG by Wizards of the Coast. Magic: the Gathering had been a tremendous and unexpected success the year before, and it gave ideas to many game companies, resulting in the launch of more than 40 CCGs during the years 1994-1995.
It's easy to understand that given the short delay for the creation of Jyhad and the youth of the CCG, many design mistakes or bad choices were made, especially in the wording of the cards and the rules. Among others, we can list:
- inconsistency (card A and B have a similar effect but use a different formulation)
- word bloat (an effect is described lengthily)
- bad use of existing mecanism unused mecanism (the "paralysis" keyword)
- missing mecanism/patterns that were added later ("during X, do Y")
- unclear/ambiguous formulation
V:TES had most of its cards rewritten at least once, but I doubt of the existence of tablets of the law: a detailed and consistent wording guideline (or at least a document complete enough to produce consistent card text).
Some terms were never fully abandoned despite their obsolescence ("destroy equipment"), some sentences are redundant with the rulebook ("If a card would give the ally blood, give the ally life instead."), reminders are sometimes written between parenthesis, sometimes not ("no cost is paid"), some mecanisms such as triggers or replacement effects are not clearly identified, and some terms were used interchangeably ("get"/"gain", "put"/"place", "may"/"can").
I wrote such a detailed guideline with the support of Pascal Bertrand, the rule directory, covering general rules and special cases (eg. the cardtext to use for a Hunting Ground), which is publicly available on the V:EKN website, and which is opened to remarks and changes.
The process was iterative:
- pick up a card with a confusing or inconsistent wording
- fix it
- write down the rule
- apply the rule to all the cards
- proceed with the next card.
Original | Revised |
[qui] Strike: 2R damage; only usable at long range. Damage cannot be prevented. [QUI] Strike: 3R damage; only usable at long range. Damage cannot be prevented. |
Only usable at long range. [qui] Strike: 2R unpreventable damage. [QUI] Strike: 3R unpreventable damage. |
or Kherebutu (Mummy):
Original | Revised |
Unique mummy with 3 life. 3 strength, 2 bleed. Kherebutu may play cards requiring basic Necromancy [nec] as a vampire with a capacity of 3. If a card would give him blood, give him life. If he is burned, shuffle him into your library. (D) Burn Kherebutu to burn a Tremere with a capacity below 5 controlled by your prey. |
Unique mummy with 3 life. 3 strength, 2 bleed. Kherebutu can play cards requiring basic Necromancy [nec] as a vampire with capacity 3. Kherebutu can burn himself and a Tremere with capacity 4 or less controlled by your prey as a (D) action. If he is burned, shuffle him into his owner's library. |
The updated cardtext is also available on the V:EKN website, in the Card Lists menu, under the name "Revised Card List". There's probably still work to do to complete it, and some complicated rules (eg. those dealing with digits or word numbers) could be simplified.
V:TES uses very little rule-keywords (and a lot more of symbols) compared to Magic: The Gathering, prefering instead verbose formulation. Without adding new keywords that would make the game even harder to learn, those formulations must be very clear and consistent.
I'll talk now about another problem related to the genesis of the game.
The original sin, or V:TES schizophrenia
V:TES is based on a role playing game and was designed to reflect the World of Darkness. Players are Methuselahs, counters are blood, cards are burned and go to the ash heap. This sounds cool and really catches the spirit of the world of darkness, until you realize that Methuselahs are vampires controlling vampires. That creates an interpretation breach in the rules because Methuselahs are not vampires game-wise, mind you. The same way, vampires are minions, but not like mages, mummies etc. who are allies. Some of those allies can play cards "as a vampire" though. Imbued are also allies, but they work half as vampires, half as allies.So, V:TES has strong roleplaying components based on realistic and imaginary elements, but is also a card game that must have strict logical rules. Dogs can ride bikes (per rule), but mortals can't burn blood, only life, or can't diablerize vampires (per rule, derivated from the WoD background). Among the other background elements that translate to cards, we could mention stakes that send vampires to torpor, daylight that causes aggravated damage and the like.
Now, that we know that everything is a bit mixed up and complex, we hopefully rely on the fact that cards explicitely refer to allies when they don't work against vampires, and never refer to vampires when they affect Methuselahs. Imbued required the errata of a few cards (such as cards that put counters on uncontrolled vampires).
Now, let's take a short moment to look at the following cards:
So, what is the common denominator between those cards?
They all share the same major flaw: at some point, the rules were forgotten and the roleplaying aspect took somehow precedence on them. The designers had in mind that you manipulate vampires that do things for you, but who really played the cards had never been considered from the start in the designers' mind. You play the cards from your hand, but sometimes on your behalf, sometimes on your vampires' behalf. And sometimes a mysterious third agent, known as "environmental" enters the garden of Eden.
For instance, Bum's Rush is played from a vampire's perspective, since a Methuselah can't enter combat. But the effect of Art Scam has sense only from a Methuselah's perspective, since vampires can't gain pool. Betwitching Oration was switched from "Gain 2 votes" to "This acting vampire gains 2 votes" since both Methuselahs and vampires could gain vote, and the distinction had to be made.
There were plenty of questions when Outside the Hourglass was released: is the damage inflicted by the vampire, in which case it counts in playing Disarm, or is it "environmental" like Carrion Crows'? Since "minion cards are played by the minions (vampires and allies) the Methuselahs control" (rulebook), the damage is inflicted by the vampire because it uses an active form. Carrion Crows states "The opposing minion takes 1R damage" which is a passive form, so it's not the minion, nor the Methuselah (the mysterious third agent). This isn't clearly stated by the rules though, and relies solely on logic.
On another level, damage from Retribution is also inflicted by nobody, and even if there's an active form used by Archon Investigation, it's hard to tell whether it's the Methuselah that burns the minion, or the game system. It's left unclear, which can work as logn as there's no other card or rule interacting with that subject, but unclear parts are bad in a rule system.
Abbot is hard to read from the vampire's perspective since it refers to the vampire as a third person, contrary to Bum's Rush or Outside the Hourglass that make the vampire the subject. Mind Numb refers to the "controller", but the last sentence "your next untap phase" must be read also from the controller's perspective as minion cards played on other minion become controlled by that minion's controller, and no longer by the player who plays it.
This leads to convulated formulations involving distinctions between this and that, inference about who plays the card etc. that have never been resolved elegantely.
As I wouldn't raise a problem without providing a solution, I've thought about a new way of expressing the perspective.
A proposal
Cards can be played by minions, or players. Let's use:- the first person for the minion that plays the card ("I")
- the second person for the Methuselah that plays the card ("You")
- the third person to refer to another vampire or player ("That vampire", "That Methuselah")
For instance:
Card name | Original text | New text |
---|---|---|
Bum's Rush | (D) Enter combat with a ready minion. | (D) I enter combat with another minion. |
Art Scam | Gain 2 pool. | You gain 2 pool. |
Betwitching Oration | This acting vampire gains 2 votes. | I gain 2 votes. |
Outside the Hourglass | Inflict 2 damage on the opposing minion. | I inflict 2 damage on the opposing minion. |
Retribution | The chosen minion takes 3 unpreventable damage. |
unchanged
or
You inflict 3 unpreventable damage to the chosen minion. |
Archon Investigation | Burn the acting minion. |
unchanged
or
The acting minion is burned. |
Abbot | Put this card on this acting Sabbat vampire and untap him or her. This Sabbat vampire gets... | Put this card on me and untap me. While I'm Sabbat, I get... |
Mind Numb | [pre] (D) Put this card on any untapped vampire. Tap that vampire; he or she does not untap as normal during his or her controller's untap phase. Burn this card during your next untap phase. | [pre] (D) I put this card on an untapped vampire and I tap that vampire. He or she does not untap as normal during his or her untap phase. Burn this card during that vampire's next untap phase. |
Yes, I know it looks weird (as with many new formulations), but let's consider the pros:
- if you take a deep voice when reading the card out loud, it gives a dramatic effect to the game. More seriously, it becomes easy to know from whose perspective the card is read.
- it's a way of getting rid of most of the "he or she" / "his or her" / "him or her" inelegant formulations (resp. "I" / "my" / "me") when refering to the minion playing the card
- it saves space; important words are less likely lost in a noise of "he or she"
- "That" would then uniquely refer to a third subject, avoiding "this"/"that" subtle distinction
A change of perspective
The second problem (that is related to the first) is that cards can change perspective. Let's focus on Mind Numb, and let's say it's played by A on B:- A puts the card on B
- A taps B
- (B controller's now control the card.)
- B does not untap as normal during B's untap phase.
- The card is burned during B's untap phase.
The first two effects are read from A's perspective. But as soon as Mind Numb is in play on B, it becomes controlled by B (per rule), and the last two effects are read from B's perspective.
One of the major drawback is that it makes card harder to understand when read. "Your untap phase" must not be read from the acting vampire's controller's perspective, as it would be if put at the start of the card text.
One of the solution is to introduce a new term for simplicity, and using paragraphs:
Attach: to put a card on another. Both cards are considered attached to each other.
I chose this term as it's neutral, contrary to "Curse/Bless" or "Affect", and works both way (attached minion / attached card).
Using paragraphs works well with the change of layout proposed in the previous article, since inferior and superior effects are separated by a line, making paragraphs usable without confusion.
Mind Numb would read (using both proposed changes):
[pre] (D) I tap an untapped vampire and I attach this card to him or her.
Attached vampire does not untap as normal during his or her untap phase. Burn this card during the attached vampire's next untap phase.
Abbot would read:
+1 stealth action. Requires a Sabbat vampire.Abbot could state "As long as I'm a Sabbat vampire, I get +1 intercept" etc., but it would break consistency with other "attach" effects that all use the 3rd person.
I attach this card to myself and I untap.
Attached Sabbat vampire gets +1 intercept against (D) actions directed at his or her controller. A vampire may have only one Abbot.
As a consequence and a matter of consistency, vampires' card text would also be changed to the first person;
Beast, Leatherface of Detroit:
Sabbat: I cannot play action cards. I cannot have or use equipment or retainers. I can enter combat with any minion as a (D) action. +1 strength.Please notice that it shortens vampires' text, which is good because there isn't much space for it, and it removes any self-reference (and any existing ambiguity, hello "Lord" Tremere), or references to gender (hello Sascha Vykos).
The same thing goes for allies:
Ossian:
Unique werewolf with 4 life. 2 strength, 0 bleed. Red List.Equipment and retainers wouldn't be changed, as they are not minions, and refer to the bearer or employer.
I can enter combat with any vampire as a +1 stealth (D) action. In the first round of combat with a vampire who has played a card that requires Auspex [aus] during this action, that vampire cannot use any maneuvers or strikes. I gain 1 life at the end of each round for each blood the opposing vampire used to heal damage or prevent destruction that round.
Master cards wouldn't be changed, as they are played from the Methuselah's perspective and already use "you".
In this article, I've talked about the content of the cards and the wording, in the next article I'll discuss about the rules of V:TES.
This is an extremely interesting idea! I think it's clear to everybody that the wording of VTES cards is a hot mess, but your suggestion of how to improve it is the most innovative I've run across. I must admit that I didn't like the first person text when I first read it, but the more I think about it the more I like it. I hope that if VTES is ever reprinted, strong consideration is given to your proposed language. Thanks for the post!
RépondreSupprimerThanks, I hope others will be as receptive!
SupprimerAny reason why vteslib.csv seems to have a load of random {} ?
RépondreSupprimerAt first I through it was to denote bold, however that's obviously not always the case:
"Weapon{:} gun.
{Strike:} 2R damage{}, with {1} optional maneuver each combat.
[myt] {Ranged strike: s}teal 1 blood.
p}ay half the cost {}round{ed} down{} of the equipment. This vampire {can} enter combat with any vampire{}
The above are just a few examples of seemingly random {} — some like {can} make sense. This is from vtescsv_utf8_revised.zip — any chance it could be corrected?
vtescrypt.csv is affected in a similar way.
{} indicates parts that have been rewritten (compared to the latest printed version), it's perfectly normal. Bold format is not indicated, it is inferred from the text structure. If you want a clear version, you just have to remove all {} characters.
SupprimerGreat; thanks for the clarification.
SupprimerThis is a very precise and well-thought proposal. Hope it will be accepted too in case of a reprint. As Brett, I was a little bit rebuked by the first person idea, but it does indeed make a lot of sense and it is both very clear and compact. I would get used to it pretty fast :-)
RépondreSupprimer