One thing that exhausts trans people and wastes a lot of their time is explaining Some Of The Most Basic Stuff. I try to make sure I offer some basic explanations of things, not because I have special insight, but just as a basic footing. And this time, we’re going to real quick talk about how you, a cis boy, should approach talking to your trans boy friends, about their boobs – not boobs in general, but their boobs, this is important.
Some notes about writing and notebooking in the
body of a book as it pertains to fluid thinking
once you get into the habit of thinking of ‘who
told me that,’ you’ll start verifying ideas, of ‘to
me, this makes sense,’ becoming less common.
The problem with much of us these days, with the
world, is a feeling of emotional certainty about what
is not necessarily true or even scrutinised. I’m
gunna admit my own habit of accepting ideas that
roll with how I already think, ideas that tell
me, ‘you are doing okay’ and to be honest
I don’t think that’s necessarily an evil. You
ain’t going to stop your brain doing it, so
the next best thing is to refine your responses to the
sharpest point possible to look at reflection as a
tool for critical self-engagement to make it
in an otherwise unexamind and uncritical world.
The next thing to do is examine the first word on each
this was originally written at MOAB, hand on paper
A draft refers to when players make exclusionary choices from a common pool; you’ll see this sort of thing in professional sports to determine where players wind up. In card games, however, a draft usually refers to a mechanism where players each are given a handful of cards, choose one card, and remove it from the hand, then pass their hand on to the next player.
Draft based on cards can put complexity on the cards themselves, rather than in the fundamental structure of the game; the game has a really simple rule of Take A Card, Pass Everything Else Along. That means players can focus on just the cards in their hand, that they can select from, and not need to worry about what else is going on at the table (though they might).
Draft is also simultaneous: Players will all be taking their turn at the same time, meaning that even if one player is markedly slower than the others, players won’t be waiting the entirety of their decision making process, since they have to do some of their own decision making process.
Draft is a super duper complicated way to design your game. In the case of a bigger game where draft is used as a component, like Magic: the Gathering there are thousands of words written every month or so about ways to do it well, strategies for repeating the same game, things you can do to handle the variance and things you can do to capitalise on it.
Players get to see a bunch of the cards in front of them; they get to know what they’re passing, and that can mean that players seeking an edge may feel obligated to remember everything going around the table. You can find this a bit paralysing.
You can make drafts open, where everyone makes it clear what they’re taking each turn, which gives players even more information, and may be even more paralysing. If you do this it’s often best to have a common pool that everyone takes one thing from at a time. I’m less fan of this but it can be a good way to make players hold grudges against one another.
Some drafting games include Magic: The Gathering’s limited format (known as draft, helpfully), 7 Wonders, and Inis.
Recently, I was listening to the Ding and Dent podcast which decided to take a momentary sidetrack into the idea of innovation as its importance to games, and it got me angry enough to sit there and froth at my computer for a little bit and write a very angry, very foolish draft.
Fortunately ‘recently’ means mid August because I try to write ahead on this blog these days, and that meant I had time to cool down and relax on the stance and come back to it to talk about my problem with the position.
So here’s the thing with innovation. For something to be innovative, it needs to be, in contrast to other examples in its type, different in a new way to overcome a challenge. The problem with describing things as innovative is that it inherently positions the speaker as an authority on what is a meaningful contrast.
The thing most people mean when they say innovative is novelty. They mean this does something in a way I hadn’t considered. Why does this give me a bee in my bonnet, though?
Because games are so broad, so wide, happening across so many languages and so many markets right now, the idea that any given thing is innovative means that the games that the speaker understands must be the ‘normal’ that exists. That a reviewer – usually of big box board games from four or five publishers – has a lens that encompasses all the games that are worth considering and therefore, what is new to them in that space is innovative.
This is an important thing to consider!
I prefer instead to talk about novelty – which is to say, this is news to me – because it avoids unintentionally positioning the speaker as an authority, and it helps push back against the idea that the small core of games being examined by reviewers are the general landscape of games.
This started out as at first, a treatment of the evolution of the rules of Psionics in dungeons and dragons from its inception through to its incarnation in 4th edition, with an eye towards showing how you can respond to mechanical restructures, but it quickly became clear to me that that was both too huge an undertaking and also one I wasn’t all that qualified for. See, I can tell you about 3.5 and 3.0 D&D psionics, and I can tell you about 4ed Psionics, because I was there, I played with them, and I enjoyed and loved them at the time.
I can talk about how 2ed psionics were broken (sort of) because the mechanics of 2ed were broken (sort of). Thing is, that will be always the dissection of an outsider, someone who misses rules as written or worse, misses rules as experienced. Nobody is under any illusion that tabletop games aren’t done with some sort of rules fiddling around.
Thing is, as broken as some things are in a roleplaying game, you don’t actually test large groups of characters against one another. You test small parties against those same small parties, and against the challenges presented to them. It’s easy for me, a player, to recognise shortcomings between two spells, but fixing the weak spells might not be as high a priority as making sure the overall structure of a game is okay. D&D is a rare example in that we have a lot – a lot – of it to work from and that huge volume means we can hold up a lot of examples to be tested against one another.
What happens to make this stuff work though is, at the table, a person communicates the rules to another person. Then, people trust one another to make their rules work out reasonably okay. And that’s why it’s important to make your rules human interpretable. If you have rules that a human can feel comfortable explaining to another human, even if they explain them a bit wrong, things can still work because a human is involved.
Still gunna do a bit on 4e Psionics, mind you.
Over on Patreon, friend of the blog and Viking Accountant Doc Destructo wrote a recent article on Asshole DNA, a series that seeks to study the way a game can leave you with a certain insight into the person who made it who’s a dickhead. He, naturally, started with Watch_Dogs.
Now I’ve spoken in the past about the Ghost of the Author, which is really just an extension of Barthes’ original idea, the Death of the Author. The notion is that there is no singular, pure entity that is the author, and therefore, the person who may think of themselves as the creator is gone and it falls to us to try and interpret who and what they do. In videogames, I argue, it’s not even possible to call that creature the author – they are the ghost of an author, a creature that came about because so much of the creative process of videogame development is
Now I want to highlight something in Doc’s piece:
This phrase he uses, this is lazy gamedev. And then he goes on to qualify how it’s not you know, laziness, but this is defintiely laziness. In this case I kind of want to chime in and note that there is a laziness here, just not the laziness of lack of energy or work. Rather, it is the laziness that reflects a lack of thoroughness.
The thing with laziness in videogames is that it’s sort of impossible to be actually lazy when you’re in this industry. Everyone is working long hours for lots of work and even the person whose work is vanishing down a hole isn’t actually being lazy – they’re just having their effort wasted by other, mistakenly made management practices.
If the ghost of an author is the collected information, behaviour and effort of the entire crew making it, this person can view the allocation of resources as effort. That is to say, while there is no actual laziness from any individual in the organisation, it can be said that having the opportunity to spend resources on a particular field of the game’s development and choosing not to, especially if those resources are being spent in a way that leaves large, unpleasant gaps in the work’s sense of reality.
Nobody on this dev team was lazy. But the author, this ghost of an author, chose to not allocate energy and effort to making sure this world’s gangs and its image of race and racism in Chicago were meaningfully well-thought out. They were done as simply as possible, using shorthand, using a general, broad method that didn’t involve spending more resources on second drafts or rewrites or double-checking narratives or implications or sensitivity testing.
No developer, writer, individual worker, creating this vast project was lazy. But the author of this work was lazy.
Hold up, time to complain about something deeply inconsequential.
Back in 1990, back when rebadging/retheming already-made anime with extremely minimal alterations to on-screen animation, Saban – yes them – picked up a Tatsunoko series and revamped it quickly and with minimal actual relation to the original material, resulting in a product that, uh… I guess the nice way to phrase it is it’d be a very different work.
Now I’m not going to talk about the remix culture of it, the thematic transformation, the characterisation of the adults doing the remake, the meta-awareness of its jokes, the winky way it handles the audience, the trans narrative inherent in an odd character decision, the plot arc about the extra rangers, or even the fact that the opening spells Samurai wrong, and nobody seemed to notice, but rather, this is about something I only just noticed recently.
This is Speedy Cerviche. Without getting too deep into it, he’s sort of the central character of the Samurai Pizza Cats. This is a series where characters commonly have punny names – Polly Ester, Jerry Atric, Seymour Cheese, for example. The thing is, for the longest time, I was convinced Speedy’s name, while pronounced ‘seh-vi-chey’ was spelled Service. I thought that was the joke. You know, his name put emphasis on the wrong syllables.
Well, turns out that no, his name is a reference to ceviche, which is a totally fine thing to reference but it’s somehow both more wide a reference and also not the really clever joke I always thought it was about ‘Speedy Service’ from a pizza delivery boy.
In the age of the easy remix, the re-use, the recycling of media concepts and design spaces and cultural concepts. It’s a space where we have a lot of different terms being used for different kinds of media. For my own purposes, I feel I need to define the meaningful differences between Remakes, Reboots, Remasters and, with new and fresh examples, Recreations.
The Remake is a global term, here. It’s just used so vaguely that it’s hard to really pin down what a ‘remake’ is. Was Full Metal Alchemist: Brotherhood a remake of Full Metal Alchemist? Sort of. Basically, in this case, I’m going to use remake as a way to refer to any new work that’s a new form of an existing work that’s designed to not require previous experience with the work. Each of these other terms refers to a specific type of remake.
A Reboot serves as a way to restart the work, a new point for someone who had no experience to start experiencing the work. A reboot wants to build something out of similar space, wants to use the iconography, it definitely wants to evoke the original, but a reboot is notable for showing you what the rebooter thinks matters to the original.
Here’s an example of four different reboots in one series: Each one was meant to accommodate major changes in the environment the franchise wanted to exist in.
Reboots are really at their best when there’s not a lot of there there, or when you’re making a work move from one form to another. While you might not consider an adaptation a reboot, they both use the same tools. It’s about taking away as much of what doesn’t work in your new form.
A Remaster is more like a translation: Conceptually, you are trying to make the thing again, that functionally works the same way, but with the new tools for presentation. It’s better audio quality, it’s more sound channels, it’s higher resolution images. In the case of some material forms, like film, a remaster can be just taking the production-quality materials and using them to create a new consumer-level version.
The recent trend towards remastering Lucasarts properties – or perhaps just a few classic examples like the Monkey Island games has had different variations on this. In the case of Full Throttle, pictured, the overall spirit is very much preserved, probably because they could work from a lot of similar sources.
One possibly controversial example of this usage of a Remaster is Gus Van Sant’s Psycho, a shot-for-shot recreation of the original Alfred Hitchcock movie from 1960. While this Remaster didn’t involve any of the original footage in creation, it nonetheless sought to be a version of the original in as high a quality as possible, with almost no deviation from the original.
And finally, the most challenging to do well: The Recreation. A recreation, for the sake of this conversation is something above and beyond what a Remaster or a Reboot can do. Recreations are reboots, but, they aren’t just about starting the continuity of the series over; recreations can be about the new continuity and about replicating the story beats or narrative components of the original.
The thing I need this term for, however, is Voltron: Legendary Defender.
Voltron: Legendary Defender isn’t just an attempt to tell the story of the original Voltron series, any of them. It’s not an attempt to update the same plot beats and introduce us to that story. Galaxy Defenders is a recreation of a feeling of the way the original series worked out. It’s a series that takes the same basic idea and ideology of the original story and tries to tell a new story with the same pieces.
The issue I have is that if you simply call it a remake that can miss the basic premise of what the series does. Voltron: Legendary Defender is a series that wants to be the Voltron series you remember and know isn’t there if you ever went back to look for it. It’s tight, dense, and it uses a the set of storytelling tools, animation tools, and trope frameworks we’ve developed in the twenty-five years since Voltron was new. There is, simply put, a lot of stuff in Voltron: Legendary Defender that wasn’t at all in the original Voltron.
Maybe this is all a bit unnecessary. Maybe I just want to tell you how cool Voltron is. Maybe I should just dedicate some time to that. Well, listen, you.
I’ve written about Problematic in the past, with the simple premise that there are no non-problematic faves, and the baked-in nature of the colonialist world we live in is fundamentally damaged. Recent events (a hot take shot from the hip) put the term in stark relief and so, since you’re all so very interested in telling me what I should think about it, clearly you’ll be interested to hear me expound. Right? Right? You’re not just looking to complain at a stranger?
This is spurred in part by recent reading about Dream Daddy. Because that’s a thing I started caring about despite having literally no interest, whatsoever, in wanting to play it, for any reason, at all, gosh dangit. With that in mind there’s going to be a minor spoiler to a thing I don’t care about but let’s take it under the fold anyway. It also involves the genders.
81. Find Where You Have To Limit Players
In RPGs, players are using your system to create and express. The more tightly you limit that, the more you cut off their options. A DM of ours, @ExManus is fond of the phrase ‘your thematics are your own. ‘ and it’s proven absolutely invaluable. Do you have the right mechanical interactions that make sense? Then fuckin’ wonderful. I don’t care if you call it Nature Magic or Fae Soul.
In RPG design, consider what restrictions are necessary to make the game work. Some games have very strict, regimented settings, such as military ones. But more creative, expressive settings benefit from letting players come up with their own explanations for things. Look at where you’re using a theme when you should be using a rule, and when you’re trying to treat theme as if it is rule.
82. Knockouts Aren’t Always Bad
Knockouts – where you remove a player from the game somehow – are seen poorly, especially amongst the Euro-gaming, victory-point counting gamer crowd, but they serve the valuable purpose of freeing people from a game they can’t win any more. If you think being knocked out of a game early sucks, try being stuck playing a game you’re completely unable to win for the full duration
83. TERM: Victory Point Salad.
Some games let you do a bunch of things to accumulate ‘victory points’ and the game just checks the count of them. These games are honestly kind of best for representing big complex economic systems where things are all of dubious total value, and goals are sort of there for players to pursue individually? But a better way to follow this is using a Victory Point Salad design is best for games where you have a lot of different systems and want to give players things they can avoid.
84. TERM: Victory Point
Call them something other than Victory Points, I mean come the fuck on, VP is the most thematically dead term by now.
85. Examine your Base Assumptions
When we code symbols in games we bring a raftload of assumptions. Maybe reconsider them and open other spaces. Bats, wolves and rats are typically ‘bad’, but bears often have a nobility to them as if they’re not all just eating the same idiots.
86. Content Vs System
Games can be broken into Content and System. Some games need a lot of System and comparatively little Content (D&D, frex). Some games are system light and compensate with an enormous volume of content (Billionaire Banshee, Elevator Pitch). If you make a lot of one, you can make less of the other. Note can; that’s not to say it’s a simple 1:1 divvy.
87. Don’t Follow Fads For Fads’ Sake
I’ll use real-time play as an example but the principle holds. Real Time is the latest thing to try doing with card games, and it’s not a bad place to go but it’s also got a big problem: Many people drawn to card games are doing so because they don’t want real-time decision making. They want a turn-based pace. So there’s a quantity of board gamers who react to games like Captain Sonar as if you’re asking them to ride a rollercoaster that’s on fire
Remember, there are some people who want games to give them reliable components. Some folk wanna shuffle up some cards and maybe make a ninja dude fight someone.
88. The Easy Seat
In team games it is 100% okay to design team roles whose job is Be Boring But Useful. Some players don’t want the stressful decisions. Don’t make it essential – don’t make it so some player has to have the dull role? But let someone who wants to take an easy job get it.
89. Players Have Material Needs
Respect your players, but do so wholly. Recognise they need breaks, have other interests, have limited space and money. If I could give up on half the content of Kalash-Tar in exchange for fitting it in the Resistance box I’d take that fucking deal
90. Build Skeletons To Know How Things Run
Try and make a deck builder, a bidding game, and a hidden role game, at least just in concept space versions. If you can explain the basic rules of how those three types of games work, well and coherently, even if you never make one for real, good.
This isn’t even vaguely hard, as it is; there are tons of examples you can look at, and it’s not like boiling Resistance down to its bones is hard.