|
6 people marked this as a favorite.
|
Pathfinder PF Special Edition, Starfinder Society Subscriber
When reporting Plaguestone for PF2 the reputation is brought down to 8 by some internal process, even though it should be 12 and was initially reported as such. Subsequently tried to update the session with the correct reputation of 12 and was again brought back to 8 upon save. This is for both GM and players.
Pathfinder Adventure Path, Lost Omens Subscriber
I'm having the same issue. Even with trying to go back in and resave the report, it continues to default it back to 8.
Came here to report exact same thing.
Pathfinder LO Special Edition, Maps, PF Special Edition Subscriber; Starfinder Superscriber
This appears to still be an issue.
This still seems to be an issue.
Pathfinder LO Special Edition, Maps, PF Special Edition Subscriber; Starfinder Superscriber
Just another update to state that this is still an issue.
Pathfinder Battles Case Subscriber; Pathfinder Maps, PF Special Edition, Starfinder Adventure Path, Starfinder Society Subscriber; Pathfinder Roleplaying Game Superscriber
I hope they get this fixed soon. APs are getting sanctioned and this bug affects all AP reporting, also.
Pathfinder LO Special Edition, Maps, PF Special Edition Subscriber; Starfinder Superscriber
Just pointing out... this is still an issue. And sounds like it's going to get worse with the AP Sanctioning TomParker mentioned...
It's 2021 and this is still an issue
Pathfinder Battles Case Subscriber; Pathfinder Maps, PF Special Edition, Starfinder Adventure Path, Starfinder Society Subscriber; Pathfinder Roleplaying Game Superscriber
How does this factor into the PFS changes? Are they still reporting Reputation but not tracking Fame?
Pathfinder Maps Subscriber; Pathfinder Roleplaying Game Superscriber
When you try to put in the 12 Fame earned for completing the scenario it defaults back to 8 and the players only see getting 8 not the 12. Also pre/post change it's still the same box to fill in when reporting.
I'll add my experience that it's still an issue.
Unfortunately, I don't have any news to share on this front; tech is aware, the fix is in progress, and once it's been rolled we'll announce it in a blog post.
Recent threads in Website Feedback
|
