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

Acme #3814

Closed
limnrix opened this issue Jul 26, 2018 · 3 comments
Closed

Acme #3814

limnrix opened this issue Jul 26, 2018 · 3 comments
Labels

Comments

@limnrix
Copy link

limnrix commented Jul 26, 2018

Virtual extra tag remains throughout run, rather than after first ice, wrongly triggering cards like Quantum Predictive Model and Dedicated Response Team. Would be useful to have a tag indication like that of Paparazzi, as well.

@nealterrell
Copy link
Collaborator

Acme is coded to disable itself after passing the first piece of ice. We'll need more information about the run you made in order to diagnose this.

@Zeofar
Copy link
Contributor

Zeofar commented Jul 29, 2018

I've figured out the likely issue here; The :rez event on Acme will be triggered by assets/upgrades/etc while in the outermost position, which makes the runner float extra virtual tags. Just needs a little extra logic to prevent irrelevant cards from interacting with the ability.

@limnrix
Copy link
Author

limnrix commented Aug 19, 2018

Now that the tag UI is broken by the attempt to show the virtual tags, I can see that an upgrade or asset rez results in 2 virtual tags.

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

No branches or pull requests

4 participants