Quantcast
Channel: Descent: Journeys in the Dark (Second Edition) | General | BoardGameGeek
Viewing all articles
Browse latest Browse all 3507

Thread: Descent: Journeys in the Dark (Second Edition):: General:: Encounter objective and Monster AI RAMV

$
0
0

by Jotun

Hi there. I’m looking forward to playing RAMV for descent solo but I probably missing a rule somewhere.

Currently I’m re-learning the rules since its been awhile since I’ve played. I also never played with a DM, only with the RtL app.

I’m stuck on the Hiers of Blood first campaign scenario ‘Acolyte of Saradyn’. In this scenario the goblin archers have both an Encounter Objective and a Monster AI. The Encounter Objective is the ‘Caravan Site’ map tile.

When I activate the master Goblin first in the first round it will follow the Encounter Objective and perform an ‘engage action’ as its first action. In the RAMV rules ‘engage’ is in principle a move action, in this case the Goblin will move towards the ‘Caravan Site’. P.S. I understood that if the Goblin is already on the ‘Caravan Site’ in a later round it will forfeit the ‘engage action’ and follow its Monster AI instructions.

I’m wondering on the next steps. After the first ‘engage’ move action I understood the Goblin will follow its Monster AI instruction card. If that instruction is ‘If no targets within 4 spaces: engage a target’ than the Goblin would move a 2nd time, right?

Can this not result in the Goblin taking a first move action to move on to the ‘Caravan Site’ and subsequently a second move action towards a target far away and as a result is no longer on the ‘Caravan Site’? And repeat this process again in the following round?

I’m not sure how realistic this situation will be and if it can occur while playing the scenario but if you are focused on healing the clergy or delving the search token I can see instances where it can occur and delay the ‘win’ for the DM.

Viewing all articles
Browse latest Browse all 3507

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>