In RPGaDay 2025 Day 4, I responded to "Message" by talking about how difficult it is to communicate long-distance without telephones. This is an update after a reader reminded me of sempahore and other signals at a distance.
RPGaDAY 2025 day 4 has the prompt “message”.
It’s easy to forget in these days of email, text, instant message, and social media, just how much effort it was to send a message in the mediaeval days which are the pattern for classic fantasy.
So how can your characters and the people in their world send messages?
RPGaDAY2025 Day 2 has the prompt "prompt".
I look at promtness in combat, and prompts to aid the players and GM in ensuring that responses are indeed prompt.
RPGaDAY 2025 launches tomorrow, 1st August, and runs all month. Join in and follow along with the hashtag #RPGaDAY2025. Here are the prompts provided by @autokratik and @runeslinger
RPGaDay 2024 days 2 and 3 - most recently played and most often played RPG. Both the same - lightly house-ruled D&D 5E, so here's the story of the last couple of sessions in my cmapaign
It’s #RPGaDay time again. August. When a whole load of RPG fans talk about our hobbies in various ways. I'm late to the party, but I'm still going to take part.
RPGaDay prompt 6 is “favourite game you NEVER get to play”. I’m going to pick Bruce Heard’s Calidar here, a massive new world in three installments (so far).
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.