Mark of Solitude does not work like Protocol. Protocol prevents you from directly attacking the enemy general and nullifies any damage you would deal to the enemy general indirectly (like splash damage from Thunderhorn/Flamewreath). Mark of solitude only prevents you from attacking the general but does not nullify any damage you would deal to them (you can still damage them with things like Frenzy or Thunderhorn).
S rank budget Faie (Jan 2019)
What you point out about the difference between AssProt and MoS is right, but just for the record Gambler should never be able to deal direct attack damage to the general if effected by MoS.
Since it’s ability states that he “has a 50% chance to attack again, attacking a random enemy”, the first and extra times he attacks targets should then always ignore the Enemy General, if he has MoS.
The problem here is that only Bloodsworn Gambler’s first attack actually counts as an attack, any attacks after that one aren’t technically attacks and don’t follow the rules of attacks (i.e. after the first attack nobody will counter Gambler even if they are in range, attacks ignoring provoke and pando’s ability, Gambler continuing to shoot down enemies even when he is already dead ect.).
Wow! How one could archieve that?
I don’t think that’s correct as the text of Gambler says: “Every time this minion ATTACKS he has a 50% to ATTACK again, ATTACKING a random enemy”.
All the damage it deals with its ability after every first attack are also attacks.
Call it spaghetti code, call it a bug, but it’s definitely not working according to the rules.
Applying MoS should still prevent it from attacking the General, if we’d go by the rules.
@terrarius: The action of attacking should work according the rules (of attack), but surely BG plays by his own rules 
BG playing by the rules ?
How about: “Whenever this minion attacks, it has a 50% chance to FIGHT a random enemy.”
Perfect fix. 
I’ve always considered “fight” to be a symmetric process, so probably not the best word to be used in this case.
I got the joke, btw 
Drop an Ironcliffe next to Gambler, attack Ironcliffe with Gambler. If RNG is on your side the 0 health gambler will proceed to shoot every other enemy on the field (this is also a good example of Gambler’s consecutive attacks ignoring provoke).
any attacks after that one aren’t technically attacks and don’t follow the rules of attacks
I don’t think that’s correct as the text of Gambler says: “Every time this minion ATTACKS he has a 50% to ATTACK again, ATTACKING a random enemy”.
All the damage it deals with its ability after every first attack are also attacks.
Call it spaghetti code, call it a bug, but it’s definitely not working according to the rules.
Applying MoS should still prevent it from attacking the General, if we’d go by the rules.
This isn’t spaghetti code nor is it a bug, this is the result of CPG giving cards poor wording and using the same word to define different effects. Gambler isn’t the only example of this, Sirocco and Ebon Ox also share this quality.
Ideally Gambler’s text would be: “Whenever this deals damage during your turn, it has a 50% chance to deal damage equal to its attack to a random enemy”. This would help prevent confusion from most of the interactions with Gambler but would be much wordier than the current text.
Ideally Gambler’s text would be: “Whenever this deals damage during your turn, it has a 50% chance to deal damage equal to its attack to a random enemy”. This would help prevent confusion from most of the interactions with Gambler but would be much wordier than the current text.
This solution is almost perfect. The only issue I find is when you summon Gambler when Ox is online. The 3 damage dealt to a random enemy due to the Destiny still counts as Gambler dealing the damage.
Looks like I indeed missed the interaction with Ox
That means the proper description of how Gambler works would be: “Whenever this minion attacks, it has a 50% chance to deal damage equal to its attack to a random enemy, every time it does so it has a 50% chance to do it again” that just sounds terrible.
Anybody have a better idea how to properly word Gambler’s effect?
We don’t know if it’s indeed a wrong wording or if the wording is correct but those specific interactions (keeping on shooting after technical death, attacking generals while Mark of Solitude is on) are actual bugs.
Surely there’s something wrong with the card, and people complained about it since forever (and who knows when things will get fixed…).
Fight is a broken mechanic. 
https://duelyst.gamepedia.com/Bloodsworn_Gambler
I don’t know, read the wiki, find out and add an interaction 
Is it safe to say Gambler’s non-first attack won’t trigger effects like Day Watcher then?
Gambler hidden passive:
When a post on Gambler is posted, there is 50% chance another post on Gambler is posted
.
Yep, only the first attack will trigger Daywatcher/E’Xun/Frostvia/vaporize mirages.
The party forgives you, comrade.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
