howandwhy99
Adventurer
The thing is, the key to those maps is really my game, or at least part of it. It's some of the code my players are attempting to decipher as they play. That means I can't really share it without risking them learning it or at least disseminating something I'd rather be using over and over again for a good while.
To give you some inkling though what I do is simplify (x3). Knowledge is treated using an information model with bits fading from memory and arranged along the lines of systems theory. Mind maps are easy enough to find for what I'm talking about. It's the relationship lines and what counts as what for those bubbles of info that are determined by my map key. My hint is: aggregate whenever possible.
A calendar map is really everything you might imagine an early D&D module to be. It's a spacial map with a description of each area highlighting what will be there when and for how long - basically what's going to go on where. This future timeline is the scenario and progressed forward between each session, but it's not too hard to prep if you know your key. (plus it's fun like generating out the potential outcomes of a sim game). Just map enough space and time to cover an average session depending upon the PCs levels. Tracking what happens during a session is often as easy as dragging a pencil behind the PCs on the map for the trail they leave & time markers for when they left it. (This helps for tracking PC knowledge maps too, if ever they become NPCs [and you've opted for that as possible in your game]).
Well, I hope that helps. I can at least give you a Dawn Patrol picture
