MegaMek / megamek

MegaMek is a networked Java clone of BattleTech, a turn-based sci-fi boardgame for 2+ players. Fight using giant robots, tanks, and/or infantry on a hex-based map.
http://www.megamek.org
GNU General Public License v2.0
297 stars 287 forks source link

Indirect fire source not displayed during double blind play #276

Closed VampireSeraphin closed 8 years ago

VampireSeraphin commented 8 years ago

Several releases ago a change was made, and now, during the firing phase report, there is no line break or source information for indirect lrm fire. Damage will be displayed correctly, but it will be lumped with the prior units fire, which can be extremely confusing.

Before (not sure how many releases back) all indirect fire created a line break in the firing phase report with ????? attacked xyz unit. This was much better because it let you know you were under attack, and clearly delineated that the attack came from a separate source.

arlith commented 8 years ago

Do you have a specific change in mind? I think you're just using different game rules. With Double Blind, information a player doesn't know about is obscured with "?????" in reports. If you select the "No Double Blind Messages" option, then all of those reports with "?????" in them are hidden instead. This generally works, but can occasionally lead to line break issues.

VampireSeraphin commented 8 years ago

Hmm, yes, we are using "No double blind messages."

Can you tell me what each of the things that option suppresses are? Depending on what else is in there, is might be worth making indirect fire an exemption to this rule.

BLOODWOLF333 commented 8 years ago

Could this be related to #225 where there seems to be funky things going on with DB reports?

Weapons fire for Griffin GRF-1N (McCarron's Armoured Cavalry) LRM 10 at Hex: 3452 (Deliver minefield); needs 8, rolls 4 : should have a line break here Weapons fire for Awesome AWS-8Q (McCarron's Armoured Cavalry) PPC at Ostroc OSR-2C (Michi) (Reaper Company); needs 12, rolls 7 : misses

arlith commented 8 years ago

Yes, it's the same underlying problem.