|
Post by james p on Nov 9, 2022 13:46:27 GMT
Hi folks,
No rush on this at all.
The recent Kantas milestone of 1,000 sessions got me thinking ...
Could there be any mileage in including session numbers in rumours as helpful references?
I don't know if the benefit is worth the time to put it in motion - so I'm raising it as an open question to see if the big brains of Kantas (1) can see some reasonable benefits, and (2) can see a way of implementing it which would be relatively low hassle.
Optimistically, if we're keeping count of sessions somewhere anyhow, then I was hoping that this might not involve too much additional effort? Wishful thinking, perhaps.
Potential Benefits: + Simple, clear references + Faster, more reliable searches of forum + Concise means of referencing in Discord chats, Loot threads, RPs, etc
It would also provide quite a neat means to concisely summarise lists of related sessions, for example if doing a meta write-up for a story arc, season finale, or for a particular PC. Skimming these session numbers would also give a directional indication for how much time had passed between those events.
A second, watered-down approach to consider would be to make available a version of whatever, numbered, master list is already being maintained - so that players can read session numbers from that if they wish instead. I guess this might make for less admin, but more scope for user error by players?
Interested to hear your thoughts, and if you can see a simple enough way to make this work, that also feels worthwhile for our awesome volunteers.
|
|
|
Post by andycd on Nov 9, 2022 16:31:45 GMT
Hey James,
Thanks for this! Had a think about it as a team, and it's one of those that's good in theory but in practice it's not going to be as useful as one might hope.
Session titles are already unique, and more memorable than a number. Searching a number on the forum (which has an awful search function at the best of times) is also not likely to be more effective than just using keywords, especially with the idea of back-dating those references? Otherwise it's only useful for sessions over 1000 which means it'll only help with the most recent sessions that people remember anyway?
The additional admin will in particular make this, we think, infeasible. Imagine the scenario of all the KDMs planning our sessions for the week, then numbering them, then someone cancels a session and someone else puts in a last minute session and suddenly we have to renumber everything else twice. We could maintain a spreadsheet perhaps, but then everyone else referencing a session that then needs to be renumbered is now wrong and it'll get tangled and messy very very quickly. Perhaps only number the session after it happens? But then people who are quick on their writeups have to remember to go back and update the labelling? Eek.
Basically - we see the idea, but the hassle will very quickly outweigh the benefits in an already high admin game. I hope this makes sense? Appreciate the thought that went into this though, always good to think through how else we could do things!
|
|
|
Post by james p on Nov 9, 2022 16:59:07 GMT
Thanks Andy (and team) for giving it your consideration.
Your response makes complete sense to me - any potential rescheduling would definitely be very onerous, not to mention confusing as well.
|
|
|
Post by james p on Nov 9, 2022 17:09:10 GMT
On reflection, it speaks to the smooth effectiveness of the session planning and scheduling operation in Kantas, that I hadn't really considered the uncertainty of rescheduling. The player-side view almost always sees a very stable, swan-like result of published rumours and sessions delivered, without all of the frantic paddling that might be going on underneath 😂!
|
|