Thread by @Delafina777

Thread, up and down.

And a few things to add:

Ajit is absolutely right about how often there are fuckups on credit pages. I’m missing plenty of dev and writing credits I should have, and have a handful I shouldn’t. It can hurt to discover you’re left out or miscredited!

https://twitter.com/ajitgeorgeSB/status/1468699208563580933

And it absolutely sucks if, for whatever reason, you really need that credit.

Companies need to act quickly—update digital files immediately, issue a public apology and correction, & make sure it’s corrected in the current print run if there’s still time—and pay the change fee

—and make sure future print runs are corrected if it’s already been printed.

I mean, were it me, I’d also probably send the person left out an apology card and some cookies to address the personal hurt as well as the professional harm.

This needs to come from the *company* because at the end of the day, making RPG books is a team thing, and screwups like this might be attributable to one person not putting a name on a list or another person missing a name on a list in layout, but that usually happens in…

…a context of not enough time, not enough editors, broken processes, etc.

Ultimately, unless you’ve got deliberate sabotage, this stuff isn’t about one person.

The bigger harm here isn’t the mistake itself—it sucks, but welcome to game publishing—but the failure of the company to publicly address it.

And that’s where I start to get really angry at supposedly progressive gamer Twitter. You can tweet about #PaizoAccountability all you want but apparently you didn’t listen to a fucking THING any of us said about how this shit goes down.

When a company’s PR machine is silent about a screwup, and a lone dev apologizes, 30 seconds of thought ought to tell you there are 3 possibilities for what’s happening:

1) The company wasn’t interested in making a statement and the dev did it anyway.

2) The company instructed people not to say anything and the dev broke ranks.

3) The company offered up the dev as a scapegoat.

Pretty much any other scenario, the company says SOMETHING.

And we just had a huge scandal in this industry about creatives trying to do the right thing in the face of company apathy, pushback, or downright hostility, but apparently an infinite number of devs have to get thrown into the spike trench before RPG Twitter builds a bridge.

And most of us talking about this shit generally try NOT to name our colleagues who are fighting the good fight unless they name themselves because they should be able to stay out of Twitter hell if they want to.

But just to be clear: we may not talk much about the good people who got out of Paizo and ended up at WOTC because they can’t talk shit about Paizo even if they want to while employed at another major RPG company.

That doesn’t mean they weren’t there with us.

Amanda was a fucking amazing colleague who could have had six wild bears chewing off her leg and would still be trying to make sure that her freelancers were treated well, that her coworkers were okay, & that our products were welcoming and celebratory of underrepresented groups.

But fine: don’t take my word for it. The facts stand:

She apologized.

The company didn’t.

And SHE’S the one you’re mad at?

Yeah, I don’t think your intentions are good.

Update: good, they finally did.

Go yell at the company, if you want to yell at someone.

https://mobile.twitter.com/Wizards_DnD/status/1468692154243588101