A part of the comment for the relevant code for this behavior:
We're skipping the "choose X" part and having it be implicit to your choice of resource
This departure from the rules as written was an intentional choice to simplify the user experience for this card. As you say, in 99.99% of games (I'd say more...), you want to get the most loyalty you can from the Casualty ability. In cases this edge-y, we consider the needs of the many to outweigh the needs of the few... or the one. #wotc_staff
If you haven't done the actual draft yet and you resign, the system will automatically return your entry.
This is a list of links to comments made by WotC Employees in this thread:
Looks like this should be fixed with the DMU release
Thanks bot, but I deleted that comment because QA realized the chains from the Stun counters don't have this problem, but normal "won't untap" chains do. So there's still a bug to solve.
This is a bot providing a service. If you have any questions, please contact the moderators.
Thanks bot, but I deleted that comment because QA realized the chains from the Stun counters don't have this problem, but normal "won't untap" chains do. So there's still a bug to solve.
Looks like this should be fixed with the DMU release
Hopefully its put in straight rather than messed around, since its AFAIK not designed for multiplayer particularly
The Arena version of the set will be the same as the printed version. No additions, removals, or changes.
Aug 18, 18:30 UTC
Completed - The scheduled maintenance has been completed.
Aug 18, 15:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 16, 15:30 UTC
Scheduled - @MTG_Arena maintenance will occur to deploy the 2022.18.60 game update.
⏲️ Full deployment estimated at ~3 hours.
🛠️ No downtime is expected but may be experienced during maintenance period.
💻 Restart required.
📝 Patch notes available soon after.
devtrackers.gg
