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 a replyNext message

City:Memphis, TN US
Personal Data:Male, born: April 18 1948
Membership21years 21days ago.
Last Login60days 2h ago.
Last Move20days 11h ago.
scotireb is currently Offline!Send a mail to scotireb


Message header
Area/Game:Blue Max
Topic:Program code error
Subject:Re: [maybe] Can anybody explain this?
Posted by: scotireb - 14years 254days ago.
Message text
Bombadil wrote:
Bombadil wrote:
Natador_NMcHarg wrote:
gugliandalf wrote:
http://www.youplay.it/play/bm_GameMove.asp?GameID=590428

I read: "Your plane's special damages: 1 gun destroyed", but my plane has "0f" guns.

Now, I think that is possible that I had "1 gun destroyed" blue chit twice (rotten luck), but in this case it should be listed under special damage, shouldn't it?

Or it is a bug and I should have "1f" instead?


This has happened to me before. I got 2 gun destroyed chits in the same turn and it only shows 1 gun destroyed under special damages. I think that this is a bug.


There do seem to be several situations where the AI makes some curious decisions on damage like the one noted where getting 2 'loss of a gun' chits has the result of loosing only one MG. Another is 'Rudder Jambs' where you get a Left AND a Right Turn, the AI chooses one of these and I'm not sure how. I think the only way you loose both MGs is to draw the chit on seperate moves. I could live with either way (both guns getting knocked out on the same turn would ramp up the "Luck Factor" when playing Advanced and some would probably object).


Another situation comes to mind...Occasionally I would swear, I'll be tailing someone and the expected maneuver dosen't match what the tailed plane actually does. Has anyone else experienced this? I usually write it off to me having a "Senior Moment", but maybe it's a bug.

Bombadil


You are right Bomb. It's happened to me twice. And fairly recently, maybe say within the last three months.

Back to the messages list
Messages thread
Posting elapsed timePosted bySubject

14years 298days gugliandalf [BM][BUG] [maybe] Can anybody explain this?
14years 298days Falconfab Re: [BM][BUG] [maybe] Can anybody explain this?
14years 298days Bombadil Re: [BM][BUG] [maybe] Can anybody explain this?
14years 260days edwardlaneuk Re: [BM][BUG] [maybe] Can anybody explain this?
14years 260days Natador_NMcHarg Re: [BM][BUG] [maybe] Can anybody explain this?
 14years 260days FENRIS Re: [BM][BUG] [maybe] Can anybody explain this?
 14years 260days Bombadil Re: [BM][BUG] [maybe] Can anybody explain this?
  14years 259days FENRIS Re: [BM][BUG] [maybe] Can anybody explain this?
  14years 259days GraysGhost Re: [BM][BUG] [maybe] Can anybody explain this?
  14years 254days Bombadil Re: [BM][BUG] [maybe] Can anybody explain this?
   14years 254days scotireb Re: [BM][BUG] [maybe] Can anybody explain this?
    14years 254days FENRIS Re: [BM][BUG] [maybe] Can anybody explain this?
Next thread
Posting elapsed timePosted bySubject

14years 254days edwardlaneuk [BM][RULES] Changing your move while waiting
14years 254days dcr66 Re: [BM][RULES] Changing your move while waiting
 14years 254days TXWard Re: [BM][RULES] Changing your move while waiting
  14years 254days edwardlaneuk Re: [BM][RULES] Changing your move while waiting
  14years 254days Bombadil Re: [BM][RULES] Changing your move while waiting
  14years 254days wetty11 Re: [BM][RULES] Changing your move while waiting
Previous thread
Posting elapsed timePosted bySubject

14years 262days derekticus [WS&IM][BUG] Thanks to Nick and Blue Dragon!!
14years 261days Longneck Re: [WS&IM][BUG] Thanks to Nick and Blue Dragon!!
14years 261days wetty11 Re: [WS&IM][BUG] Thanks to Nick and Blue Dragon!!
 14years 259days BlueDragon Re: [WS&IM][BUG] Thanks to Nick and Blue Dragon!!
14years 259days BlueDragon Re: [WS&IM][BUG] Thanks to Nick and Blue Dragon!!
 14years 255days derekticus Re: [WS&IM][BUG] Thanks to Nick and Blue Dragon!!
Page generated in: 26.61133 milliseconds.