Chapter 1 of the cultist scenario should get changed

gerald witcher3 gwent

I've always felt that no matter how strong a scenario is. it's kind of fair because you can either heatwave it or bleed it out in round 2. but cultist scenario feels completely unfair because both of these don't work.

With the reworked affan, they can proc the most important chapter instantly, so heatwave don't work. And because the passive from chapter 1 can be carried over, bleeding it out don't matter anyway. The carryover aspect is extra tilting because in a way, you are dealing with the scenario twice in a game.

Just imagine chapter 1 of harmony scenario working the same way. not only would you need to deal with the usual harmony engine, but now every random card like operator is an exponential engine as well. that does not seem right at all.

I'm aware that there is hard matchup for cultist and its does not auto win everything, for example sk raid where everything gets killed. But not everyone gonna be playing full on control deck every time. Plus, even with raid, I've had matchup where even if i managed to kill all of the initiates, the carryover from scenario is still enough for them to win the game. 25 points each nauzicaa brigade is a joke. this carryover aspect makes matchup between low control deck like deathwish vs cultist unfair.

I'm not sure what was the reasoning for this carryover design decision. Perhaps the dev thinks that its cool lore wise or that cultist need it to be competitive. But with the reworked affan and the buffed initiates, they are competitive already.

I feel like the passive from chapter 1 should only work while the scenario is on the board, in line with the other scenario. Or, at the very least, it needs to the lose the exponential aspect of the infusion and work like harmony instead.

Anyone care to provide their opinion? perhaps there's something I've missed, and that the carryover design is necessary?

Source: https://www.reddit.com/r/gwent/comments/z3e2qa/chapter_1_of_the_cultist_scenario_should_get/

leave a comment

Your email address will not be published. Required fields are marked *