|
I try and report a scenario I ran last Sunday and it is not letting me pick the actual scenario. In the drop down list for it all it has is "Pick a Scenario"
My event number is 5066 #26
The Date is 07/17/2011
The Scenario was "The Throaty Mermaid"
Thanks!
Deanoth
p.s I hope I put this in the right place as I was unsure as to here to put it.
Director of Brand Strategy
|
This is an extremely annoying change for ongoing events. Picking from a long list might be a slight hassle, but loading up the Edit screen every time you want to report is far worse.
The idea is that you check a specific scenario a week or two before you run it, so it shows up for someone searching for your event, and then when you're done reporting it, unclick it so it doesn't look like you'll be offering it the following week for new people who happen upon the event through the search. If it's too large a hassle, you can just keep them all active at all times and they'll all show up on the dropdown every time you report a session.
|
| 1 person marked this as a favorite. |
The idea is that you check a specific scenario a week or two before you run it, so it shows up for someone searching for your event, and then when you're done reporting it, unclick it so it doesn't look like you'll be offering it the following week for new people who happen upon the event through the search. If it's too large a hassle, you can just keep them all active at all times and they'll all show up on the dropdown every time you report a session.
I dislike this as well - for our group, often, scenarios aren't finalized until we know who is showing up. I understand that it's nice to be able to advertise running a specific scenario in advance, just in case someone nearby wants to drop in to play specific mod. But for isolated groups, it's just more work for no real benefit. It is definitely a pain to have to update the listing after the fact, just to be able to report. I don't like leaving all the scenarios checked as a solution either, as then anyone who *did* drop by unannounced would have seen what amounts to false advertising.
If there isn't a compelling reason for this change, I'd prefer things went back to the one-step reported we used to enjoy.
|
The list of options selected is meant to support events where specific events are being run. Regular games which may draw from the pool at any time are difficult to set-up this way. By selecting every single module for an event, you're missing new modules when they come out and need to constantly update your event list. If you don't select any specific modules, everything will always be available when you go to report.
Mark has indicated in the past that it is Paizo's preference that a new event be created for each event being hosted. A 3-day convention would be an "event", as would a weekly play session. By consolidating all your events into a single event, it actually under-represents your efforts. You also quite literally fill up the entire search screen with a list of dates when you continue to add dates to one event.
Venture-Agent, Indiana—Lafayette
|
just my two coppers:
Paizo's preference makes complete sense and works fine for conventions that have a clear beginning and end or possibly even for a monthly FLGS event. However, it is cumbersome for a FLGS event that runs twice a month or more.
As for the long list of dates for the event. I have been deleting past dates for our FLGS event (except our initial) so that the focus is on what's to come. As I type this I realize that removing past dates may muck up some of Paizo's tracking, I hope not.
Ideally there would be an initial check box when creating an event that allows for two different formats, one for one time events like conventions and one for continuous events like home PFS and FLGS play. I realize that this would require significant tech time and may not be very practical.
I don't understand how keeping a bi-monthly PFS event at a FLGS 'under represents one's efforts'. I am apparently missing something.
|
|
just my two coppers:
Paizo's preference makes complete sense and works fine for conventions that have a clear beginning and end or possibly even for a monthly FLGS event. However, it is cumbersome for a FLGS event that runs twice a month or more.
As for the long list of dates for the event. I have been deleting past dates for our FLGS event (except our initial) so that the focus is on what's to come. As I type this I realize that removing past dates may muck up some of Paizo's tracking, I hope not.
Ideally there would be an initial check box when creating an event that allows for two different formats, one for one time events like conventions and one for continuous events like home PFS and FLGS play. I realize that this would require significant tech time and may not be very practical.
I don't understand how keeping a bi-monthly PFS event at a FLGS 'under represents one's efforts'. I am apparently missing something.
I run bi-monthly at our FLGS and haven't had a problem with events. The clone button is especially handy in this aspect. Until recently I had all the mods I'd purchased checked as we were on a 'i'll run what we can put together' kick. Recently I've scaled that back to the last Season + a few mods. It's really no issue at all to clone your last event and make what mod offering changes you need to on the clone.
Reporting the weeks events in each seperate one is absolutely no issue at all as it's literally only one or two extra click to report two whole events instead of one.
As for deleting old events, I wouldn't think it would matter much *unless* you had reported mods on those events. In which case it may now be reporting that those mods never got run.
|
From what I gathered from Marks post about this, and his comment on my reply post, is that they only wanted New Events for actually new Events.
If you are running a Bi-Weekly event, keeping it all in one event instance was fine. But if you did something outside that Event you should put in a new one.
Edit: And for those who are annoyed with the new system of only showing in the drop down what you have selected, I think a good thing to add would be a Select all button that auto selects everything as they are added.
|
|
I've been running scenarios somewhat regularly for the last couple of years (only a 2 star GM) and suddenly with the inclusion of core reporting is "all screwed up."
Apparently, if one of my players (brand new people that don't really understand the reporting, or in this case 2 brand new people and one LONG time player that may have poor attention to detail) accidentally clicked on the wrong box and created their character with the core flag when they are in fact 'normal' PFS (rpg?) they block the GM from being able to report the event at all. Alternately, my assumption that the RPG box is for 'normal' PFS and the PRC stands for "core" is incorrect.
This is incredibly frustrating, as it's taken me over an hour to attempt to report my most recent session. And I'm not 100% sure i did it right.
|
|
I've been running scenarios somewhat regularly for the last couple of years (only a 2 star GM) and suddenly with the inclusion of core reporting is "all screwed up."
Apparently, if one of my players (brand new people that don't really understand the reporting, or in this case 2 brand new people and one LONG time player that may have poor attention to detail) accidentally clicked on the wrong box and created their character with the core flag when they are in fact 'normal' PFS (rpg?) they block the GM from being able to report the event at all. Alternately, my assumption that the RPG box is for 'normal' PFS and the PRC stands for "core" is incorrect.
This is incredibly frustrating, as it's taken me over an hour to attempt to report my most recent session. And I'm not 100% sure i did it right.
Nice necro, especially since there are several live threads on this issue.
The web programmers are working on fixing the issue, as reported in those other threads.
If you need to get the session reported immediately, for some reason, you can report only what the system will take, the registered players with registered PCs, and then come back, after the issue is resolved, to add in the other players and PCs giving errors.