Well, that seems a bit excessive to me. Plus we can have the same issue down the road, if we're reading the map differently. Honestly, this game has been sucking me in so much that I haven't been getting my house chores done or the prep work for my weekly D&D game. I think I'll just go ahead and...

I can understand how that would be a pain, but we can't have a coherent game if the GM and players are reading 2 different mapsheets. And starting the turn over would necessitate redoing that, anyway, as damage that has been inflicted will not be the same. Not trying to be a pain in your keester, he...

It's just the resolution of the image you're using makes it blurry. But it really is a level 2 hex. Here's a higher resolution of the map you're using (The mapsheet from the Classic BattleTech Introductory boxed set). You can see that 1204 is clearly lvl 2:

1305 is level 1. But 1204 (which blocks line of sight for E4 to P3) is level 2.

wolfpack, I don't think E4 can see P3, because E4 is standing next to a level 2 hill which should block his line of sight. Also, P3 only jumped 4 hexes, so a +2 movement mod. Please correct me if I'm wrong. That's correct. I didn't catch it before but, according to the rules (Mechs are 2 lvls tall,...

OOC: Man, that rat bastard in the Hermes is getting to be a real pain. :evil: Gene raises Tricksies large laser and fires at the Clint, but his erratic movement makes the shot go wide. (E3). Large Laser: Hit=[2d6] = 6 | Location=[2d6] = 10 | CritChance=[2d6] = 6 Orloff, being far outside his weapon...

Oh, right. I see what he meant, now. Thing to remember, Greywolf, is each of those hexes is meant to represent an area 30 meters wide. So your 'Mech actually takes up comparatively little space in that area.

Hm? What's Ivan to do with it?

GreyWolfVT wrote:

Recklessfireball wrote:Ivan runs to 1012, facing the light woods at 1112.

this is really close to what i was gonna do anyways.

Cool.

Ivan runs to 1012, facing the light woods at 1112.

Alrighty. I'm gonna line you up with your other dude, so you can be set up for the rush on hamburger hill, with the rest of us, next turn.

Dagger opens the inter-unit comm channel. "Orloff, run to coordinates zero, one, zero, six and prepare to make an assault on that sniper's nest. I'll approach from the south, on the bounce, and we can pinch them between us. All remaining 'Mechs, pair up and prepare to make a run on that hill.&q...

Machine gun ammo is a bitch in 3025. I swap those suckers out for a different weapon, as soon as possible, when I wind up in a 'Mech that mounts them.

Orloff tries to kneecap the Phoenix Hawk with his Commando...
Orloff Kick attack: Hit=[2d6] = 9 | Location=[1d6] = 1 | CritChance=[2d6] = 12
EDIT: Oop. Heh. Nevermind, I guess.

Initiative [2d6] = 4

Well, Orloff certainly gave him a face full of laser-missile death.

Dagger twists his 'Mechs torso to the left and fires its Harmon large laser at the enemy Phoenix Hawk (E1)... Large Laser: Hit=[2d6] = 7 | Location=[2d6] = 11 | CritChance=[2d6] = 5 Lt. Orloff pours fire onto the same target with every weapon in his Commando's arsenal... Orloff Medium laser hit [2d6...

Move to 0411 facing 0512. Then twist your torso to fire at P1. You'll be at close range, have some cover from the woods, and get a +3 move modifier.

Ooops I completely messed up. I said E1 stands still when I meant E2, but I will let it stand since I imagine that is why F1 didn't move.

Heh. Yeah, that one took me by surprise. I thought you had some nefarious scheme up your sleeve.

Ah, and Orloff will turn to face the enemy Phoenix Hawk (E1).