LOGIN
User Name
Password
Remember me


Register...Forgot password?
Main menu
Leagues
Gonzaga
Blue Max
Cartagena
Wooden Ships...
King Me!
VampiRing
Forum Message
Previous messagePost on the new forumNext message

City:Pailin MY
Membership23years 159days ago.
Last Login11years 337days ago.
Last Move14years 338days ago.
Crash and Burn is currently Offline!


Message header
Area/Game:Blue Max
Topic:Program code error
Subject:Re: rudder jam bug
Posted by: Crash and Burn - 20years 106days ago.
Message text
pokerguy wrote:
Crash and Burn wrote:
warrax wrote:
In this particular case, the special damage "Rudder jam ..." should have been changed automatically into "Engine damaged - no 3/4 speed moves"...



The "no 3/4 speed moves" is a different chit. All that needs to be done here is to ignore the rudder jam results and put the damage against the engine and not the tail. When you go head to head with someone and they shoot at you and you pull the rudder jam chit, all that is done is that the engine takes the required damage (2 or 3 points) and the rudder jammed left or right is ignored. I have seen house rules where instead of ignoring the rudder jam chit change it to engine damaged, but they are just house rules and not offical rules of Blue Max.

C&B



In my origional 1983 version the rules state that if fired on from the front change rudder jammed to engine damaged no 3 or 4 moves, and if fired on from directly behind change engine hits to tail hits and rudder jams must go straight for 3 turns.


I better go dig out my original set of Blue Max rules. Currently I've been using the "Miniatures" edition of the rules with the new early war aircraft charts. These rules are the same as the version before (3rd printing?). But I have either a first or second edition of Blue Max as well and I better check this to see if they have it. If so, then it was changed thereafter. But I should also double check the newest "Miniatures" edition to see if I'm not mistaken.

Back to the messages list
Messages thread
Posting elapsed timePosted bySubject

20years 107days ksnake [BM][BUG] rudder jam bug
20years 107days ksnake Re: [BM][BUG] rudder jam bug
 20years 107days Bombadil Re: [BM][BUG] rudder jam bug
 20years 107days pokerguy Re: [BM][BUG] rudder jam bug
 20years 107days Gabriel Guerin Re: [BM][BUG] rudder jam bug
 20years 107days warrax Re: [BM][BUG] rudder jam bug
20years 106days Crash and Burn Re: [BM][BUG] rudder jam bug
 20years 106days warrax Re: [BM][BUG] rudder jam bug
  20years 106days Crash and Burn Re: [BM][BUG] rudder jam bug
   20years 106days pokerguy Re: [BM][BUG] rudder jam bug
    20years 106days Crash and Burn Re: [BM][BUG] rudder jam bug
     20years 106days pokerguy Re: [BM][BUG] rudder jam bug
Next thread
Posting elapsed timePosted bySubject

20years 106days Lord Locquax [OT] Away for a Few Days
20years 106days ksnake Re: [OT] Away for a Few Days
Previous thread
Posting elapsed timePosted bySubject

20years 107days Resisti [WS&IM][SYS] WS&IM: why not the timeout option for this game,too?
20years 106days Bombadil Re: [WS&IM][SYS] WS&IM: why not the timeout option for this game,too?
20years 106days Nick Re: [WS&IM][SYS] WS&IM: why not the timeout option for this game,too?
 20years 106days Sabelkatten Re: [WS&IM][SYS] WS&IM: why not the timeout option for this game,too?
  20years 106days Nick Re: [WS&IM][SYS] WS&IM: why not the timeout option for this game,too?
   20years 106days Sabelkatten Re: [WS&IM][SYS] WS&IM: why not the timeout option for this game,too?
Page generated in: 24.60938 milliseconds.