Out Of The Basement Podcast – Episode 85

October 3rd, 2019

The boys get together to talk about various geeky topics, including video games, RPGS, MMOs, movies, comics, etc. In this episode, we are joined by Patrick Ramsahoye, and our main topic is a discussion about what might be coming up for Marvel Studios, now that Phase 3 has officially come to an end..

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.

We’d like to thank Radio Free Music for providing our new Intro and Outro music. The first track is called Drop and Roll, the second Grand Navy Plaza. Both are by an amazing artist called Silent Partner.

Out Of The Basement Podcast – Episode 84

September 6th, 2019

The boys get together to talk about various geeky topics, including video games, RPGS, MMOs, movies, comics, etc. In this episode, we are joined by Patrick Ramsahoye, and Dwayne McKinnon, and our main topic is a discussion about toxic fandom.

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.

We’d like to thank Radio Free Music for providing our new Intro and Outro music. The first track is called Drop and Roll, the second Grand Navy Plaza. Both are by an amazing artist called Silent Partner.

The Force Is Not Always With You – Episode 66 (Season 9-3)

August 12th, 2019

In this social episode, Alan, Dan, John and Jen and Alain spend their time planning (kind of).

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.

Battletech: Homebrew Simultaneous Movement Rules

August 2nd, 2019

Back when dot matrix was the printer of choice and Windows 98 was the best option for an OS, I came up with a set of rules for simultaneous movement in Battletech. The regular miniatures game was fun, but I had gotten into flight simulators on my computer and I felt the experience could be better. What I came up with added some complexity to the game, but it also became the preferred rule-set among my friends.

My original rules have been lost to the vortex of forgotten file formats. What I present here is what I remember of them with a few modifications based on experience, new ideas from other games, and “this makes more sense” moments during my recollections.

I haven’t had a chance to read the latest Battletech rules, but if the Harebrained Schemes computer game represents them well, it shouldn’t be hard to adapt what I am presenting to them.

Step 1: Planning Phase

I introduced a turn record sheet. It had columns for starting hex, movement type, hexes moved, ending hex, and ending heat. The starting hex may seem redundant after the first turn, but melee combat can change a mech’s position before the end of the turn.

Each side was given a few minutes to plan their movement. In a multiple lance situation, if you want to simulate command structure, the unit commander can give orders to the lance commanders who work with their lance-mates to figure out a way to execute those orders.

Since both sides are using the same map, it is best to do as much calculating in your imagination as possible. You don’t want to be giving too much about your tactics away.

Movement type is important for determining how many movement points a mech has as well as movement penalties during combat. Hexes moved helps determine all mechs’ movement as well as defensive targeting modifiers.

Step 2: Movement Phase

Mechs move based on weight class. The heaviest mechs move first. This reflects the relative agility of lighter mechs. I developed these rules after the Mechwarrior RPG came out. Players get one opportunity during the movement phase to make a tactics roll to change their plan once movement has started. They have to keep to their movement type.

First determine initiative. The side with the winning initiative decides if they want to move the first mech or the last one for all of the weight classes. One decision applies to all of the mechs.

The heaviest weight class on the board moves first based on initiative. If there are an uneven number of mechs in a class, work out a ratio so that initiative is kept. For example: the side with initiative wants to move the last mech and has two mechs of a certain wight class to the other side’s four. The side without initiative moves two mechs before the side with initiative moves one.

As another example: the side with initiative wants to move first and has three mechs to their opponent’s two. The side with initiative moves two mechs, their opponent moves one, then each side moves one until all the mechs of that weight class have moved one hex.

This continues until all the mechs in the weight class have moved one hex. All movement points spent in hex (facing changes, terrain modifiers, etc.) are spent at this time. This means a mech will be facing its direction of travel before moving into the next hex.

The next heaviest weight class moves the same way, then the next heaviest, until finally the light mechs move. Then movement goes back to the top with each mech moving just one hex.

It is likely that some mechs will use up all their hexes before others do. Once it has moved into its last hex, its movement has stopped. The other mechs continue as normal. This could break initiative. If only one side has light mechs, they will always be moving the last mech.

As I mentioned earlier, each pilot has one opportunity during a turn to make a tactics roll to change their planned movement. The first movement point change is free. Each one after the first they intend to change adds a +1 to the difficulty roll. For example: a pilot wants to eliminate the last planned facing change and continue in a straight line for two hexes instead of one. They only have to make a normal difficulty tactics roll. If the pilot decides not to make a facing change and as a result not make an elevation change, the tactics roll gets a +1 difficulty modifier.

Step 2B: Mistakes

A mechwarrior planned out their movement and as they make the moves they realize they don’t have enough movement points to reach their declared last hex. They have to make a piloting roll with a penalty based on the number of movement points they miscalculated On a successful roll they stop in the last hex they could legally enter. Any unused movement points are lost. If they fail the piloting roll then they skid based on their velocity and direction of travel before any facing changes may have happened. This could result in a fall or damage from charging a terrain feature.

Step 3: Reaction Fire

This is something I borrowed from the sadly maligned Battletroops game.

Mechwarriors can decide to spend movement points setting up a reactionary arc of fire. Setting up reaction fire ends the mech’s movement.

Even though the mech is not moving, setting up and widening the reaction arc counts as hex movement for the purposes of plotted movement. Also, since the mech has stopped moving, any mistakes made calculating movement point requirements simply means an arc is not set up or widened properly.

The first movement point sets up an arc through the hex-side the mech is facing. The next movement point adds the hex-side to the left or right of the first. A third movement point adds the hex-side to the left or right of either of the previous two. If the final three hex-sides do not match the initial forward arc of the mech, it is considered to have done a torso twist.

Any enemy mechs moving through that arc can be fired upon using any weapon that has the range to reach them. The firing mech’s movement type and the targeted mech’s total planned number of moved hexes count towards determining the gunnery target number. This is the only time weapons can be fired during movement. Any damage is applied immediately. This damage can potentially disrupt the target’s movement.

Weapons can only be fired once during a turn. Any unfired weapons can be fired at a second mech moving through the firing arc. Secondary target penalties apply. Any weapons not used during reaction fir can be used during the regular fire phase. The secondary fire rules still apply. If only one mech was targeted during reaction fire, a fresh mech can be targeted as a secondary target during the fire phase. If two mechs were targeted during reaction fire, then any weapons held for the fire phase must target one of those mechs.

The turn after a mechwarrior sets up a reaction fire arc, they can maintain that arc or expand it to any three consecutive hex sides at no cost so long as they do not move. One facing change is allowed for free. Any other movement destroys the established reactionary arc and it must be started again. Already established reactionary arcs exist at the beginning of the turn. Reactionary fire can only be made against mechs that move in some way. This includes facing changes.

Step 4: Melee Combat

Kicking and punching occur after the fire phase as normal. Charge and Death From Above attacks can only happen as accidents or unplanned opportunities

Any time two or more mechs end a step in the same hex there is a chance for a collision. Unless the conflicting hex is being used for landing, jumping mechs only risk a collision with other vehicles. All involved mechs make unmodified piloting rolls. If they succeed they can choose to react to this situation. If they fail they at the mercy of the other player or fate.

If all involved mechwarriors failed their piloting roll, then they all automatically make charging attacks against each other. Airborne mechs that are successfully charged (intentionally or accidentally) take damage from a level three fall (assuming they are over level zero terrain) and end their movement prone in the last hex they occupied before the conflicting hex.

Any mechwarrior that succeeds can chose to make an appropriate physical attack (charge or DFA) or they can choose to avoid contact. If more than one mech is involved, an attacker must chose which mech to target. If the attack is successful, the untargeted mechs are subject to being pushed.

If two mechs decide to charge each other, the charges are automatically successful. If one chooses to dodge, the pilot makes a piloting roll. If successful, the charge attack is automatically dodged. If the pilot is dodging more than one charge attack, a +1 modifier is added to the difficulty for each additional attacker.

If the dodge is not successful, the attacking mechwarrior still has to make a normal charging attack. If more than two mechs are involved and only one chose to dodge, if the dodge is successful then the two attacking mechs charge each other.

Damage from mid route collisions happens immediately and will end movement for any mechs that fall. Mechs that remain upright can continue their movement as normal. Charging attacks in the last hex of DFA attacks are resolved during the melee attack phase as normal.

If the collisions happen during a jump, any mech that was not the recipient of a charge attack can continue their movement as normal.

Death From Above attacks can only happen if a jumping mech and a ground based mech end their movement in the same hex. A jumping mechwarrior that has not already used their tactics roll, can use it to set up a DFA attack provided they have enough movement points to do so.

If two or more mechs using any movement type will end their movement in the same hex there are two options. First, an unused tactics roll can be used to end movement in a different hex. If this results in a collision also, follow the collision rules above. The other option is one or more mechwarriors may chose to initiate a charge attack. Resolve this normally.

This ends simultaneous movement. The remainder of the turn happens normally.

Variant Option

While it can be done with the regular rules, a double-blind setup works especially well with simultaneous movement. There is a game master/referee who controls the main map board. Each side has identical maps, but they only have their pieces on the board until the enemy reveals themselves in some way. Once the sides are revealed to each other, planning is done on the faction maps, but movement is plotted on the main map. This adds a powerful fog of war element to the game.

Review of the Clones – Episode 10: Invasion of the Body Snatchers

August 1st, 2019

In today’s episode, we are joined by our friend Patrick, as we do a full blown comparison between the original 1956 version of Invasion of the Body Snatchers, and the 1978 remake.

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.

Out Of The Basement Podcast – Episode 83

July 30th, 2019

The boys get together to talk about various geeky topics, including video games, RPGS, MMOs, movies, comics, etc. In this episode, we are joined by Patrick Ramsahoye, and our main topic is a discussion about whether the Replicants in Blade Runner qualify as AI/Androids.

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.

We’d like to thank Radio Free Music for providing our new Intro and Outro music. The first track is called Drop and Roll, the second Grand Navy Plaza. Both are by an amazing artist called Silent Partner.

The Force Is Not Always With You – Episode 65 (Season 9-2)

July 29th, 2019

In this episode, Alan, Dan, John and Jen and Alain meet with a shady business man.

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.

Filling in the Blanks

July 26th, 2019

In the early days of the Internet, one of my Dungeon Masters did something innovative. He had one of us take notes which he used to email us a summary of that session. We had details about what happened, XP summaries, wound summaries, and a list of the treasure found.

I’m sure session summaries are fairly common to most tabletop RPG sessions now. If you’re not using them, they can really help the experience in several ways.

First, I hold off on sending a summary out until a few days before we are scheduled to play again. This serves as a reminder that we are playing and it brings the players back to where their characters are paused in the adventure. This is especially helpful if there is a large gap between sessions.

The summary also gives me an opportunity to provide any information I might have forgotten to mention while we were playing, to flesh out details (especially useful if I’m working out an encounter on the fly), or to retcon details to better suit the narrative I’m developing. With respect to that last point, I don’t make major changes, just ones that help put past or future events into context. For example, maybe a guard cries out an alarm as the fighter cuts him down even though that wasn’t mentioned during play.

Lastly, these summaries help me remember details about what happened as the campaign moves forward. I might be looking for something to do for the next encounter, review my summaries and remember that a minor villain managed to run away from a fight sometime last year. Time for her to make a reappearance with vengeance on her mind.

One of the things I like most about being a Game Master is the ability to tell a story. But this also provides me with my biggest frustration. I put time and effort into building an encounter. I know how it fits into the bigger picture. I know why an enemy is doing what they are doing. However, for the players these encounters are usually just stops along the plot path. They might figure out some of the details, but they never get the whole story.

That’s what makes other narrative styles, such as books or film, so engaging. The audience can be let in on information that characters would never get.

Recently I stumbled upon a way to give the players this information without giving away the whole plot, and it involves session summaries.

The party in my current D&D campaign are trying to build up to starting a civil war. They are looking for allies in the upcoming struggle. They happened across the Druids of the North. The druids were concerned about recent events which were the reason the party wanted to overthrow the current government. However, the Druids wanted to be sure the party’s intentions weren’t at odds with their own. They gave the party a task.

The fire giants and frost giants had gone to war. While the Druids would normally stay out of the conflict, the collateral damage from the war was having a serious impact of the lands and creatures they swore to protect. The Druids tasked the party with finding the cause of, and hopefully a way to end the war.

The players were able to discover that the fire giants were wrongfully accused of stealing a holy artifact from the frost giants. In retaliation the frost giants kidnapped the fire giant king’s daughter. The players were able to figure out through divination magic that the real culprit was a cloud giant.

The party made their way to the cloud giant city and began making inquiries, a little too obviously. The cloud giant got word and sent his henchmen to ambush the party.

I built an interesting group of henchmen. Each had their own reasons for working for the cloud giant. None was a cookie cutter character. The ambush happened. The party was victorious. All the backstory I had worked out faded into nothingness.

This is where I used the session summary to make my hard work as interesting for my players as it was for me. I told the summary from the point of view of the ambushers. I began with the cloud giant giving his henchmen their orders. I showed how the henchmen were connected to the tiefling rogue that set up the party. I was able to show that the cloud giant operated a museum and that the frost giant relic was taken to be part of the collection. I was able to explain who each of the henchmen were, and touch on why they were doing what they did. I was also able to show how each companion’s death impacted the survivors among the henchmen.

My players loved it. They told me it was one of the best summaries I ever gave them.

I’ve used that technique a few times since then. I don’t make every summary about the villains. It only happens enough to let the players in on information their characters would never get.

If you like to use summaries to keep your players up to date, I would recommend shifting the point of view once in a while. It helps give your world life and lets you tell more of the story.

Paul’s Workplace Rants – Episode 1

July 24th, 2019

Today, we introduce a new podcast on the OOTB network, a show where our co-host Paul records rants while working at his blue collar job. These will be free flow, unscripted segments, on a variety of topics. This first episode, unsurprisingly is about Star Wars. The audio quality isn’t great, and he’s frequently interrupted by chatter over his CB radio, but he believes its all part of the charm of a workplace rant, and the quality will improve as he looks into technology to make recording the rants a bit clearer and smoother.

These episodes will be released monthly (or more often, if Paul finds topics to rant about). This first episode is available on our regular OOTB feed, but if you want to hear future episodes, you’ll have to join us over at Patreon and become a subscriber.

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.

We’d like to thank Radio Free Music for providing our new Intro and Outro music. The first track is called Drop and Roll, the second Grand Navy Plaza. Both are by an amazing artist called Silent Partner.

The Force Is Not Always With You – Episode 64 (Season 9-1)

July 1st, 2019

In this episode, Alan, Dan, John and Jen and Alain have a new task.

The episode can be downloaded directly from the following link, or automatically downloaded if you have already subscribed to the RSS feed through iTunes or any other feed reader.