Letters from a ttRPG Dev to a Freelancer, 6. When The Publisher Ruins Your Turnover
This entry in the Letters from a Dev series is adapted from a direct message I sent to a freelancer who I had offered to help get some 3pp material published for, and who then had some other opportunities pop up that (quite rightly) they pursued first. But we kept in touch, and I was happy to give guidance and advice when they wanted it.
Recently, they had some material in something published professionally… and the product was not great. I won’t go into details, other than to say the final text is pretty clearly worse than the original turnover the freelancer sent in. Now, that happens sometimes. It’s much, much rarer than things being significantly improved, in my experience. It’s even rarer than a freelancer thinking something has been ruined, when in fact the publisher has made improvements the freelancer simply isn’t fond of. But a publisher ruining a good draft does occasionally happen. And, when it does, it can be a shock, and a real emotional gut-punch.
Especially if the product was something you were excited about, seeing it’s final form be less clear, more typo-ridden, and riddled with worse rule implementation can be spectacularly disheartening. Given how tough ttRPG creation work is, how poorly it generally pays, and how little respect the work earns from the general public, often the joy in seeing the final product–with all its polish and improvement–is the biggest reward for the labor you put into it. When that is not just worse than you expected, but worse than you handed over, it can feel like you wasted your time and have been treated with disrespect.
In this case, the freelancer asked if I was willing to offer any suggestions on how to handle both the professional issue, and the emotional toll it takes. My adapted response is below.
“First, know that this is rare. Also, that’s always hard when it does happen. As a socially awkward depressive, I have had some projects changes and/or cancellations send me into deep negative states. It’s rough.
So, what to do about it.
Assuming the whole book isn’t a shitshow, it’s totally worth celebrating it as a project you contributed to. Credits are important, and even if they take away your joy, they shouldn’t also get to take away your stepping stone. You worked hard for this, and if you decide to move forward with freelance work, it’s worth having a professional credit from a recognizable company name on your resume. As long as the issue isn’t a moral or legal failing, even if you aren’t a fan of the final form, the very fact you did the work and it got published can help you get more opportunities in the future. The best way to clean a bad project taste out of your mouth is with a better project.
Even if you claim the project credit, since you earned it, feel free not to talk about what specifically you wrote for it. Usually, people don’t ask. If the DO ask, just say “Since the developer made changes, I don’t want to claim anything specific without the developer weighing in first.” If someone notes the project has a lot of errors, it’s fair to say you are not the developer or the editor, but don’t go farther than that. As a freelancer looking for more gigs, there’s no upside to making a stink about the quality of other people’s work if it’s not an ethical or legal issue.
It can be worthwhile to reach out to your developer and (politely) ask about specific changes that seem to be errors or violate the guidelines you were given. Don’t say it’s wrong and they messed it up – just say something like “I note that I wrote the Thingamabob gives a +2 bonus, in keeping with the design document I had, and the final version gives a +5. Is there a design consideration I should be aware of, so I can create material closer to what you need?” This kind of request-for-feedback is fairly common, and even if it the change to what your wrote just a big fuckup on their part, bringing it to their notice at least means they can start more quickly to work on errata, if any.
Those are practical concerns. Emotionally? That’s harder.
Bitch to friends you trust to keep it quiet. Play a game as different from what you worked on as you can. Pet a cat. Do an internet search for “TSR DaWizard,” and when you read the stories remember a BIG company got that one wrong on a huge scale. Drink some hot cocoa (or whatever fills that role for you). Let some time pass.
Know that this is a moment in your career, not an omen about the entirety of it.
Also… the pandemic has been hard on every creative I know. This both makes projects more likely to get botched, AND makes the impact of having your work be mangled so much more impactful. We have no idea the circumstances under which the developers/editors got their work done on this project. It may be an outlier that just suffered from massive internal problems with the company. It sucks for you, but it isn’t personal. And it isn’t going to happen every time.
Give yourself permission to be angry right now, and to need some time to shake it off. Usually, after a few weeks, it won’t be quite so raw a wound.
Support My Patreon
The more support I get, the more time I can spend on writing things like this.
If you enjoy any of my articles, please sign up, for as little as the cost of one cup of coffee a month!
Posted on December 8, 2021, in Business of Games, Musings, Writing Basics and tagged Essays, Freelance Life, From My Files, Letters from a Dev, Mental Health, Writing Basics. Bookmark the permalink. Leave a comment.