|
Both me and a friend about to be running home games with some friends. I offered to manage the book-keeping(event tracking)
It appears that you can add additional "session" to a single "event"
The question I'm trying to ask is thus:
Should I add new "events" every week or so when we play, or should I simply add additional "session" to a single event for our home group?
Taxonomy always feels like the most inconsequential thing, but when it's not per the "norm" it usually causes problems, so I'm asking here before an issue comes out of it.
Venture-Captain, Michigan—Mt. Pleasant
|
While not an official answer, I don't really think it matters a whole lot which way you do it. I will tell you from experience that after a while if you keep it to one event it starts to get very messy. I tried it for a couple of months, and it got confusing for me. I don't confuse easily, for what its worth.
|
|
The last time it was asked, they wanted separate events created.
More specifically, the post I saw recommended a public event be created as separate events so it would show up on the calendar. For your home game, I would imagine it would be fine to keep using the same event.
(Unless, of course, I've missed something important. That happens from time to time.)
|
I had the opposite experience to Eric; I had a different event for each week of our local gaming club, but keeping track of a whole list of events with different event numbers and reporting against each of them got unwieldy. Now we just have one event which I update from week to week. It appears in the event list fine.
Maybe I'll end up switching to a new event in a few months when the list of sessions gets too long; we'll see.
|
Venture-Captain, Texas—Waco
|
Wow. Surprising 3 people feel its easier to keep track of things with a billion tables under one event.
I also use one event code per location and just add event dates as necessary. Much cleaner than 98 different events! It also makes it faster to find and edit a specific reported game so long as I know where the game was played.
Frankly, I'm a long, long way from having a BILLION tables under one event. :P
|
|
Thanks for all the advice guys. Personally I think the single event code will make reporting easier, since it's easier to remember a single number for our chronicle sheets.
Especially thanks Jon, It was nice meeting you at Anime Fest, I'm sure I'll see more of you at other Conventions in the area. :3
|
Wow. Surprising 3 people feel its easier to keep track of things with a billion tables under one event.
Personally, having ONE event code tied to one date is what makes the most sense to me. Makes it simple to go back after the fact and edit tables.
Finding the specific event for the specific date is actually harder than scrolling through a date-ordered list of tables in one event. Browser search functions are also your friend. YMMV.
@Rixius: Glad to have met you, too. Hope you guys can make it out to some of our gamedays.