|
I am glad to see that a count has now been generated for tracking table credits so GMs can officially earn glyphs. Unfortunately, it doesn't seem like it is counting everything. Is this a glitch or is the tracking of table credits limited to certain games and/or games ran after a certain date. I've run over 20 games now (I think 23 but will have to check) and currently the system is only showing 10. Please let me know if there is something I need to do to fix this or if there is a restriction on what qualifies as table credit.
Thanks
So currently, if I remember correctly, the table count shows in full credit numbers, and quests are .25 so it may be showing slightly off. Also, the team is still working to iron and chase out bugs as they become aware of them. I am sure they are thankful for your patience.
|
I've been tracking and reporting ACP issues for a couple of months. Here's a list of things to look at before reporting to Paizo for further investigation.
A) Are all your sessions reported?
Double check that all your sessions are reported On your Organized Play > Sessions page. Checkboxes for both GM and PFS(2ed) -- of course wait for the page to update between checking boxes. Do you see the ~23 sessions you expect? If not track down which ones haven't been reported. Try removing the 2nd filter to see if anything got applied to the wrong system, remove the GM filter see if any of your GM sessions show up as played, etc.
B) Go to GM/Events Coordinator and Refresh Points. Wait for it to finish. You may have to try several times. Check the number of tables of credit for Pathfinder Society Second Edition. Some of their code changes required the user to initiate the Refresh Point to force a recalculation/updating of data in the Sessions page.
C)Go back to sessions, and apply a GM and 2nd filter. Scan the "Points" column of that filtered session view. You should expect regular scenarios to say 1 Pathfinder Society (second edition) GM Credits. You should expect Quests/Bounties to say 0, and Fall of Plaugestone/Age of Ashes Chapters to say 3. Also check if any of them list any 1st edition credit in addition to 2nd credit.
-- There is a current/recent bug where many old conventions are awarding 9 GM table credits for scenarios, so overcounting is currently very common, but that doesn't sound like your issue.
-- For instance my second running of Fall of Plaguestone current is completely empty in the points column and I've reported that to pfsreportingerrors@paizo.com for further investigation.
-- If you see any with 1st ed credit, 'Show seats' for that sessions and check if any of them have an error message about wrong system. Previously I had had a couple of people with character numbers in the 2000s, but tagged as 1st edition characters which through everything off in one of my sessions.
-- One of my recent conventions sessions must have had some data entry issue, which has resulting in the GM name column being blank, while having my correct Paiso number. I'm pretty sure this sessions is not being counted on the Gm/Event Coordinator refresh points view.
-- For a long time, the late spring scenarios had ACP (not GM credit) issues when run a second time. The most recent fixes they pushed seems to have fixed that, but spot check any scenarios that have "Player has already run ..." text in the notes field to make sure the Points and ACP Earned columns look correct.
d) Calculate your number of expected tables manually off the filtered view: 1 for sessions 0.25 (not 0) for quests, and 3 for FoP/AoA chapters. Find out how many you're off by. Currently it seems like quests are more likely to give problems from what I've heard from other people and weird/odd one-off problems from scenarios that require pretty deep investigation.
e) if you want to dig deeper yourself, one thing I tend to do is cut and paste all my GM'd 2e sessions into a spread sheet ( you can cut and paste 1 page worth of data at a time. I tend to add columns to pull out the numeric value of ACP and GM credit to be able to sum those directly. And check for anythng else that looks wrong- This is really just repeated step C, but sometimes the alternate format makes it easier to spot things.
f) If still nothing, email pfsreportingerrors@paizo.com. Be prepared to wait weeks to months, however, depending on the complexity of the error.
|
If still nothing, email pfsreportingerrors@paizo.com. Be prepared to wait weeks to months, however, depending on the complexity of the error.
With the addition of Alex to the org play team, responsiveness was supposed to be significantly improved. In practice, has anyone reported an issue to the address in the last 4-6 weeks? If so, what was the response time?
|
|
I feel Alex has been moving mountains and being an extraordinary asset to their team. However I can't say I've seen any improvement in responsiveness on this particular topic.
My initial ACP error email to them was on July 3rd, with 5 categories of errors and detailed examples for each. On August 2nd I sent a followup reply outlining a 6th error, and providing details on how the other 5 categories had been partially fixed over the past month by their different tweaks; none had been resolved. That email thread has not been replied to. I'm not planning to send a September update in case its like the CS queue were replies send the email to the back of the queue. However some of their tweaks have I think fixed one of the categories.
I did have a simpler email after GenCon, where one of my players entered the wrong character number and they told me about it after the session had already been reported. That one was corrected and responded to within hours. Though in that case the email appears to have been forwarded from the pfsreportingerrors address to the the GenCon event reporters and they handled it.
My sense is when its a data-entry problem, they have a workflow that corrects and notifies you. When you have a problem that requires debugging, and code fixes, I don't think they have a process that connects bug reports to particular code fixes, therefore they don't know who to contact after a widespread fix is rolled out.
Organized Play Associate
|
| 1 person marked this as a favorite. |
If still nothing, email pfsreportingerrors@paizo.com. Be prepared to wait weeks to months, however, depending on the complexity of the error.With the addition of Alex to the org play team, responsiveness was supposed to be significantly improved. In practice, has anyone reported an issue to the address in the last 4-6 weeks? If so, what was the response time?
Just to shed a little light on this publicly (this is not a callout for you, you just happened to ask):
When I started with Paizo, we had reporting errors that were over a year old sitting in the inbox. In the post-covid, pre-con season era, I was able to cut this down to about a month of backlog. Then, of course, convention season began with PaizoCon Online and has only juuuust begun to let up (yes Nicole I know PAXO is this weekend don't @ me).
Reporting errors are also, for me, a "background" task, something I tackle when there is little else to do. They are, with exceptions for some AcP fixes as we get reports of a widespread issue, not the top priority over, for example, getting new Guides out the door, sending out convention support packages, running major, Paizo-sponsored cons (the Gen Cons and Originses of the world) and even taking a backseat to sanctioning APs and rulebooks depending on the focus. We're also entering the time of year when we start planning for next year's products and convention schedule.
As Eric alluded upthread, for about 2-3 weeks after a convention, I try and forward any errors related to that convention to its organizers for immediate fix. However, I can't ask someone to dedicate their entire year to such fixes, so at some point I've gotta start putting those back onto my pile. Currently, my oldest email dates from about the start of July if I recall correctly, which I acknowledge is not ideal. I also acknowledge that while I know how much progress has been made on these issues, that's not necessarily visible to the world.
If someone is having an issue with reporting, the best things I can recommend to get them fixed quickly are as follows:
- See if you can trace the source of the error. Emailing me to say "I think I have too few AcP" is, to be frank, not helpful! I don't know what the problem is immediately, and if you're a prolific player, that's a lotta sessions for me to sort through and makes it that much likelier I skip you when I only have 10 minutes left at the end of the day and I'm looking for an easy fix so I feel good when I log off
- Reach out to the GM or event organizer. In many cases, they're able to fix errors faster than I will, and if not, they might know who can. VCs have some limited privileges to fix errors as well (I think?), so escalate up to them if necessary
- If you do email pfsreportingerrors, include your chronicle from the session(s), because if you just email and say "hey this is wrong" my first email, either when I see it in the inbox or whenever I reach you in the queue, will be my form email saying "hey to fix this, I need to see your chronicle, thanks!" (this is less relevant for AcP errors, as those aren't tracked via chronicle, but hey, it never hurts, and these days all your chronicles are digital anyway so attaching it shouldn't take that much effort)
Sorry, this became a lot. I'm realizing that while I do a pretty good job of talking with our volunteers, we can still do better at communicating with the community writ large, and we're looking at ways to do so.
|
Organized Play Associate
|
| 1 person marked this as a favorite. |
GM counts are currently broken in two fun and contradictory ways:
- Quests are not counting correctly, rounding down to 0 instead of .25 as they should. I believe this should be fixed with a coderoll soon but I do not know that for sure.
- With our introduction of Chronicle Boons (set to replace the boons on paper chronicles) GM credits are ballooning, often counting one table as 9 credits. I am less certain about the fix status of this.
Venture-Captain, Nebraska—Omaha
|
- With our introduction of Chronicle Boons (set to replace the boons on paper chronicles) GM credits are ballooning, often counting one table as 9 credits. I am less certain about the fix status of this.
Yea, this is a fun one! Having 106 tables of credit is great! What, 72 of those tables are going away... ah shucks....
|
|
Thanks Eric for the detailed description. Unfortunately I could not find anything wrong on my end and refreshing did not help. I have just sent an email to pfsreportingerrors to assist with this issue. If you want, I can let you know what they return with.
Yes please let me know when/if your errors get fixed, especially if it turns out that its something we can look for/identify to help with reporting other problems.
We know there's both systemic issues and crazy one-offs, the latter take a lot longer to investigate and might not get global fixes if its not a code problem. But if we can at least point out a problem was similar to another problem they solved, that should help things be fixed faster.
I've been generally happy watching the list of errors from ~late May, slowly decrease/become less common. There's still a lot out there, but it is getting there. I'm still very curious about the one table of PFS2 1-00 I have that's awarding both PFS1 and 2 credit. Tonya has poked at it a couple of times and fixed some things, but its still in an odd state. (I've run that scenario a lot of times, and only that one instance is messed up.) It was also one of the first (by months) sessions to show any GM credits at all, so I think it could have gotten some odd data cached, etc. Maybe they should just delete it and re-enter (but I hear that has other problems).