|
As a coordinator you set up an event, then report all your tables through that event (they show up on your event as Event xxxxx, Session yy).
So, for instance, a 4 day convention will have a single event number, and the 300 tables run during that event will be sessions 1-300.
Another for instance: I do a single event for my store's PFS games: PFS at Enchanted Grounds - 2013. It will end up with around 280 sessions and I will complete its reporting in January next year when I start a new event.
This keeps us from having to do new location info, scenario selection, etc. for every event we set up. It also keeps it very easy for us to find errors and fix them, or to figure out what that (illegible) PFS number actually is (I can do a search on the event page for the PC's name and get the number that way).
Doing a separate event for each day would make all this extremely tedious.
Edit: The only time an event number really matters in terms of "legality" is whether an event has enough sessions to qualify for convention level support. Those events must have at least 15 sessions that occur during a 3 day span.
|
Think about it like event = player, session = character
644-101 was yesterday's session of Throathy Mermaid. Yes - this is the Sunrise Lodge - running for >3 years now and we just managed to get past 100.
I only apply for new events
Each year for a convention in London which I organize
For special events like weekends 'cons' where I invite multiple player from elsewhere and where we do multiple scenarios or >1 module
As Drogon mentions - he seems to do similar at his shop. Only he changes each year while I'm proud I still have this low event number.
Others might generate a new event code every single time - but this is recurring - Wednesday evenings - for 3 years now.
|
Yeah,around here each store will only have one "event" listed in the system. I generate new ones each year for my conventions, but the store event code will be the same until I need to hand over the organizing duties. Drogon already explained the main benefits of doing it that way and the main drawbacks of the alternative.
But yeah, though the event code is the same, the session code is what you need to be concerned with.