I have upgraded to MT4 but its only sorta compatible with my old templates and things, it also seems to have broken comments. I'm just going to go ahead and do a full re-install of the whole system, hopefully that won't take too long.
April 2008 Archives
So I'm really neglecting the blog these days. I'm not sure if they last post even counts since really all I did was post an email I had written. The capstone course from hell is finally over. It wasn't all that bad really it just took up A LOT of my time, which I never have enough of.
Elanna and I are still training hard for the MS-150. Only about a week and a half left now. We can easily ride about 40 miles in one go. I'm not sure if that translates into being able to complete 80 miles in one day but I guess we'll find out. The weather is really hampering our training right now. If its not cold it's windy, if it's not windy or cold it's raining. I think so far since we started training we've only had one day where it was not windy or cold or both.
Our house is still on the market but we've only had one person look at it so far. I think that means we'll have to lower the price soon. The agent is doing an open house next weekend so we'll see how that goes.
In the meantime we may have found a new house to buy. It's bigger than what we need and needs some work but has everything else we are looking for. The location is great, right off 121 in Grapevine. That alone will cut my drive time to work in half. WOO - HOO!
The next and FINAL Masters course starts next Saturday. Digital Forensics, which sounds a lot more interesting than it is. It could also be called "How to read log files."
A friend emailed me today and asked for advice on running a new RPG campaign. My response turned into a long email and since I'm really lacking in the blogposts I thought I would repost it here.
Read the section of the rulebook on running the game. Those sections usually have some pretty good stuff. Some other books that have good general GM advice are the 3.5 D&D Dungeon Masters Guide and any of the newer White Wolf rulebooks. Just the sections on how to run a game. The parts that pertain to the storyteller and D&D system specifically aren't all the useful, of course, unless you are running one of those games.
Other thing I try and do is to be prepared. Read through the adventure and make sure you've got the general plot down and think about how the players will go through the adventure. If the adventure wants the PCs to go from point A to point B then think about how to get the players to do that. Sometimes you have to change some things so the adventure moves in the direction it's supposed to.
For example, in my last Delta Green game, the players get attacked by some Mi-Go and cultists. The adventure assumed that when faced with monsters and cultist that the players would run off into the jungle which would lead them to discovering the Migo's lair. I knew that would not happen. The players would stand there and shoot the cultists till they were all dead or the cultists killed them. My plan was to have anyone who failed their SAN check run off into the jungle and discover the entrance to the liar. If no one had gone insane I was going to have one of the Migo fly off in that direction.
Some adventures have really complex plots, in that case I make a"cheat sheet" in a notebook that outlines how I want the plot to flow. That when I am running the game I can glance at it and see what I had planned to happen next.
Another thing to do is to prepare for any combats that are going to occur. In a fantasy game a lot of times the players will be fighting a monster with special powers or a wizard that has loads of spells. I try and read up on the rules for the powers and spells of anything the players are going to encounter in the next session. I don't memorize the rules but I try and know enough about the monsters abilities so I can decide if I want it to use them or not.
This website has some good advice http://www.treasuretables.org/ as does this one http://www.treasuretables.org/wiki/index.php?title=Main_Page.
