Once again, this forum is awesome. I grabbed the new version of Adobe Reader and problem solved. It's probably something I would have had to do sooner or later anyways. My mistake was clicking (and trusting) on Adobe Help / Check for Updates, which said No Updates Available. It didn't say anything about a newer version being available. Duh. Thanks for your help, guys.

Very nice job Zalt and any2cards on the Index. Really clarifying and easily understandable <thumbs up>

Just readed the whole glossary and the campaign flow, these will be a mandatory read for the heroes, and no more complaining allowed!

Very nice job Zalt and any2cards on the Index. Really clarifying and easily understandable <thumbs up>

Just readed the whole glossary and the campaign flow, these will be a mandatory read for the heroes, and no more complaining allowed!

I'm in the process of updating the glossary right now. Hopefully there will be a new version posted in the next few weeks.

Version 2.1 of the Glossary just posted to BGG. It's got an improved (hopefully simpler) format, an index at the end for easy location of terms, references to expansion-specific content, and a clarified space counting example. Additionally, by changing the example chart's format, the file is 1 MB instead of 9.5 MB. You can find it by using the link in the first post. Enjoy!

Good day.

I found something intresting in your glossary about situation when one character can be affected twice by one attack (with redirrecting multitarget attack). Could you please give some more info about it? Like source of this info. I mean it sounds logical, but anyway...

Thank you so much for your amazing work!

Good day.

I found something intresting in your glossary about situation when one character can be affected twice by one attack (with redirrecting multitarget attack). Could you please give some more info about it? Like source of this info. I mean it sounds logical, but anyway...

Thank you so much for your amazing work!

The knight can redirect the other "flail" target to himself and be affected twice (defend twice against the same attack roll and be dealt damage for each defense)

Because "Defend" is a "use" skill and not an "exhaust" skill, the knight could use it multiple times if there are multiple opportunities. Therefore, if an elemental were to perform "Fire" and target the knight and 2 other heroes (both adjacent to the knight) it follows that he could use "Defend" twice (once triggered when the Elemental targets one hero, and once when then elemental targets the other) and become the target of all 3 attacks. He would need to pay a fatigue each time.

The knight can redirect the other "flail" target to himself and be affected twice (defend twice against the same attack roll and be dealt damage for each defense)

Because "Defend" is a "use" skill and not an "exhaust" skill, the knight could use it multiple times if there are multiple opportunities. Therefore, if an elemental were to perform "Fire" and target the knight and 2 other heroes (both adjacent to the knight) it follows that he could use "Defend" twice (once triggered when the Elemental targets one hero, and once when then elemental targets the other) and become the target of all 3 attacks. He would need to pay a fatigue each time.

Hm, that seems right. Would it be the same with something like Fire Breath? In fact question is: Does it apply to situation where characters "affected" by attack or it only works when they are targeted?

Well I guess in such scenario Knight could only redirrect ones (from initial target of an attack)

Two things about Defend a d Fire breath:

1) You picked up correctly that defend says,"targeted." So, if a hero adjacent to the knight is merely affected (as with fire breath,), it cannot trigger.

2) Targeting (almost) always happens during step 1of combat. Far and away, this is when Defend is triggered. It can (almost) never be triggered in a later step, like when fire breath is applied in step 4.

Zalt, in your recent charter of space counting, you ignore the black edges of the map while maneuvering to your destination? I mean, you take straight diagonals instead of counting orthogonally around corners with black edge. I thought this kind of move were only allowed when maneuvering around blocked spaces.

Zalt, in your recent charter of space counting, you ignore the black edges of the map while maneuvering to your destination? I mean, you take straight diagonals instead of counting orthogonally around corners with black edge. I thought this kind of move were only allowed when maneuvering around blocked spaces.

I created a picture with grid labels to make communication easier.

Space D4 is adjacent to both C5 and D5. It is not adjacent to C4. Likewise, space E6 is adjacent to both E7 and F7, but not F6. This means you can count from D4 to C5 as 1 space. If there isn't an elevation line, portcullis, or some other movement blocking thing, it also means that you can move directly from D4 to C5 (or from E6 to F7.)

It's very similar to the movement example show on page 9 of the base rulebook. Point 3 states that '... the black edge of a map tile does not block diagonal movement around corners. ' The only difference between that diagram and mine is that in mine, the extra space (C4/F6) is actually a space, and not a blank area.

It has come to my attention that some pdf applications don't properly display the bold text. If you are having this issue, open (or print) the pdf using chrome's plugin. Everything seems to display fine there.

I'll put this in the first post as well.

This is very helpful, thank you Zaltyre.

I found a potential error, on pg. 3, "Adjacent", it says:

"Two spaces are adjacent if they share exactly 1 corner (if diagonal) or 2 corners (if side by side)."

This implies that if you share more than two corners, thus not exactly 1 corner or 2 corners, they don't count as adjacent. But there are figures in the game that occupy more than this, such as Shadow Dragons.

If a Shadow Dragon and an Ettin would stand next to eachother, they'd share 3 corners, but they'd still be adjacent.

My suggestion would be to simply change it to "Two spaces are adjacent if they share at least one 1 corner, diagonally or side-by-side."

Or if you're just considering the corners of the models themselves and not the corners of squares, the sentence still needs to be reworded; for example, an Ettin and a Hero standing next to eachtoher would then only share 1 corner, but they'd still be side-by-side adjacent, not diagonally adjacent. Not that that matters - but if it doesn't matter, the distinction should be dropped.

I found a potential error, on pg. 3, "Adjacent", it says:

"Two spaces are adjacent if they share exactly 1 corner (if diagonal) or 2 corners (if side by side)."

This implies that if you share more than two corners, thus not exactly 1 corner or 2 corners, they don't count as adjacent. But there are figures in the game that occupy more than this, such as Shadow Dragons.

If a Shadow Dragon and an Ettin would stand next to eachother, they'd share 3 corners, but they'd still be adjacent.

My suggestion would be to simply change it to "Two spaces are adjacent if they share at least one 1 corner, diagonally or side-by-side."

Or if you're just considering the corners of the models themselves and not the corners of squares, the sentence still needs to be reworded; for example, an Ettin and a Hero standing next to eachtoher would then only share 1 corner, but they'd still be side-by-side adjacent, not diagonally adjacent. Not that that matters - but if it doesn't matter, the distinction should be dropped.

When counting spaces, the model size doesn't matter. Actually, you are never attacking the Ettin model, only a square (or space) the Ettin occupies. Following this, of you blast attack an Ettin, the blast will only affect spaces adjacent to the space you attacked (and of course, a figure can't be affected twice by the same attack).

"Two spaces are adjacent if they share exactly 1 corner (if diagonal) or 2 corners (if side by side)."

Notice the bolded part. The definition is correct for spaces. Then you're talking about adjacent figures . If two different figures have each one a space that is adjacent to one of the other, both are then adjacent.

The spaces were worded that way (one corner if diagonal, 2 if side-by-side) to include the exceptional case of two spaces separated by a short segment of map edge. The diagonal spaces are adjacent, but the two immediately to the side of the map edge only share one corner (at the end of the edge) whereas in the other corner, they are fully separated by the black map border.

Thanks for posting. If you do find an error, please post it.

Zaltyre,

I have a contribution to your Glossary of Terms.

Researching for a next plot deck to use, I've found a card that instances a parameter not yet mentioned by you on the glossary.

Deceiptful Scribe: "Use this card during the spend experience points step of the campaign phase. You receive 1 XP.Then return this card to the game box ".

Maybe it's me being to much of a perfectionist, but I think we should explain better the meaning of "return to game box".

In my view, "return this card to the game box" is different than "return this card to your plot deck" (i.e.: all agent cards - when it gets killed).

Returning a card to the game box is a one way thing, it disappears from the campaign (not on the plot deck anymore, it is spent), while an agent card can be purchased again and again.

I also saw somewhere ( I cant recall right now) the term "return to the supply" , wich is more often used on game tokens, monters etc, but on my understandment means it can be used again.

In an old post (Plot decks cards description - Started by Vancheng, Jan 15 2015 06:29 AM) it was already debated, but since our goal is to keep the doubts on track, I think it would be a good thing to add the query to the glossary.

If it is already stated somewhere in the core rules, please direct me to it

Share your thoughts please.

Thanks, Dommus! I'll be sure to add these terms to the next version of the glossary.

"Return to the game box" is most often "get rid of it for good." The only exception I know of to that meaning is a clearly odd case where a hero can hang on to the Jinn's Lamp until Act 2, and then use it to draw a card from the Act 1 shop deck (which was returned to the game box after the interlude shopping step).

The only exception I know of..

SoN - Arise My Friends, OL reward

Conversion Kit = Item Fantasy Flight won't support and pretends doesn't exist.

FF reissues most heroes and all monsters in later products and does not issue errata or a summary of changes for existing 1e Descent customers who bought the conversion kit.

For customers using the conversion kit with their physical game, the Return to Legend app doesn't support it (apparently deliberately). I seriously doubt we will see an updated conversion kit with new stats to match the hero & monster collections stats? (A conversion kit for the conversion kit).

I just hope they eventually release the other 12 heroes.

danman- it's possible you posted in a different topic than you intended.

Hi Zaltyre,

Glossary:

Empty space: A space that does not block movement or line of sight for any object .

Is a space with a KO hero token an empty space or not ?

e.g. can you spawn the reanimate on a field with the hero token ?

RAW:

A space containing a knocked out hero (represented by a hero token) is considered to be empty to other figures for the purposes of movement .

In other words, any figure may move through and end its movement in thatspace. Also, knocked out heroes do not block line of sight.

Rules does not say a field with a hero token is considered as an empty space in all cases.

Core rulebook page 9, box at the top:

Empty Spaces
Some card effects and abilities refer to empty spaces. An empty
space is defined as a space that contains no figures and that
blocks neither line of sight nor movement. Unless otherwise
noted, spaces containing tokens are still considered to be empty
for the purposes of these effects.

perfect, thank you HavocDreams!