Skip to content
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

Fix field::negate_chain #147

Merged
merged 1 commit into from
Aug 7, 2023
Merged

Fix field::negate_chain #147

merged 1 commit into from
Aug 7, 2023

Conversation

NaimSantos
Copy link
Contributor

If a Spell/Trap card that is going to have its activation negated leaves the field but it is put back in the S/T zone before this function (field::negate_chain) is executed, it should not be sent to the GY when the negation occurs because it is treated as a different copy of the card. Currently it will be sent to the GY, which is wrong

This pull requests adds an extra check for the chain relation before setting the status to the card

bug: if the Spell/Trap card that is going to have its activation negated leaves and returns to the field before the function is executed, it should not be sent to the GY when the the negation occurs because it is, for the game state, a different copy of the card.
proposed solution: check for the chain relation before setting the leave_confirmed status
@edo9300 edo9300 merged commit eb0947d into edo9300:master Aug 7, 2023
12 checks passed
@NaimSantos NaimSantos deleted the negatechain branch October 12, 2023 08:38
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

Successfully merging this pull request may close these issues.

2 participants