Items and cards that cause discard or ace other cards sometimes trigger on random cards about doomtown-reloaded-octgn

[db0]

Is this something new, or have you seen it in previous updates. I've never seen anything like before. Of course for shotgun and coachwhip, that;s normal since they take the dude's items with them. But Hex slinging should discard the spell, even if you target a dude by mistake,

Can you find a replicatable scenario for me to test?

[swider33]

The bug is quite old, I am pretty sure that I saw it pre-NTNR.
I think I described the bug incorrectly so I will do it again.
Basically, after using one of those cards, more than one dude becomes
discarded/aced, usually the dude that was an owner of the goods.Also it
discards/aces extra dudes, even if only one card on a map is targeted.
Strange thing is that when you manually bring them back to the board it is
sometimes impossible for a moment to reattach the goods to a dude. It works
only on n-th try. And again sometimes when you ace a dude in a shootout,
he spawns at home.

Sometimes the bug "snowballs" and dudes/deeds start disappearing
practically after every play, although this is really rare.

When it comes to hex slingin', I didn't use it in a while, also people
don't play 4th ring recently, but what usually happened was that the wrong
spell got discarded on playing it.
If you want to replicate the bug I would suggest to create two big posses
and use cards effects on dudes in those posses. I will try to recreate the
bug myself, if I succeed or see it online again, I will describe it to you
as well as it is possible.

Thank you for answering, and all the fixes you have done yesterday.
Fantastic job.

On Tue, Dec 16, 2014 at 12:53 PM, Divided by Zer0 [email protected]
wrote:

Is this something new, or have you seen it in previous updates. I've never
seen anything like before. Of course for shotgun and coachwhip, that;s
normal since they take the dude's items with them. But Hex slinging should
discard the spell, even if you target a dude by mistake,

Can you find a replicatable scenario for me to test?

—
Reply to this email directly or view it on GitHub
#8 (comment)
.

[db0]

OK, if it happens, try to copy paste the log to me in a pastebin so that I can take a look.

[db0]

Still didn't happen again?

[swider33]

I haven't noticed this email yesterday. I think the bug was created by
targeting more than one card when card's effect was discarding/aceing a
card. I haven't seen this bug snowballing since reporting it. Constraining
a type and/or a number of cards targeted by a card that discards or aces
other cards might be a good idea. While it is quite easy to manualy reverse
a created problem , sometimes a card removed from the table, for instance a
huckster, has other cards attached to it that have various state ( booted /
unbooted), and recovering the state of all of those cards is sometimes hard.
On 24 Jan 2015 11:09, "Divided by Zer0" [email protected] wrote:

Closed #8 #8.

—
Reply to this email directly or view it on GitHub
#8 (comment).

[db0]

Cards are already constrained, but if you target two dudes with coachwhip
and one is wrong, then there's really nothing I can do

On Sat, Jan 24, 2015 at 1:19 PM, swider33 [email protected] wrote:

I haven't noticed this email yesterday. I think the bug was created by
targeting more than one card when card's effect was discarding/aceing a
card. I haven't seen this bug snowballing since reporting it. Constraining
a type and/or a number of cards targeted by a card that discards or aces
other cards might be a good idea. While it is quite easy to manualy
reverse
a created problem , sometimes a card removed from the table, for instance
a
huckster, has other cards attached to it that have various state ( booted
/
unbooted), and recovering the state of all of those cards is sometimes
hard.
On 24 Jan 2015 11:09, "Divided by Zer0" [email protected] wrote:

Closed #8 #8.

—
Reply to this email directly or view it on GitHub
#8 (comment).

—
Reply to this email directly or view it on GitHub
#8 (comment)
.

Personal haven @ http://dbzer0.com