|
I am currently having the same issue. One of the players in that particular game had not registered their character. When I removed that player from reporting, the game reported properly. I am having that player register his character and will report back if it goes through correctly.
I just had that player properly register their character. Seems like players simply have to be registered from now on, as it worked perfectly. Hope that helps!
|
|
Having the same issue here! We had new players at a convention over the weekend and they were issued PFS numbers. No idea when they will actualy register their character, but until then we are unable to report the entire game.
If this is the new norm it will make reporting for games with new players very difficult.
We're looking at this issue now; the problem is, indeed, that folks have not yet registered their characters. Once that's done, reporting will work normally.
The problem is that until a character is registered, the system doesn't actually know what kind of character it is. So if we allowed them to register "blank" as it were playing ACG, they could then go back and register as a Core character and the data gets.... unfortunate.
So, yeah, we know can be a pain as it's currently working, but this way maintains the integrity of the data while we figure out a more graceful solution. And we are working on a more graceful solution, we just want to make sure it's the right one before we implement it.
I haven't played PFS in a while. What is this Core business?
Edit: Nevermind, I found the appropriate forum threads under Society play.
Byakko - The GM does specify whether the game is Core or not, that's done when you select the scenario. Beyond that, we're looking at solutions that are similar (but not exactly the same) as what you're describing, it's just a little more complex on the back end.
And yeah, listing which character(s) is/are causing the problem is on our list of improvements.
Having this same problem with reporting tables from the ACG.
Has everyone in the session registered their characters?
The Show All Scenarios box also seems to not work anymore. Or is that just me? What is the work-around to report when I don't have edit abilities for the event?
Has everyone in the session registered their characters?
Nope. Not sure I'll be able to convince them to register their characters either, but we'll see.
|
|
Has everyone in the session registered their characters?
Cort, I ran a small GameDay here last weekend where we introduced Adventure Card Guild to new people who sat alongside established gamers in my Lodge. I have yet to be able to record the credit that anyone at that table received for the game. Some of the established gamers at my Lodge are interested in taking their ACG characters into another game, but they don't see any credits from last weekend showing up on their accounts. I've tried now multiple times over multiple days to record their information. I'm sure it's one of the newer gamers who hasn't gone online to Paizo to register their character, but I don't have anyway to contact those people.
I know you're trouble-shooting the issue and making sure that people have gone online to Paizo to register their characters as a means of safe-guarding against those NE types who would register a CORE character or an ACG character falsely, but this issue is negatively affecting two separate groups of people: the established gamer (who cannot advance their character), as well as the new gamer (who has no idea that they need to go onto Paizo to register their character - hell, I didn't have any idea that I had to register my character to avoid an error message until last week).
I'm very much hoping that this issue is resolved soon. Thanks for your hard work.
I believe all the player needs is their signed chronicle sheet. That is is the official record. Though I could be mistaken.
So I needed a workaround to report the scenario and is there one past this issue as well. It's like the damn reporting system doesn't even work anymore. We give out numbers for new players for a reason, this breaks that whole mechanic.
|
At least five of my players (between two separate tables) need to create characters up to/including their character number for me to successfully report them. Fortunately, these are new players who seem to becoming regular players. When I have over a 40% failure rate to report player participation...
What I did was removed those invalid character numbers in order to report the scenarios for those players that did successfully register players. Now I'll have to go back in a month to edit the reporting to add those players in. Assuming that I don't forget (which I won't; I've added it as a calendar reminder to do so.) I can foresee other GMs/Event Coordinators who will not be so diligent.
Do we now need to bring tablets for players to make sure that they've logged the characters they're playing in prior to game end?
Constructive Criticism portion: Can the system be changed to theoretically create a placeholder for xxxxxx-yy as a Campaign or Core, depending on the scenario type being run, just so the game can be reported?
-- Steve
|
I'm just back from Conception with 140 game sessions to report and it's not going well. Many character numbers are causing the report to fail to save. They seem to be new character numbers that haven't yet been registered or numbers where a player is planning to create an extra character but hasn't registered it yet. The ones that are accepted come up as "RPG". The ones that aren't accepted remain blank in that column.
It's a real problem because the whole game report fails to save. I can't wait for players to register their characters online and, of course, the reality is that some never will. Is there anything I can do to work around this or are you working on a fix?
| 1 person marked this as a favorite. |
So this has been broken for over a week and it's been almost as long since we've gotten an update. I have a scenario I would really like to report as well has Angel Gabriel who has gods knows how many.
New players aren't very likely to register their characters in the beginning. What's the point in handing out generated character numbers?
This needs to be fixed.
I am also having this problem reporting two sessions.
All the players tell me they are properly registered. They may not have registered specific characters - but in both cases we were playing We Be Goblins, and one players wasn't sure at the time which character she'd be applying credit to.
I'm finding this frustrating - this didn't used to happen.
| 1 person marked this as a favorite. |
Oh, just add me to the chorus of people expressing frustration with the huge hitch this throws into routine reporting of games. We have numerous casual and/or young players who come in to play once every few months, who have not registered their characters and probably never will; under the old system this was just a minor detail that could be bypassed when you went to report. Under this system it means none of our regular, dedicated players (or myself, closing in on my third GM star, and really wanting to be sure every game I run gets logged) can receive on-site credit for games if we happened to have one of these players at our table.
Nobody in my area has any interest at all in playing Core, at least not for the foreseeable future. It's something that doesn't even apply to us, as ALL our games and ALL our players are sticking with the regular campaign.
By not having had a better design in place for how you were going to implement Core reporting (without screwing up reporting for non-Core games), you've successfully made me even less thrilled about Core and less likely to ever want to try it. :-\
This isn't unfixable; I have faith you'll get it sorted out, Paizo, but please, do it quickly. A "new way to play" that makes it harder to report for people who don't even want to play the 'new way' doesn't do either side of the organized campaign any favors.
|
|
| 1 person marked this as a favorite. |
While its frustrating, its hardly game breaking.. as the Chronicle sheet is the most important thing for people. The reporting online comes a distant second. Please take the time you need to fix this issue properly.
While it is true that the physical chronicle sheets are most important for the players, the GMs rely upon the online reporting to get credit.
Time is of the essence. The longer this goes on, the larger the backlog will grow for unreported/under reported tables. As has been stated in the guide, "reporting is very important to the
success of Pathfinder Society Organized Play!"
|
Sorry but the push for a GM to get a new star is hardly a reason to rush the IT guys at Paizo in a flurry to resolve this.
' Oh man, that reroll would of so worked if only the IT guys at Paizo had of fixed the reporting system. I should have 3 stars not 2!'.
Im not saying its not important.. but how does that phrase work:?
'First world problems?'
| 1 person marked this as a favorite. |
Tracking GM credit is ONE reason why this is important to get fixed, and not the biggest one. Yes, in an ideal world, everybody is a perfectly organized person who keeps perfect track of their Chronicle sheets and has a nice typed and organized list ready to go so that they can tell you at a moment's notice which scenarios they've played and haven't played.
The real world is not filled with organized people, however. For many players, especially those who started as casual players and didn't fully grasp when they started that their Chronicle sheets were very, very important, the online tracking system is the most complete record they have of their play history. It's also already all collated in an easily searchable format, which casual and intermediate players may not understand the need to take the initiative to do on their own. Once you start getting past fifty or a hundred scenarios played, you either need to create a spreadsheet of your scenarios played in order to be able to remember what you have and have not played, or.... as many, many players do... you rely on the online tracker system.
I'm not saying that's ideal. I KNOW that the Chronicle sheet is the final 'proof' of your play, and that the burden of remembering things like that is on the player, not on Paizo's logging system. But at the same time, it's a reality that the online tracker IS how many players actually do keep track of and confirm their played sessions.
It's also a reporting tool for Paizo's benefit, to understand exactly where, when, and by who the games are being played. With the implementation of Core it's a way to track Core games versus regular games. It's in Paizo's best interests to have a reporting system that works, and allows for the actual reality of many players who a) don't register their characters and b) rely on the online system for logging purposes.
I don't think anybody is seriously arguing for "Paizo, rush to fix this even if you come up with a crappy solution!"
We're expressing frustration that a major change to the system was implemented (requiring that all characters to be registered, or logging can't happen at all) without (apparent) consideration of the reality that game reporting often involves unregistered characters... and that in the meantime, for as long as it takes for Paizo to engineer a solution, hundreds and hundreds of games are going unlogged (especially given several recent cons that will be impacted by this, DundraCon, Strategicon, etc.). Many of those games will probably never get logged at all, because the followup rate for GMs when they can't log a game the first time they try is likely to be low.
Calling the concern over this a "first world problem" seems silly to me. Being at all concerned over ANY ASPECT of something like an organized play RPG program is, by definition, a first-world problem. That doesn't mean we shouldn't be offering feedback on it, or expressing frustration.
|
The thing folks seem to be missing is that results from scenarios are reported to PFS leadership so they can take those results and shape future stories. That is why we now have A, B, C, and D check boxes for success conditions. As long as this persists these results are not being tabulated, which is hurting the overall campaign.
If it can't be fixed, at least give us a workaround.
Quality Assurance Axiomite
|
| 5 people marked this as a favorite. |
Hey everyone,
I'm currently doing QA testing for the next website update. When it goes live it should address the issues preventing PFS reporting. We're revamping a few different parts of the website so it'll take a bit for us to properly test it, but know that this issue should be addressed with the next launch.
The current issue is that the system checks to make sure that character types match the PFS game type being played to prevent mislogged events. Characters that haven't been registered yet trigger this as well since they don't match the game type being played, meaning that characters that haven't been created on the Paizo.com website cannot be reported. We should have this resolved with the next update.
- Erik Keith
|
|
If it can't be fixed, at least give us a workaround.
I recommend not reporting the characters that are causing the issue. If it does not pop up RPG when you enter their number, delete them. If the GMs character is not registered, do not add his character number, just his player number. You can report a table of zero players. (This is how Overseer GMs are usually reported) If the players later register their characters, you can add them in later. Since the reporting system is not the official record of experience, minor errors like this do not affect much in the grand scheme of things.
|
|
If it can't be fixed, at least give us a workaround.I recommend not reporting the characters that are causing the issue. If it does not pop up RPG when you enter their number, delete them. If the GMs character is not registered, do not add his character number, just his player number. You can report a table of zero players. (This is how Overseer GMs are usually reported) If the players later register their characters, you can add them in later. Since the reporting system is not the official record of experience, minor errors like this do not affect much in the grand scheme of things.
The issue is then we have to remember what we didn't report then go back and report it again. This may seem like a small thing to people who don't understand how busy other people can be but it really is a big thing for us from our perspective. For time constraints I really want to just report the scenario once and be done with it. Now I have players emailing me and asking me why their sessions haven't been reported.
I've had way too many times where I don't get all of the information from players at the game. They swear they will give it to me and nine times out of ten they never ever do and I am left holding the bag with reporting stuff.
It really is a bad thing for bugs to prevent us from even saving what we do have from my perspective.
|
|
The issue is then we have to remember what we didn't report then go back and report it again.
I am aware, but I do not think never reporting those characters is a crucial problem. If the players ever look to their sessions and notice it, they will contact someone about correcting it. If not, then it never comes up.
Now, if number of players is a truly important metric then it should certainly be a concern. But as it is right now, I don't see the quantity of errors to be significant over all. Erik or someone in the know is welcome to correct me.
Now I have players emailing me and asking me why their sessions haven't been reported.
You are correct that I do not have the workload that others do, and my perspective as a VL is a little different. So I will concede that it does increase your overhead, and I hope to see the bug fixed sooner rather than later myself.
The current issue is that the system checks to make sure that character types match the PFS game type being played to prevent mislogged events. Characters that haven't been registered yet trigger this as well since they don't match the game type being played, meaning that characters that haven't been created on the Paizo.com website cannot be reported.
Why not simply assign unregistered characters the type appropriate to the event being reported? At least then there would only be a reporting issue if and when a subsequent event of a different type is reported on that character. Right now you're foregoing a lot of data...at least some of which you won't ever be able to get back.
Is the idea that, by forcing people to explicitly register their own characters before they can be used, the character type is more likely to be accurate? I think that's a highly questionable assumption, since the owner of the character is the source of the data in either case. I'm lucky if people can remember their freakin' number sometimes. :P
|
| 2 people marked this as a favorite. |
I haven't been able to report my scenarios for weeks. I feel like I need to point this out:
to prevent mislogged events
This issue is creating mislogged events. The preventative measures are creating the issue they're trying to prevent.
Scenario reports are piling up that need to be logged.
Folks, the solution is in testing. Assuming it tests ok, that is the last step prior to release. There is literally nothing you can say that will make it go faster at this point.
That...seems a little harsh; I was trying to help. >:/
Edit: Do you even database, Wertz? :P
| 1 person marked this as a favorite. |
We understand the frustration, which is why we have prioritized the redesign of that component for the next release. I think folks are just asking that people keep an even keel and let us work out a solution that will work for both our internal needs as well as all the players.
We do appreciate your feedback and the solution we're implementing is very similar to what Bugleyman suggested, just a bit more complex ('cause things are always more complex than you would think on the back end). Things are in testing now, but we want to let the Goblins pound it a bit and make sure it's reasonably solid, or at least well armored against dogslicers.
We appreciate the updates, and we know it's probably a thorny knot on your guys' end. Thank you.
|
|
Is there and ETA/time line on when this "next release" will be in place? I am asking, as I have several events over the next week, or so, and if the issue will likely be resolved soon, than I'd rather just wait to enter the information, versus adding to my stack of events that are missing data.
Don't worry, BrewCityCrafter- I have your data from two weeks ago, and I'll enter it once this is cleared. ;)
I plan on getting our people who attend tomorrow to register the characters to assist in reporting the scenario from 2 weeks ago.
See you tomorrow!
-- Steve
Fix is in testing. I will note that if all the characters have "claimed" their characters (e.g. registered the characters they received as cards) then reporting should work as it is currently. If you have a pro-active group of players, just have them register their characters and you can report immediately.
|
|
Fix is in testing. I will note that if all the characters have "claimed" their characters (e.g. registered the characters they received as cards) then reporting should work as it is currently. If you have a pro-active group of players, just have them register their characters and you can report immediately.
Cort, how I wish it were that simple! :)
Thanks for working the kinks out of this. Those of us with conventions and regular gamedays know that more often than not our players tend to be a little lax when it comes to registering each character they play after their first. I've been noticing its even worse for reporting for the card game OP campaign. I've stressed it though! :)
That's... interesting. It's been very consistent in our testing. Are you sure he/she gave you the right character ID?
|
Chief Technical Officer
|
Folks, the solution is in testing. Assuming it tests ok, that is the last step prior to release. There is literally nothing you can say that will make it go faster at this point.That...seems a little harsh; I was trying to help. >:/
Edit: Do you even database, Wertz? :P
Instead of picturing me as William Shatner at a sci-fi con telling you "Get a life," picture me as Scotty in the engine room telling you "I cannae get na maer powaer, cap'n!"