bonsai#70698
My feedback
222 results found
-
1 vote
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment bonsai#70698
commented
I should've been more specific Rezzaahan. Though I have a principle objection to any/ll 2-card blind combos (*sigh* Splinter Twin), my specific issue in the post not with the 2-card Bloodthirsty Conqueror combos existing in Arena (I think there's 8 atm), but the implementation which results in a non-interactive loop that either outright crashes the client or would result in a draw IRL.
WotC *can* fix this, they have chosen not to address it. The *fix* atm on macOS is to simply kill the Arena client process.
bonsai#70698
shared this idea
·
-
3 votes
An error occurred while saving the comment bonsai#70698
commented
I concur with proposal #1. It should take no more than 7 seconds to decide on any mulligan.
With respect to #2, I think the time-outs should be much shorter, but you should be able to "bank" more of them.
Especially when board-states explode after 1 turn with multiple interaction paths it can take quite some time to ferret everything out on a small screen with many tiny cards.
I've long-since stopped expecting WotC to do ANY player moderation. I just keep a list of "known bad" actors (~100 atm) and never play with them.
bonsai#70698
supported this idea
·
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
Unstoppable Slasher can't instakill by itself if your life total is 18. Likely, a card like Bloodletter of Aclazotz was controlled by your opponent when this happened.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
I concur. Given the trivial amount of actual computer storage required for a deck. An online limit of 100 is laughably small.
Yes, I'm aware decks can be easily imported/exported, but that's not the core issue.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
FWIW, it's clear WotC has learned the error of its ways and has been printing less cheap removal in recent sets. The current spate began in Ixalan and continued through Bloomburrow.
It's trivial to construct an all-kill 1:1 removal deck which, though not necessarily competitive, introduces a very unfun interaction into games.
-
1 votebonsai#70698
shared this idea
·
-
2 votes
An error occurred while saving the comment bonsai#70698
commented
I agree that Alchemy cards are, generally, poorly balanced and shouldn't be forcibly included in ANY format.
I don't play Brawl on Arena for that specific reason.
-
2 votesbonsai#70698
supported this idea
·
-
3 votesbonsai#70698
shared this idea
·
-
2 votes
An error occurred while saving the comment bonsai#70698
commented
Thanks very much for clarifying Rezzahan. I came to Magic well after Oblivion Ring and was, initially, also confused in some Sheltered By Ghosts interactions.
-
2 votes
An error occurred while saving the comment bonsai#70698
commented
I don't play Pioneer, but I voted for Leyline of Resonance to be banned in all of Standard as it's just OP given even post-ban red aggo power.
Generally speaking, just like alternative win conditions, leylines were/are a bad idea in Magic.
Play should always begin on Turn 1.
bonsai#70698
supported this idea
·
-
2 votes
An error occurred while saving the comment bonsai#70698
commented
A bit of an update. This appears to be a Unity engine issue where the game "portal" (i.e. the window size) is not being calculated properly on macOS when in "full-screen" mode.
This is a regression to an early bug circa (3?) years ago. Unfortunately, this time a simple screen-mode-reset does not fix the problem.
I've attached a screenshot of the same version in "windowed mode" showing the correct aspect ratio of the portal wrt the screen-size. It's no longer zoomed.
This is fundamental Unity game engine calculation stuff folks and nothing Arena-specific. Check your test-suites as this should be an easy-win fix.
bonsai#70698
shared this idea
·
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
I am not familiar with that particular card interaction, but I have encountered a similar "surprise loss" and I agree that not placing an auto-stop there is a flaw (not bug) in Arena's current implementation.
In any IRL game, this lack-of-stop would never occur.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
LOL. I didn't see Rezzahan's comment until now. Yeah, what he said. ;)
An error occurred while saving the comment bonsai#70698
commented
This is by-design according to the rules of magic.
-
2 votes
An error occurred while saving the comment bonsai#70698
commented
I concur.
One would think that, by this time, WotC personnel would actually (formally) post on their own forum (I know 2 that do sub rosa) and they'd have a bug/issues triage list on their own property or a self-hosted Github equivalent.
One would think...
bonsai#70698
supported this idea
·
-
4 votes
An error occurred while saving the comment bonsai#70698
commented
Sadly, this bug has been in Arena for over 2 years and I've lost hope of WotC ever addressing it.
-
2 votesbonsai#70698
supported this idea
·
-
3 votes
An error occurred while saving the comment bonsai#70698
commented
Well, FWIW I have over 5k of play-hours on Arena, have reported over 40 players for conduct and have never seen it have ANY effect. I stopped reporting player conduct about 4 months ago.
Just keep a log of known-bad players and refuse to play with them. Atm, my known-bad list is over 80 players.
If WotC refuses to do player moderation, at least give moderation tools to the players to self-manage this issue.
bonsai#70698
supported this idea
·
-
3 votes
An error occurred while saving the comment bonsai#70698
commented
I whole wholeheartedly concur that "emergency bans" should be rare, but possible.
Atm, the only decks I play without Vivi Ornitier are either deliberately mono-colored or choose not to splash red or blue.
Vivi Ornitier is so powerful that's you're a fool to NOT play it if you're in those colors. It's even worth splashing for this single card unless a 3 mana creature somehow is anathema to your deck's goals.
It's akin to Cori-Steel Cutter in red prior to its ban.
bonsai#70698
supported this idea
·
FWIW, I recently had a game where Requisition Raid was bizarrely un-castable ( https://feedback.wizards.com/forums/918667-mtg-arena-bugs-product-suggestions/suggestions/50435961-requisition-raid-denied-all-casting-options ) despite having available targets, available mana, and no other board interaction limitations.
This is under Version 2025.51.20.3396.1177291 on macOS Sonoma 14.3 (23D56)
I've never had issues casting it before and I've cast it successfully in many games since then w/o issue though none with such a "target rich" environment so I'm wondering if it's (yet another) alternative-casting-cost bug.