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

Refactor: remove TargetPointer::getFirstAsFixedTarget #12547

Closed
Susucre opened this issue Jun 30, 2024 · 1 comment
Closed

Refactor: remove TargetPointer::getFirstAsFixedTarget #12547

Susucre opened this issue Jun 30, 2024 · 1 comment
Assignees
Labels
refactoring Developers topics about code and programming

Comments

@Susucre
Copy link
Contributor

Susucre commented Jun 30, 2024

A single card is using it [[Giant Oyster]]. I don't see a reason for the method. It was actually used by a bugged version of Narci, Fabled Singer, cleaned in 5016a57.

@Susucre Susucre added the refactoring Developers topics about code and programming label Jun 30, 2024
Copy link

Giant Oyster - (Gatherer) (Scryfall) (EDHREC)

{2}{U}{U}
Creature — Oyster
0/3
You may choose not to untap Giant Oyster during your untap step.
{T}: For as long as Giant Oyster remains tapped, target tapped creature doesn't untap during its controller's untap step, and at the beginning of each of your draw steps, put a -1/-1 counter on that creature. When Giant Oyster leaves the battlefield or becomes untapped, remove all -1/-1 counters from the creature.

@xenohedron xenohedron self-assigned this Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Developers topics about code and programming
Projects
None yet
Development

No branches or pull requests

2 participants