
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
4 people marked this as a favorite. |

FYI, after speaking with Tonya, I have confirmed that the reportingerrors@paizo.com email address is currently dead. Don't bother sending to that address as no one is monitoring it. If you have submitted any errors to it that are still pending, you will want to direct the issue to another channel.
We are discussing what an official reporting error program needs to look like and how it will function. In the meantime, we have to work together as a community to resolve these issues. Ideally, event organizer/coordinators will be the best source to fix issues with their events. This includes the organizing committees for each of the premier events. Use the official contact address listed HERE
Venture-Captains are the secondary point of resolution, but keep in mind that many of our VCs are waiting on their nda to be processed so their Paizo account can be updated. Until this happens, they do not have the necessary admin access to search for and correct reporting errors. You'll have to contact your local VC to determine their capabilities.
It is important to note that whomever you contact to fix your error will require as much information as possible. If you don't have any meaningful information about the event/session it is possible they will not be able to help you. We strongly encourage you to review your reporting history on a regular basis. The longer you wait to try and correct something, the more likely details will be forgotten and increase the chance nothing can be done.
Ideally, send a picture of the reporting sheet with your request. That is the best way to resolve your issue. Otherwise, provide as many of the following details as possible:
- Your name
- Your screen name
- your OPF# & character #
- character name
- character faction
- event name
- event number
- date
- GM's name
- GM's screen name
- GM's OPF#
- session number (if the table occurred at a convention or multi-table event)
If you can take a screen shot of the table/session from your log in My Organized Play it is also helpful.

Keldin |

So, as I thought. I mentioned this last month when Paizo posted that, essentially, the playtest sheets were worthless. I was told to report it to pfsreportingerrors@paizo.com. I did. This time, at least, as opposed to when I posted in 2017, I got form responses back, but I just checked, and still no changes.
As for pictures of reporting sheets? As far as I know, that's a completely new thing, only having been suggested with the start of PFS2.

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

essentially, the playtest sheets were worthless
Not necessaryily. I don't know if we are locked out from reporting Playtest events yet or not, but its worth sending the info to your VC or RVC to see if they can help. Ideally you should contact the event organizer for the specific table, but you may not know who that is.
As for pictures of reporting sheets? As far as I know, that's a completely new thing, only having been suggested with the start of PFS2.
Actually, it started at Gen Con 2018. Some of us have been recommending it a bit longer than that. It is much more prominent now that reporting is much more important given the AcP. In an ideal world it wouldn't be necessary, but the reality is the only person those AcP matter to is the one earning them. So, my advice is protect yourself (C.Y.A.) and make sure you have all the necessary info to follow up if you find your reporting is in error.

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

edit sessions back?
No idea. Some VC/RVC still have their admin access to edit reporting (check with yours to find out), but ideally errors should be pushed back to the event organizer because they have access to edit reporting for their event regardless of their VO position (or not). It is extremely difficult to correct play errors since no one has visibility to play sessions anymore. Those with access can only see the GM session log so we can only correct tables that were reported, just reported incorrectly.

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

Any idea when we get the NDA's so we can sign them and return them?
Nope. The VO maintenance process is being worked as we speak, but its at the RVC level at the moment. Even after the nda if complete, we are still dependent on when Paizo tech can assign the scripts to the individual so provide the proper access. Some scripts also need to be updated.

![]() |

If people have problems that are less to do with reporting (I personally have the issue that I accidently deleted my XXXX-01 number and I'd like to see if theres any way that I can recover it), is there anywhere currently that we would be able to contact to see if we can fix it while the reporting errors emails address is currently dead?