8000 The order of "Destroyed:" abilities · Issue #4377 · keyteki/keyteki · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

The order of "Destroyed:" abilities #4377

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
D07U opened this issue Nov 2, 2024 · 4 comments
Open

The order of "Destroyed:" abilities #4377

D07U opened this issue Nov 2, 2024 · 4 comments

Comments

@D07U
Copy link
D07U commented Nov 2, 2024

Hi develoment team!
According to the latest rulebook (https://keyforging.com/wp-content/uploads/2024/09/KeyForge-Rulebook-v17-4.pdf), when there are many "Destroyed:" abilities in the same time-window, those with "instead" keyword should be resolved last (because they're considered "replacement effects").

sdxrtvxder

A judge also confirmed that in one of my post here (this is for reference only, I think you should contact GG if in doubt...).

(https://www.facebook.com/photo?fbid=437927192111120)

But in a game in which my opponent play "The Body Snatcher", follow by a fight to kill off my "Dust Imp", its "Destroyed:" ability doesn't get to triggered first (I believe its should be triggered first, before the one "The Body Snatcher" gave it - because its doesn't have "instead" word.)

cdfybrty

If you could review this case and make an improvement, it's great!

TCO is becoming quicker these days, thanks for all of your efforts <3

@strib
Copy link
Contributor
strib commented Nov 2, 2024

Thanks for the report. Note that TCO already allows you to choose the order of destroyed effects if you have the "Prompt to order simultaneous abilities" option enabled in your TCO profile. Do you (or your opponent, in this case) have that enabled? If not, then the order is random.

As for replacement effects resolving last, I can kind of see that in the rules section you posted but it seems a bit ambiguous because in this case it's inside a "Destroyed:" effect which should be ordered by the active player alongside the other destroyed effects. I don't have a Facebook account so I can't read the link you posted.

@D07U
Copy link
Author
D07U commented Nov 2, 2024

I have it "on" all the way but it never ask me on cases like these...? Does it need to turn "off" or the issue lies in my browser? (I'm using a Chome-based browser that is customed by the local developers, here: https://github.com/coccoc).
dfrty

About that Facebook post, sorry for my assumption before (it's just Facebook is so popular at my place... :3) @@ It basically looks like this: (according to the judge, it needs some deduction to result in ["Destroyed:" with "instead" should wait to be resolved last])
dxdery
sdfgdr
fgft

@strib
Copy link
Contributor
strib commented Nov 2, 2024

Ok I discussed with a rules lawyer and I agree with you, though given how hard it would be to implement, I'm not sure I'd ever be able to personally find the time to fix something so niche. But patches welcome for anyone who wants to prioritize it, as always!

It looks like you have it configured correctly. But in the case you mentioned, your opponent is the active player so they would have had to have it turned on.

@D07U
Copy link
Author
D07U commented Nov 3, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0