Looking into things some more WRT my scenario posed in question #4, I came up with more related questions that I feel aren't clearly answered in TW.
Consider the following scenario:
1 - Attacker A (70 ton Grasshopper) has won initiative and is on one side of a row of level 2 buildings (CF of 54) and Target B is 2 hexes away on the other side of the buildings.
2 - During the movement phase, B chooses to not move.
3 - A decides he wants to DFA B. Here's where things become unclear, because TW doesn't appear to indicate exactly when during A's move the DFA declaration is made.
Does A's player declare the DFA and then pick up the mini and move it to the adjacent hex to B (the building hex), OR does he move the mini first and then declare the DFA?
Order of operations seems to matter here.
If all attack declarations require LOS, it would seem to follow that A has to move the mini first and then declare the DFA (which also seems to clutter up how things work with double-blind play as outlined in TO, but that's another matter), otherwise, A couldn't declare the DFA (or a charge for that matter), which would also be true if LOS was being blocked by a hill/trees/water/smoke and not just by a building.
If, on the other hand, the mini is being moved first, then LOS would be obtained as soon as A moved the mini to the top of the building hex adjacent to B... Which seems reasonable but then raises a slew of other issues that raise questions not clarified in TW. Such as:
If A has to jump to the top of the building before he can then declare a DFA on B, what if the building can't support his weight? I don't think this is what the spirit of DFA intends, but things aren't entirely clear. Let's skip this for a moment and move on.
Once A has made his declaration and all movement for the turn ends, where is A actually located during the Weapon Attack Phase? Is A standing on top of the level 2 building? The building would collapse. What if the building had a CF of 72? The building wouldn't collapse but could it be shot out from under A during the weapons phase?
I'm certain all BT players (myself included) assume that A is in mid air and not standing on the building, but what if we changed the scenario so that the building was 4 levels high (and A still only has 4 jump MP)?
TW's rules for DFAs indicate that A actually jumps into B's hex but is placed in the adjacent hex. What if B had a friendly unit B2 who was already on the building? Clearly two mechs can't occupy the same hex, so where is A and can B2 shoot at him?
Page 149 of TW indicates that A is considered to be adjacent to B and 1 level higher than B or 1 level higher than the hex A occupies (the building), whichever is higher. So if the building is a level 4 building, A is considered to be 1 level above the building (putting him in the air 5 levels up), despite the fact that he only has 5 jumping MP. If B2 is on the building does that mean that A is going to collide with B2, or is A now 1 level higher than B2 (which puts A at level 7 - quite the jump for the Grasshopper)?
I'm certain that I'm not alone in accepting the intent of the rules and that A temporarily is located 5 (or 7 if B2 is on the building) levels up, despite not actually being able to jump that high for the purpose of making DFA rules work, though I'm just pointing out that TW isn't terribly clear on some of the details.
If you really want a head-scratcher, consider the same scenarios in double-blind play.
If LOS is required to make a DFA and A attempts to jump into an "empty" hex behind a building but there happens to be an enemy mech B there, does A land on the building instead (and possibly collapse it) or does A automatically DFA B? What if B is a tank? A can share the hex with B so does A just land in B's hex or does A land on the building or does A DFA B? Again, what if B2 is on the building?
I suppose the simplest solution to all thes DFA/charging issues is to say that LOS isn't a requirement for physical attacks and write an errata to that effect, though I wonder what other issues might surface from an official errata like that.