OBT Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

AU Developers - Please PM Knightmare or MechRat if you need board or permission changes

Pages: [1]   Go Down

Author Topic: Primer for Interstellar Operations  (Read 3278 times)

0 Members and 1 Guest are viewing this topic.

bjorn

  • Menig
  • *
  • Offline Offline
  • Posts: 11
Primer for Interstellar Operations
« on: October 26, 2011, 09:30:14 PM »

I recently was pondering the Inner Sphere in Flames game from the old Combat Operations sourcebook. I have attempted to GM and play heavily modified versions of these rules on at least five occasions, focusing the game either for 3025 or 3039 eras, and none of the games survived more than two turns. While ISIF has a solid premise, I think the rules are largely unplayable, needing radical revision. Moreover, I do not think this ISIF really had a good battletech feel to the rules system. This got me thinking of what I would do if I was creating a system from whole cloth for a game like ISIF. I thought I would share as a way to start a dialogue on what other people would want and avoid from a set of rules to simulate strategic and operational conflict in the battletech universe.
1.   Keep it fairly simple. Just the general scope of the game can be daunting, when one is dealing with thousands of planets and hundreds of regiments. Try to keep the game streamlined and fairly simple in its overall rules, and only add complexity when absolutely needed to impart the feel of the battletech world.
2.   This is a game about precious war machines, and every machine needs to be directly represented in force calculation. In the Battleforce 2 handbook, Brian Nystul mentions that Battleforce 2 was revised so that players could comfortably play a battalion or more of forces in one game session. Each Mech was abstracted down to just 6 numbers, allowing the game to flow well but still maintain the feeling of a battletech game.  I have found that Battleforce 2 has been then most playable version of the game that I grew up playing and think we can learn a lesson from this system. I thought as a working model, when developing a regiment of mechs, we should fill it with mechs based off of weight class or (ie light, medium, heavy or assault) or by role (fire support, assault, scout… ect.) Each type of mech would have a defensive and offensive value, and you would add each mechs value together when calculating the units overall value. You would compare a units attack verse an enemy’s defensive value and role on a chart, and then calculate how many mechs were destroyed (the mechs would be like hit points for the formation). This does not have to be limited to just mechs, all sort of combat vehicles can be given values, and added together to calculate a unit combat values.   
3.   Battlemechs should be the Kings of the battlefield, but not exclusive. We play this game because we love big stompy robots, but ASF, infantry, and combat vehicles have their place as well. Mechs should have certain advantages, such as being more resilient, or quicker to return to the field.
4.   Each planet should be represented as an objective. I played one game that tried to collect planets into grids, it did not feel like battletech.
5.   Armies should be forced to stay relatively small. It should be difficult to rapidly increase the amount of mechs in house armies. I think this should be done by strictly limiting the amount of mechs that can be build each year to barely cover losses in a low intensity conflict. If this option is taken, salvage should be an important part of the game.
6.   Salvage should be calculated directly into post battle recovery. Maybe some of the destroyed units can be put back in service if the unit has some rest and supplies at hand.
7.   Advanced technology should be involved in the game. The higher the tech level the higher the ratings of the combat vehicles.
8.   Unit quality, reliability, and leadership should have an impact on battles. I think these three traits should play a role in the battle, perhaps reliability rating impact how much damage a unit could take before it is forces to retreat to a friendly planet. Quality and Leadership should have a direct impact on the random element that calculates how much damage was dealt or suffered by the unit.



Thoughts?
Logged

Ice Hellion

  • Protector of the Taurian Concordat
  • KU Player
  • General
  • *
  • Offline Offline
  • Posts: 4,482
  • Beware of the all-seeing eye: Ice Hellion
Re: Primer for Interstellar Operations
« Reply #1 on: October 27, 2011, 02:30:43 PM »

The problem with point 2 is that you will quickly focus on Assault designs only as they would be the biggest, meanest units around.
Logged


"In turn they tested each Clan namesake
in trial against the Ice Hellion's mettle.
Each chased the Ice Hellion, hunting it down.
All failed to match the predator's speed and grace.
Khan Cage smiled and said, "And that is how we shall be."

The Remembrance (Clan Ice Hellion) Passage 5, Verse 3, Lines 1 - 5

Takiro

  • General
  • *
  • Offline Offline
  • Posts: 10,175
  • For the Last Cameron!
Re: Primer for Interstellar Operations
« Reply #2 on: October 27, 2011, 04:09:52 PM »

When we did a House Campaign as we called them here there was a lot of give and take between GM and House Rulers. Of course we began before any rules were ever published for BattleTech on this scale but still I imagine any set is going to have problems with the sheer size of said campaign. There were a lot of outside sources I consulted like a certain D&D set and Traveler to fill in some gaps but still it depended largely on the interaction between the players and events. We had fun with several include a Campaign entitled Splinters.
Logged

Blacknova

  • Puppet Master
  • Global Moderator
  • General
  • *
  • Offline Offline
  • Posts: 2,351
  • Rugby Players - Inspiration for the BattleMech
    • The Kapteyn Universe
Re: Primer for Interstellar Operations
« Reply #3 on: October 27, 2011, 05:06:17 PM »

We have already done such a thing for the KU and it has a 90 page rule book and a pile of spreadsheets, hence why we are looking at getting the bugger automated.  You have two options for such a trip to insanity, Keep it very very simple or it will become a beast that takes over your life.
Logged
Dedicated to committing viciously gratuitous bastardy of the first order.

The Kapteyn Universe - http://www.ourbattletech.com/kapteyn

Follow the KU on twitter: Matt Alexander
@BlackNova01

You know there is something wrong with the FWL, when Word's spell check changes Impavido to Impetigo and Zechetinu to Secretion.

bjorn

  • Menig
  • *
  • Offline Offline
  • Posts: 11
Re: Primer for Interstellar Operations
« Reply #4 on: October 27, 2011, 08:35:17 PM »

The problem with point 2 is that you will quickly focus on Assault designs only as they would be the biggest, meanest units around.

Perhaps, but not if those units are only produced in small numbers. In a 3025, most houses (Steiner excepted) produce less than 25 Assault mechs each year. Conversely, they produce around an estimated 200 light mechs a year. It would take quite a long time to see a radical change in those numbers.


I was also thinking that heavy and assault mechs would have lots of firepower, but their defensive values would be less, as they do not have the tactical speed. Light mechs would have high defensive values, but at the expense of offenisve value. I am still playing around with some ideas on how to balance something like that out, but that is my thinking.
Logged

Ice Hellion

  • Protector of the Taurian Concordat
  • KU Player
  • General
  • *
  • Offline Offline
  • Posts: 4,482
  • Beware of the all-seeing eye: Ice Hellion
Re: Primer for Interstellar Operations
« Reply #5 on: October 28, 2011, 02:12:29 PM »

Balance is the key here.

As for lack of mobility vs increased armour...
Speed and armour are needed.
A Locust might be harder to hit but an AC/20 will go through it.
An Atlas might be easier to hit (although it would probably intimate you too) but an AC/20 won't go through.
Logged


"In turn they tested each Clan namesake
in trial against the Ice Hellion's mettle.
Each chased the Ice Hellion, hunting it down.
All failed to match the predator's speed and grace.
Khan Cage smiled and said, "And that is how we shall be."

The Remembrance (Clan Ice Hellion) Passage 5, Verse 3, Lines 1 - 5
Pages: [1]   Go Up