
![]() |
Hello! I'm playing a lot of the organized play: Heggal when it's just my wife and me playing, Vika when our roommate can play as well, and Lesath whenever others can join in. I've played most of the scenarios two or three times each.
I'm responsible for reporting all of our sessions, so everyone's used to my note-taking at the end of each scenario.
When I report a scenario that has been played by the same player, but with a different character, the reporting system shows an error, stating that the player has already played that scenario. That's true; the player has indeed already played it; but the character hasn't. So there shouldn't be an error at all.
In fact, because replaying is allowed (although you can only take the scenario reward once with each character), the only error that ought to trigger is when I check the "take reward" box for a character that has already played that same scenario and checked the "take reward" box--all other play should be acceptable.
I don't know if this is something that is even on IT's radar, as it seems low in priority, but I wanted to see whether there was a fix for this in the works (and, importantly, if I should hold off on reporting until it's fixed!).

![]() |

I have a question, have you registered three characters for yourself?
1234567-1001 Heggal
1234567-1002 Vika
1234567-1003 Lesath
And when you report the various sessions, you are reporting the "above" character for yourself for that session?
You should only see that notation on the screen (it's not an error) when your character has actually replayed that scenario. I have Harsk (my 1001 character) which I tend to play which has replayed many scenarios with various groups. So the system tells me when I've originally played the scenario. So the only time I can check off the Take Reward is the first time that character has completed the scenario.
So I'm wondering if you're trying to report Heggal, Vika and Lesath all under 1001 rather than three separate characters.

![]() |

I just wanted to check to make sure you weren't trying to report different characters on the same one. :-)
And if you are looking on the Player Sessions and you see under the column Notes:
"Player has already played scenario at session # 2 of event # 51250 PFSACG @ Six Feet Under Games on November 04, 2014."
That's fine. Just a note (not an error). I have that on several of my characters.

![]() |
I just wanted to check to make sure you weren't trying to report different characters on the same one. :-)
And if you are looking on the Player Sessions and you see under the column Notes:
"Player has already played scenario at session # 2 of event # 51250 PFSACG @ Six Feet Under Games on November 04, 2014."
That's fine. Just a note (not an error). I have that on several of my characters.
That's precisely the type of flag I'm getting--but it seemed like an error to me rather than an informative note. It didn't stop me from reporting the event, or invalidated the table, or anything, so it doesn't seem to impact my reporting--I just thought it didn't need to be there, because it was flagging something that is entirely permissible.
Full speed ahead from me, then! (I have to say that I'm piling up with the star rating by organizing these--I'll be a four-star GM by Christmas!)

![]() |

That's precisely the type of flag I'm getting--but it seemed like an error to me rather than an informative note. It didn't stop me from reporting the event, or invalidated the table, or anything, so it doesn't seem to impact my reporting--I just thought it didn't need to be there, because it was flagging something that is entirely permissible.
Full speed ahead from me, then! (I have to say that I'm piling up with the star rating by organizing these--I'll be a four-star GM by Christmas!)
Here's the thing ... this reporting system was originally designed for PFS RPG scenario reporting. Replays are more restricted. So the system simply takes the PFS#-Character# and checks against previous reported scenarios and makes a note if that character has already participated in that scenario.
As someone that deals with records and personnel, a notation like this is fairly common. So to me, it doesn't look like an error or a warning. Just a note to let me know.
Secondly, they're removing our stars ... soon.