[FastJack]

I've been pointing people over there whenever they bring errata up. I'll also bring it up with the other Mods to see about keeping it more organized.

[Bull]

There's been a bit of discussion on the freelancer groups about that as well.

But yeah, I agree...  Keeping the threads contained, on topic (i.e., no rules discussions or arguments), and concise would help a lot, as would some standardized format of listing potential Errata. 

I would actually suggest two threads..  One for pure Errata (Obvious typos and errors), and one for "Questionable COntent" (THis would be where you go "Did you REALLY mean for that to only cost 1,000¥?  Seems cheap) or "These rules seem broken!", though again the latter would need to be discussion free...  Post up the "Questionable content" there so freelancers and devs can review it, but discuss it over in one of the other sub-forums.

Bull

[PeterSmith]

I would actually suggest two threads..  One for pure Errata (Obvious typos and errors), and one for "Questionable COntent" (THis would be where you go "Did you REALLY mean for that to only cost 1,000¥?  Seems cheap) or "These rules seem broken!", though again the latter would need to be discussion free...  Post up the "Questionable content" there so freelancers and devs can review it, but discuss it over in one of the other sub-forums

BattleTech's forums split that into two sections. Keeps the chatter down in the Errata threads.

[JM_Hardy]

There are a few forum tweaks I need to do--I'll see what I can get to over the weekend. Maybe while I'm enjoying the Bears game …

Jason H.

[Dread Moores]

A thread for each book, with a first post updated with the current errata ever so often, would get a hearty recommendation from me. It's a nicely organized way to do it, and it makes it very easy to find the most up to date information. A few different game forums I frequent use that (Battletech among them), with the usual format of product, page number, issue noted (without long arguments ideally), and suggested corrections (if necessary). I'd think that would be a solid format to follow, provided (and this is really key), clear examples for the desired format of errata submissions are provided at the beginning. Without those examples, confusion can easily result.

[PeterSmith]

...and suggested corrections (if necessary).

I prefer the so-new-that-people-didn't-follow-it format of the now down BattleTech forums:

Discussion is only in the "Ask The..." section (whatever its counterpart will be called over here). Aside from obvious tense/word substitution errors, there are no suggested changes in the errata threads. Rather there are links to the outcome of the discussion from the other board.

[Dread Moores]

Yeah, I don't mind either way, really. I think it worked in that particular instance, mostly because it was constrained to something like "You missed a half ton on construction here. Need to drop this thing that is only thing that weighs a half ton on the design." In general, the suggestions might be best when they are limited to something that clear cut, and not something liable to inspire heavy debate, or something that is more a matter of personal tastes. Once you start delving into more of the fluff material, it's tough to make clear suggestions.

[PeterSmith]

In general, the suggestions might be best when they are limited to something that clear cut, and not something liable to inspire heavy debate, or something that is more a matter of personal tastes. Once you start delving into more of the fluff material, it's tough to make clear suggestions.

Problem stems from what is defined as "clear-cut" changes from person to person.

[Cain]

I can't really imagine that the trash talkers and trolls who comment on these leaks are part of your loyal customer base.

On the contrary, pretty much all of them are/have been loyal members of the customer base for years/decades(some from the very first books ever released) thats the exactly the reason why they take time to express their worries about the way the game line is going to.

I'm one of the ones he's talking about.  I've played Shadowrun for twenty-two years, I love the game and I'm not giving up on it.  So, I complain loud enough to have my voice heard, because I care about the game line.  If I didn't care, I'd be content to let the line die.  Only people who care will fill out complaint cards, after all.  The 60's are long gone, but there was a time when we knew that if we shouted loudly and passionately enough, we could cause a change. 

[Dread Moores]

Only people who care will fill out complaint cards, after all.  The 60's are long gone, but there was a time when we knew that if we shouted loudly and passionately enough, we could cause a change.  

I'd disagree that complaint cards are only filled out due to care. Sometimes folks just want to complain (legitimate or otherwise, all depends on the situation). Also, sometimes shouting loudly just ends up being a whole lot of noise and not a whole lot of clear message.

[Dread Moores]

Problem stems from what is defined as "clear-cut" changes from person to person.

Yeah, like I mentioned earlier, I think you can have it work as suggestions (and only suggestions, not rants or kvetching). We'll probably differ on that, but it really only works when you're looking at hard and fast numerical mistakes. That was my experience with the BT errata, but then again, I don't actually think the new policy there made sense. That's just personal taste speaking, though.

I'm not sure if you'll find that same sort of hard and fast corrections in the type of SR errata needed as a general rule (there could certainly be some things in the future that might fit that mold, I have no clue), as there's less of a construction system in play. (Excepting things like the vehicle/weapon mods). When you get into fluff issues/conflicts, the situation gets a lot messier. I can definitely understand not going the suggestion route there, and simply wanting submissions to point out the conflict, rather than offer a fix.

[Kid Chameleon]

Only people who care will fill out complaint cards, after all.  The 60's are long gone, but there was a time when we knew that if we shouted loudly and passionately enough, we could cause a change.  

I'd disagree that complaint cards are only filled out due to care. Sometimes folks just want to complain (legitimate or otherwise, all depends on the situation). Also, sometimes shouting loudly just ends up being a whole lot of noise and not a whole lot of clear message.

Or people with a lot of time on their hands. 

[Sichr]

Well I'm not going to hold against you things you didnt get given, hand overs at work during good times can be a ass at bad times I dont even want to imagine.


Can we have some reasurance that the quality issues are being handled in both directions? It does wind me up that I put up with a older copy of a book and the only way to get the updates is to buy a new one.

Yup. I've gotten the schedule for the year more formalized, and that builds in more quality-assurance time. I'll also be working on a new errata-generating procedure, most of which should be in place by the end of the month.

Jason H.

Ummm I may have missed that, well...what year were you exactly talking about?

[FastJack]

If you have a question for the developers, please ask in a respectful tone.

I realize updates and errata are an outstanding issue, but being disrespectful to the developers is not a way to get them motivated.

[CanRay]

Please be nice to the Freelancers as well.  We have sensitive feelings.