
![]() ![]() ![]() ![]() ![]() ![]() ![]() |

First off: I'd like to apologize if this is the wrong place to put this question. That being said, my question is: I see (open) calls for writers and artists, but is there ever an open call for proofreaders?
I love Pathfinder, especially Society and its scenario's, but I have a healthy case of OCD and my fingers itch when I prep a scenario and find (small) errors in it.
I'd love to help and make the scenario's even better, but I have no idea if such a thing is even done by Paizo. Has there ever been a call for "external" proofreaders/editors?

![]() ![]() ![]() ![]() |
1 person marked this as a favorite. |
I believe it to be an immutable law of the Internet that whenever someone offers editing assistance, there is inevitably a hidden grammar, spelling, or similar error in the offer.
That said, I'd be happy to assist as well - amusing as it may be to read about swim checks to break down the door, the constant minor issues are a routine (albeit minor) annoyance when reading or running a scenario. Of course, I understand the reluctance of The Powers That Be to allow random GMs on the boards to see content while it's still being developed. I'd expect if "volunteer proofreaders" are ever allowed, they'd probably come from the venture officer ranks. Which is a shame, because as an innate grammar nazi, I go through scenarios with a red pen anyway after they get released.
An idea - next month, when the next set of PFS scenarios come out, why don't we start a thread to find all the various errors, both typographic and mechanical, in the scenarios? That way we can actually test and see if there's any value that an extra set of eyes can add to the document. If nothing else, we can provide unofficial errata to the scenario and throw it up on the PFS prep board as patch notes.

![]() ![]() ![]() ![]() ![]() ![]() ![]() |

I believe it to be an immutable law of the Internet that whenever someone offers editing assistance, there is inevitably a hidden grammar, spelling, or similar error in the offer.
That said, I'd be happy to assist as well - amusing as it may be to read about swim checks to break down the door, the constant minor issues are a routine (albeit minor) annoyance when reading or running a scenario. Of course, I understand the reluctance of The Powers That Be to allow random GMs on the boards to see content while it's still being developed. I'd expect if "volunteer proofreaders" are ever allowed, they'd probably come from the venture officer ranks. Which is a shame, because as an innate grammar nazi, I go through scenarios with a red pen anyway after they get released.
An idea - next month, when the next set of PFS scenarios come out, why don't we start a thread to find all the various errors, both typographic and mechanical, in the scenarios? That way we can actually test and see if there's any value that an extra set of eyes can add to the document. If nothing else, we can provide unofficial errata to the scenario and throw it up on the PFS prep board as patch notes.
I agree and I would totally understand it if Paizo says they're not going to do that. Just want to know whether or not to keep my hopes up :)
I'd definately be up for starting a thread (though it might be difficult not to have it turned into a 'quote everything that's wrong with the scenario'-slugfest). They may be only little things most of the time (for example, my latest scenario is missing one monster in the bestiary appendix and the hp of a monster is quoted wrongly in the tekst), but it'd be nice to help.