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

New cards (MKM) #4746

Closed
wants to merge 206 commits into from
Closed

New cards (MKM) #4746

wants to merge 206 commits into from

Conversation

dracontes
Copy link
Contributor

@dracontes dracontes commented Feb 26, 2024

Tested card scripts

* With an assist from Glorax's attempts at these cards.

Minor Fixes

  • Updated Mythos of Snapdax to reflect the admittedly contrived possibility of a planeswalker also being a land.
  • Fixed some inconsistent capitalization issues with a few parameters, always defaulting to the more common version.
  • Updated the Mystery Booster Playtest Cards \editions file as recommended on Discord to disambiguate between its Red Herring and the MKM one.

Split off into #4754
Split off into #4753

This was referenced Feb 27, 2024
@dracontes dracontes changed the title New cards (MKM, MH3), minor fixes New cards (MKM) Feb 27, 2024
@tehdiplomat
Copy link
Contributor

Whoever ends up merging this, can we make sure to squash and merge so we don't have 200 commits being added for 4 cards.

@tool4ever
Copy link
Contributor

One comment left open (in case you miss it)

SVar:DBForEach:DB$ RepeatEach | RepeatPlayers$ Player | RepeatSubAbility$ DBChoose | SubAbility$ DBDestroyAll
SVar:DBChoose:DB$ ChooseCard | Defined$ You | ChoiceZone$ Battlefield | Amount$ 1 | Choices$ Land.nonBasic+RememberedPlayerCtrl | Optional$ True | ImprintChosen$ True | ChoiceTitle$ Choose up to one nonbasic land this player controls.
SVar:DBDestroyAll:DB$ DestroyAll | ValidCards$ Land.nonBasic+IsImprinted | RememberLKI$ True | SubAbility$ DBSearch
SVar:DBSearch:DB$ ChangeZone | Origin$ Library | Destination$ Battlefield | Tapped$ True | ChangeType$ Land.Basic | ChangeNum$ 1 | RememberChanged$ True | DefinedPlayer$ ImprintedController | Optional$ True | SubAbility$ DBCleanup
Copy link
Contributor

Choose a reason for hiding this comment

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

why are you using ImprintedController here?
only RememberedController would have fewer (in case some were indestructible)
(the RememberChanged also does nothing)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm using ImprintedController because I lifted a good deal of the script from From the Ashes. I imagine then that one also needs some updating. My tendency, navigating the code, likely unaware whether or not parameters are interchangeable, is to use what, given the name, seems to be the most relevant one.
(Forgot to remove RememberChanged even knowing it was setting up library shuffling. My bad on that one.)

Copy link
Contributor Author

@dracontes dracontes Feb 28, 2024

Choose a reason for hiding this comment

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

Just replaced ImprintedController with RememberedController to test it out and, on the selected lands being destroyed, I get no prompt to search my library for a land nor do tapped lands show up on my AI opponents' battlefields. I do vaguely recall this being an issue but I'm about 10 iterations deep on this script at this point.

Copy link
Contributor

Choose a reason for hiding this comment

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

well RememberLKI doesn't exist on DestroyAll
so use RememberDestroyed

@Hanmac
Copy link
Contributor

Hanmac commented Feb 29, 2024

@dracontes you could try to make a "git rebase" too to skip the unwanted commits
https://git-scm.com/docs/git-rebase

check "git rebase -i" to go into interactive mode, then you can "remove" the commits you don't want in this branch

@dracontes
Copy link
Contributor Author

@dracontes you could try to make a "git rebase" too to skip the unwanted commits https://git-scm.com/docs/git-rebase

check "git rebase -i" to go into interactive mode, then you can "remove" the commits you don't want in this branch

Having looked at my options, installing GitHub Desktop and Git Bash, I feel like I can squash commits confidently enough in the former. Otherwise, it'll definitely take me a while to figure things out, seeing as I've never used this software before. Unfortunately, the day job hasn't allowed me a whole lot time lately.

@Northmoc
Copy link
Contributor

Northmoc commented Mar 1, 2024

Closing in lieu of #4764
I didn't want to mess with your master
In future, try creating a branch with new changes before creating a PR

@Northmoc Northmoc closed this Mar 1, 2024
@dracontes
Copy link
Contributor Author

Closing in lieu of #4764 I didn't want to mess with your master In future, try creating a branch with new changes before creating a PR

Fair enough and much obliged for the quick resolution to this pickle :)
Looking into various ways to correct the situation I'd put myself in, I've already come across some best practice recommendations for code review. I'll be sure to follow those.

@tehdiplomat
Copy link
Contributor

Thanks for trying to push it forward though!

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.

5 participants