BronxWench

31228

31226

31224

We're in the midst of a code revision project, and some of our usual features have had to be disabled temporarily. I do believe that the ability to select email notification for reviews is one of them, unfortunately. I'm not sure if it can be turned on by our tech admin, but when she surfaces from what's been a gruesome RL workload, I'll check.

31222

I think that's the part of the rabid fandom thing that bothers me the most. When you drive a person away from writing simply because they wrote a pairing that isn't "beloved" of the masses, there's something profoundly wrong with that fanbase. Some people need to step back, look long and hard in a mirror, and think about how they'd feel if they were on the receiving end of the vitriol they spew with such abandon. Maybe there's a "50 Shades of Cyberbullying" out there handing out misinformation on what constitutes appropriate online behavior in a fandom?

31220

The Harry Potter fandom isn't much saner, to be very honest. I'd wager most fandoms can be obsessive. When I do write for a fandom, it's for a game fandom. The Dragon Age fandom doesn't seem quite as hysterical about sacred pairings, and I haven't been shot for my Neverwinter Nights 2 sidestep from the "canon" romance. But, like Melrick, most of what I write is original fiction.

If he becomes an annoyance here, we'd be happy to assist.

I'm not seeing anything by that title in my records. Do you remember the author's name?

31214

Thank you! It's visible once more.

31212

I like constructive criticism, although I'll never turn down glowing praise. I might blush a little, but I do like it. What.s really, REALLY useful is knowing what worked for readers, and what didn't. My editor was all bothered by one review on Goodreads, where the reader felt I could have done more character development in my debut novella. And you know what? That reader had a valid point. I don't see that as a negative, because it tells me what I need to do better. The reader did go on to say that they were looking forward to the second book. Let's hope I did better, but if not, that's still valid from that reader's perspective, and I'm not crushed to be told that. I don't worry so much about long or short, or if it's one returning reviewer or many reviewers. When I write online, either is fine. When I publish, I get one shot at a review, so it's not an issue.

It does need to be at the bottom of each chapter. When I swept your story, I was immediately aware of the dialogue from the game, having played it myself. Chapter 3 in particular contained a lot of dialogue from the Dalish elf opening sequence. So we'd need to see that citation in each chapter.

Okay, because I was obviously NOT clear enough in my previous post: DO NOT POST LINKS TO A STORY THAT THE AUTHOR HAS REMOVED. DO NOT POST LINKS TO A SITE THAT DOES NOT HOST THE STORY WITH THE AUTHOR'S CONSENT AND PERMISSION. Michally took the story down, does NOT wish it posted, and we will not allow this forum to be used as a conduit for piracy. If you can't abide by our rules, don't post here.

31199

Bear with us. DemonGoddess061 has a ton of work in RL right now, and that has to take priority. She'll take care of this as soon as she can find some time.

Hi, The issue is that you've used dialogue from the game in the story, specifically in Chapter 3. When that happens, we require a citation at the top or bottom of the chapter, stating that some dialogue is taken from Dragon Age: Origins. I suggest something like this: "Some dialogue has been taken from Bioware's game, Dragon Age: Origins." I recommend a citation like this be used wherever any dialogue is paraphrased as well, particularly when it remains close enough to the original dialogue as to be recognizable from the game. The FAQ does show some examples, and at the end of the first post of the FAQ, it does use something very similar as an example.

31192

31190

31188

As far as I'm aware, this is not on the list of features we're looking to incorporate as we roll out the new code for the archive. I'm not sure if that will change, but I haven't seen any requests for this feature since we've been rolling out the code.

31182

31180