HoloGnome |
1 person marked this as a favorite. |
Since you are in the midst of reporting/layout changes, there are a few problems with PFS reporting that I would like to add:
1. If you enter a GM PC for a reported session and save the session, then go back and change the GM name because of a mistake, etc. It never properly resets the name for the assigned PC, where the wrong name is propagated in the GM session list and the specific play session list for the -x PC.
For example, from PaizoCon 2017, my GM credit for Bluebeard Alefist (-3) character shows up as "Jim Davis 747" because of a saved, then corrected, entry error on Solstice Scar. In addition, another game I ran (House of Harmonious Wisdom) was assigned to a player at the table instead of me, so a credit for "Sortox the Mad" (my -23) shows up as "Colby Chedderington" (which is an awesome name, but not the one belonging to the PC assigned for my GM session).
Solution: Make sure the code resets the GM name and PC assignment fields when they change in the reporting session, and you probably also want to run a batch query against the database to clear out all the wrong names that have been saved over time.
By the way, the same thing happens when changing the name of a PC. The name changes have never propagated properly.
2. On the "Player" tab for Pathfinder Society info, when viewing the list of reported sessions for a specific player PC, the "-x" number doesn't show on all the entries. At first, I thought it was a field width issue, but in looking at the page source, the -x numbers are not there. So, when you do a query from the database to show the PC's play history, the -x number is either missing from the source field or getting deleted for some entries along the way prior to final display.
If I want to grab all my player sessions for a particular PC, I have to always edit the PFS IDs, since some number of them don't include the suffix.
3. On the reporting side, when saving sessions that have player counts of less than six, the blank entries are now being stuck in the middle of the list after saving by the newly-changed reporting code (recent change). So, if I enter Player 1, Player 2, Player 3, Player 4, then save it, when I look at the session afterwards, I see Player 1, Player 2, Blank, Blank, Player 3, Player 4, etc. Saving PFS sessions should preserve the list order and put the blank entries at the end. And again, you may want to run a batch query with a date after the recent changes to globally eliminate the blank space.
Thanks. It would be great if you could fix these issues.
HoloGnome |
Is there any time estimate to fix the above problems?
Also, to the above list, you can add:
#4: The new search and filter interface for GM and Player sessions doesn't correctly handle basic search for scenario names. With no filters selected and everything displayed (default view condition), I should be able to enter a part of a scenario name, hit search and see the result, if present. Currently, the search returns nothing for valid name search strings.
For example, if I know that "Sewer Dragons of Absalom" is in my GM history and I type in "Sewer" and hit the Search button, the search finds nothing instead of finding the scenario.
This functionality needs to work, especially since the recent changes force the scenario listings on to multiple pages. It is now impossible to quickly find if I have run a scenario. When everything was listed on the same page, I could at least use the browser find to locate things quickly. Thx.
HoloGnome |
Beyond the posts above from 1 and 2 months ago, I have noticed that the scenarios that show up in the play lists for individual PFS characters are now missing multiple entries, even though they show up as assigned on the GM side. Maybe it's that the UI is failing to pull GM sessions assigned to PCs? Not sure.
Is there an ETA for a next major release that will hopefully fix the above PFS reporting issues and also address the incorrectly-diplayed/missing PFS character session entries?
Chris Lambertz Community & Digital Content Director |
HoloGnome |
My comments above represent abstract bug reports spanning months. Fix ASAP comments are an indication that the bug (session lists in this case) should be considered higher/immediate priority (failure to perform a basic or necessary function, but with an indication as to the source of the problem) and, from a quality perspective, do not carry any other implication.
For example, having been at GENCON, I assume that we all have the same post-GENCON recovery period. I, for one, am still a bit jet-lagged.
I also assume that Paizo fixes things whenever they can. The response time is often long, as shown above, but, again, that is an addressable and ongoing quality/resource issue that is not tied to any particular external event or point in time.
Erik Keith Software Test Engineer |
2 people marked this as a favorite. |
Glad to hear jet lag was the worst of it for you this year HoloGnome,
I've gotten the PFS reporting issues you've listed above documented and on our list of improvements the reporting page can use. As you noted above certain ones look to have higher priority and will likely see resolution sooner than the others. I appreciate your patience.
- Erik K
HoloGnome |
Hi Erik -
It's been about 2.5 months since the above discussion. Can you provide any further, updated insight/guidance on when the problem with assigned PFS GM credits not appearing in character play histories will be fixed?
It is impossible for GMs to use the PFS/OP web interface to track their PFS characters.
Thanks - I hope that there can be a quick turn to resolve this issue!
Robert Brandenburg Software Developer |
Hi Erik -
It's been about 2.5 months since the above discussion. Can you provide any further, updated insight/guidance on when the problem with assigned PFS GM credits not appearing in character play histories will be fixed?
It is impossible for GMs to use the PFS/OP web interface to track their PFS characters.
Thanks - I hope that there can be a quick turn to resolve this issue!
We have identified the cause of this issue and it should be fixed in the next major website update, along with a few other issues related to organized play reporting.
Scott Romanowski |
We have identified the cause of this issue and it should be fixed in the next major website update, along with a few other issues related to organized play reporting.
Is one of the issues the inability to report or view sessions of events, as discussed in this thread?
Robert Brandenburg Software Developer |
Robert Brandenburg wrote:We have identified the cause of this issue and it should be fixed in the next major website update, along with a few other issues related to organized play reporting.Is one of the issues the inability to report or view sessions of events, as discussed in this thread?
Yes, this issue should be fixed in the next update.
The Masked Ferret |
Scott Romanowski wrote:Yes, this issue should be fixed in the next update.Robert Brandenburg wrote:We have identified the cause of this issue and it should be fixed in the next major website update, along with a few other issues related to organized play reporting.Is one of the issues the inability to report or view sessions of events, as discussed in this thread?
Thanks! Up to 4 events to report...
Chris Lambertz Web Production Manager |
Locking in favor of our new Missing Organized Play Session Reporting Thread. If you are experiencing outstanding issues that aren't covered in that sticky, please go ahead and start a new thread with a detailed description of the problem.