Subject: Congrats for the record.
Author:
Posted on: 2016-05-11 21:18:00 UTC
The quality of the mission only make it look better. I wish you well for any future mission you'll be writing, and hope you won't end up with another enforced hiatus.
RC 211 Mission 14: "...in the Wind"
Agents—Valon and Kala
Continuum—Dust: an Elysian Tail
You're right; that is a big deal.
*applause*
Well done, and good work keeping things from getting too...icky.
And it seems that there's only one error!
Nimbat doll, I asked Publica to make one for Leyuu.
Punctuation error: that comma should be a semicolon or period.
The quality of the mission only make it look better. I wish you well for any future mission you'll be writing, and hope you won't end up with another enforced hiatus.
And congrats on the new record! *applauds politely*
You could've at least waited for me to actually try and proofread this thing before posting it! XD Whatever, I probably wouldn't have found any issues SPaG wise regardless.
Great mission, overall - though I do hope how Kala's tech interest developed between this and her previous mission gets explained in full soon. It sounds like a fascinating avenue for exploring her character and I'd like to see her take on a mission that requires it someday. :)
What's with people posting stuff before their betas have finished, y'know, betaing? I've seen so much of this in the last year or so, in missions from multiple people, and even on occasion in Permission requests.
If you ask someone to beta your writing, the least you can do is wait until they've signed off on it or said they have to back out. Posting isn't time-critical - you can afford to wait a day or two, or even a week or two!
hS
Allow me to point everyone to PC's workshop on beta-reading. Among other things, it contains useful advice about communication between beta and writer. Communication is a thing that should be happening before, during, and after the beta-reading process.
~Neshomeh
There's also been more than a fair share of conflicts between the writer and beta in this time period too, come to think, which is also something that probably/apparently needs further explication for what the roles are supposed to be.
The beta shouldn't be outright ignored when they suggest something to be changed, but it doesn't mean the beta should be taking control over of the story and turning it into their idea of what should be happening either.
I've been through that song and dance before, and nobody came out of it well. A beta, in my book, should really be more of an editor than a glorified spell-checker; they should discuss the themes of the work with the person they're betaing and only seek to change them if they're really not working.
I don't do that.
I don't do that because it's too much like hard work. I don't do that because I'm lazy. I don't do that because nine days out of ten I can barely muster an emotional response to what I'm reading and the tenth I'm trying to think through tar. I am a horrible beta and I cover for it by making jokes and cracking wise at the fic's expense, because even when I can't do what's asked of me I can at least do that.
I urge anyone being a beta, and everyone having their work betaed: take this on board. Think more deeply about your work. I know Iximaz and Skarmory churn out missions like nobody's business, but it's not a competition. Your agents are overworked semi-professional exterminators held together by spit and baling wire; you guys aren't. Take a step back, breathe, and wait for everything to come in. It can only help the process.
And for the love of God, don't be me, but you probably knew that already. =]
Also worrying: The recent tendency to ask for betas one day and posting the mission the very next day (or similarly short period of time). There is little to no chance that the betas had time to do their work and for the author to make the necessary changes and (hopefully) repeat.
Maybe we need to teach people how to beta and how to work with a beta?
-Phobos
I thought that would be enough.