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

Support engine tracking card mover vs. controller #6420

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

tool4ever
Copy link
Contributor

Adds support that will be needed for #5137

@tool4ever tool4ever added Game Mechanics Rules compliance Bringing the engine or cards closer to CR labels Oct 23, 2024
@tool4ever tool4ever marked this pull request as draft October 23, 2024 17:06
// Don't copy Tokens, copy only cards leaving the battlefield
// and returning to hand (to recreate their spell ability information)
if (toBattlefield || (suppress && zoneTo.getZoneType().isHidden())) {
copied = c;

// in some cases it's always affected that puts them in play (initially)
String defPutter;
if (cause == null || (!cause.hasParam("Putter") && (c.isToken() ||
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if I like it there

I probably would move the Putter logic into AbilityKey.addCardZoneTableParams

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmn, the problem is the Putter can be different players during the same effect

and most effects currently don't need to modify moveParams between cards and reuse them instead

so I'd have to refactor those further, especially when they pass down to helpers in SpellAbilityEffect like with discard?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

imo it would be more clean if the stuff is done in the specific SpellAbilityEffect classes (or a helper function)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game Mechanics Rules compliance Bringing the engine or cards closer to CR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants