[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (TFT) Megahex definition
- To: "tft@brainiac.com" <tft@brainiac.com>
- Subject: Re: (TFT) Megahex definition
- From: Jeffrey Vandine <jlv61560@yahoo.com>
- Date: Mon, 7 Dec 2015 00:38:32 +0000 (UTC)
- Authentication-results: zappa.brainiac.com; dkim=fail reason="signature verification failed" (2048-bit key) header.d=yahoo.com header.i=@yahoo.com header.b=rzq7ei5+
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1449448882; bh=nlP6wYsS0TNRN5ILVDb/ET/P3dOXdZOHGt+Z+ESqvSk=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=rzq7ei5+q8mmrrkfyZemjFHC/24yR3NvACUsXsiMuQAAR0m2JT0Ytubi1n0wAoYs5kJwW8EZmP0J0WL4oimH1XPKfNAbquC5bQabcC6o6DssCMmqoABYzJUPtj/6JZFKSA9mOydBeQ8/5iM3ldRvaniCWIGT1Ie0nxHc+ebHL59cJBrF/aHPjlx2AUhQLiKKPGIkovCyUq8Eldm9OmR341dbMjV4A6uNs/QM9IQUcgm/Nxwarj1dL3V/11+yGakTt4poF0loP1OOsIZxAbUp2ajghFmoE8I9JLyl2TV6M0i9LWoL2BpnfpOi1uEBc+ZnPOB/F3v7yJn2CxIFlaPbyg==
- In-reply-to: <08F04EDE-FD19-40EE-81E9-BE7C5F8D0CA7@lightspeed.ca>
- References: <08F04EDE-FD19-40EE-81E9-BE7C5F8D0CA7@lightspeed.ca>
- Reply-to: tft@brainiac.com
- Sender: tft-admin@brainiac.com
Different strokes for different folks -- I prefer less rigid rules.
v/rJeff
From: Rick Smith <rick_ww@lightspeed.ca>
To: tft@brainiac.com
Sent: Sunday, December 6, 2015 2:54 PM
Subject: Re: (TFT) Megahex definition
Hi all,
I use the strict "printed on the board" meaning of MH. However
,
I have rewritten the spells which affect one hex and adjacent
hexes to say, "Target hex, and all adjacent hexes" so there is no
ambiguity in my rules.
I would suggest, that you uses the MH printed on map, definition,
in all cases except in one MH spell description.
Warm regards, Rick.
On 2015-12-06, at 2:26 PM, Jeffrey Vandine wrote:
> It depends on how specific you need/want to be in your games. To ca
lc
> ulate range for Missile Weapons and Spells, I always assumed the shooter
wa
> s in the center of a megahex based on the hex he occupies, and then calcu
la
> ted the number of MH range on that basis if it became necessary to achiev
e
> that level of specificity. Otherwise I let the MH boundaries dictat
e
> the issue. Put another way, if that one hex of distance made a significan
t
> difference, we accounted for it, otherwise we didn't worry about it.��
> As a general rule, let common-sense prevail. The heavier borders fo
r
> the MH boundaries are there for your convenience, not to constrain you.
>
> From: Eric Tetz <erictetz@gmail.com>
> To: tft@brainiac.com
> Sent: Sunday, December 6, 2015 2:16 PM
> Subject: (TFT) Megahex definition
>
> We can't find a formal definition in the manuals, other than referring to
> the included hexpaper. Is a megahex:
>
> 1. The hex you're on/targeting and it's surrounding 6 hexes.
> 2. The drawn megahex on the map that you happen to be standing
> in/targeting.
>
> In other words, is the following character in the yellow-outlined megahex
> (i.e. the one defined by the megahexes pre-shaded on the map), or in the
> blue-outlined megahex (i.e. the megahex centered on his current hex):
>
>
>
> Eric
>
> Post to the entire list by writing to tft@brainiac.com.
> Unsubscribe by mailing to majordomo@brainiac.com with the message body
> "unsubscribe tft"
>
>
>
>
> Post to the entire list by writing to tft@brainiac.com.
> Unsubscribe by mailing to majordomo@brainiac.com with the message body
> "unsubscribe tft"
>
Post to the entire list by writing to tft@brainiac.com.
Unsubscribe by mailing to majordomo@brainiac.com with the message body
"unsubscribe tft"
Post to the entire list by writing to tft@brainiac.com.
Unsubscribe by mailing to majordomo@brainiac.com with the message body
"unsubscribe tft"