bonsai#70698
My feedback
222 results found
-
6 votesbonsai#70698
supported this idea
·
An error occurred while saving the comment -
2 votesbonsai#70698
shared this idea
·
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
Wow! So, basically, the "can't be countered" effect that Cavern of Lost Souls put on the creature Trumpeting Carnosaur was also applied to an enchantment and a sorcery spell cast with the no-mana cost clause of its Discovery mechanic.
I wonder if the fault lies with Trumpeting Carnosaur, Cavern of Souls, or the Discovery mechanic itself.
It would be a neat test to try this with other Discovery cards like Geological Appraiser or other land that disables countermagic like Mistrise Village.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
For low values of N, even a purely random distribution will have "clumps". FWIW, 10 is a very low value in this context.
As an experiment use a random number generator on a calculator or computer.
An even better illustration is to graph the Normal Distribution using discrete points for N=1, N=10, N=25, N=50, N= 75, N=100, N=200, etc. to watch how things form. Then repeat that formation sequencing process several times.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
I'll go further and allow users to simply set a 'favorite' playing surface and be able to exclusively play on that one.
For me, the only surface and music combination that I really, really don't like is Duskmourne. I'm pretty neutral on all the others, but if I had to choose only one to play on it would be the Bloomburrow river.
-
2 votesbonsai#70698
supported this idea
·
-
2 votesbonsai#70698
supported this idea
·
An error occurred while saving the comment bonsai#70698
commented
I wonder if this is an old bug resurfacing post-patch. Bitter Triumph had a bug shortly after its block release where it would get "stuck" on whatever initial casting cost was used such that no alternative casting cost was possible for the remainder of the match.
I posted on this previously https://feedback.wizards.com/forums/940206-mtg-arena-archive/suggestions/47521073-you-cannot-pay-with-life-when-casting-bitter-triu and it was fixed, but maybe there's been an unintentional reversion.
FWIW, one consistent source of individual card bugs has been alternative casting costs.
Most recently, it occurred with Rottenmouth Viper https://feedback.wizards.com/forums/918667-mtg-arena-bugs-product-suggestions/suggestions/48955952-new-rottenmouth-viper-mana-discount-calculation-b
-
4 votes
An error occurred while saving the comment bonsai#70698
commented
I would simply no longer play with any individual that goes by that name. If you're paired, insta-concede the match.
Technically, there could be other 'Nikoloplast' players as it's just a handle and not a unique identifier, but the odds are against it.
You can report them via WotC's official player conduct form: https://mtgarena-support.wizards.com/hc/en-us/articles/360025191111-Report-a-Player , but in all my years of playing Arena and reporting unsportsmanlike conduct, I've never seen it make any difference.
I've stopped bothering to report players and now expect zero player moderation on Arena.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
I agree, in the current Standard meta, there is far to much cheap removal. I believe that WotC realized their mistake based on so much less of it in the recent block.
I don't think self-milling is bad, but I've always felt that offensive milling should not be a mechanic in Magic. On Arena, I just insta-concede to mill decks. Though I could possibly win the match, even playing a few turns against offensive mill is unfun. It's kinda' obvious, but people play Magic to play the cards in their decks and offensive mill's explicit goal is to not let that happen.
Unlike with removal (excepting sweepers), counter-spells, or hand-hate, offensive mill is typically also a 1 for N effect instead of 1 for 1.
I don't think Counter magic is bad, but akin to hand-hate, it's a narrow-edged balance between the mechanic enabling dynamic creative game-play or lock-down tedium. We saw that with the recent Hopeless Nightmare ban.
Along the same lines, I don't feel alternative win conditions (Toxic, etc.) should be "a thing". Magic, or really any game, is the most fun when both opponents are trying to achieve victory via the same goal.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
Post your OS and version to help WotC track down the issue.
On macOS Sonoma 14.3 (23D56), I've been getting match crashes to the home screen and networking issues (infinite queuing, and random disconnects) for over 30 days.
-
5 votesbonsai#70698
supported this idea
·
An error occurred while saving the comment bonsai#70698
commented
FWIW, I've had stability and networking issues on Mac (macOS Sonoma v14.3 (23D56)) for more than 30 days.
I'd just wait until all the craziness of the Fall rotation and at least one patch from the inevitable new card bugs get worked out before playing again.
I'm personally not going to re-install and attempt to play until after August 15th.
-
2 votes
An error occurred while saving the comment bonsai#70698
commented
@KaufeeCake#01584 You're leveling some very serious allegations against WotC. Please share evidence to support them.
An error occurred while saving the comment bonsai#70698
commented
If there is data that supports a rigged shuffler, please share it. I have yet to see any evidence supporting that hypothesis.
-
2 votes
An error occurred while saving the comment bonsai#70698
commented
To be frank, I feel *all* alternative win conditions (and non-loss conditions) should be removed from the game.
Games are the most fun when opponents are both trying to achieve the same results to win.
bonsai#70698
supported this idea
·
-
2 votesbonsai#70698
supported this idea
·
An error occurred while saving the comment bonsai#70698
commented
Sadly, this has been an known issue on Arena for years and WotC does not seem to have a priority to fix it.
There's also the issue of Arena rewarding zero-interaction infinite combos (e.g. Marauding Blight-Priest + Bloodthirsty Conqueror) as Wins/Losses when according to Rule 731.4 they should be Draws.
"731.4. If a loop contains only mandatory actions, the game is a draw. (See rules 104.4b and 104.4f.)"
Whenever I see Bloodthirsty Conqueror enter the battlefield, I just concede.
-
3 votes
An error occurred while saving the comment bonsai#70698
commented
I think matchmaking can be improved, but I do not think the shuffler is rigged. It would not be in WotC's best interest to "rig" a shuffler and it would take a great deal of meta-gaming effort to "rig" a shuffler in any single way to benefit a particular cohort of players.
I can't comment on cheating tools / manipulation, but I wouldn't rule it out.
FWIW, I have over 5k hours on Arena and I've only had a handful (maybe 7?) Bo3 matches where things felt "off" and my opponent seemed to have complete knowledge of the, otherwise hidden, game states (library orders, hands).
Given that extreme ratio, I chalk those experiences up to my own fallacies of misleading vividness.
-
2 votesbonsai#70698
supported this idea
·
An error occurred while saving the comment bonsai#70698
commented
At this point, I simply recommend holding off attempting to play until well after the Fall rotation.
There have been consistent fundamental stability and networking issues on Android for the past 2 patches and consistent networking issues on Mac for the past 3 patches.
It's one thing to have single-card interaction bugs and a sideboard that can't count. It's entirely another to have consistent client crashes and networking time-outs/disconnects.
For whatever reason, I think WotC's resources have been stretched beyond its capacity to maintain Arena's infrastructure for at least the past 30 days; if not slightly longer.
I suspect they'll get freed-up after the push for the new release + Fall rotation has been completed.
At this point, I'm not planning on re-installing or attempting to play again until after August 15th.
-
8 votes
An error occurred while saving the comment bonsai#70698
commented
I concur that Alchemy cards are simply not as thoroughly Q/A'd as Standard.
The game should simply default to the last-played format as the vast majority of players tend to consistently play the same format.
-
2 votesbonsai#70698
supported this idea
·
An error occurred while saving the comment bonsai#70698
commented
Since the 2025.49.00 patch (~ 30 days ago) on macOS Sonoma 14.3 (23D56) I'd noticed a significant increase in queuing issues (waiting forever for a match or outright networking errors).
I've also had 2 instances where Bo3 matches should've continued, but I (likely both of us) were simply returned to the home screen (in lieu of sideboarding after game 1) as if the match had never taken place. No victory, loss, or draw--just an abrupt transition out of a match to home.
Atm, I just don't think WotC has the requisite corporate workforce/expertise bandwidth to support Arena and have uninstalled the game.
I'm hopeful things will stabilize after the Fall rotation and will re-install sometime in August.
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
That's a neat interaction I hadn't noticed before! Likely, since (atm) aside from Into The Flood Maw, I don't routinely play cards with Gift.
Thanks @Rezzahan#77802 !
-
1 vote
An error occurred while saving the comment bonsai#70698
commented
FWIW, I had that happen once after the 2025-49-20 patch (1 month ago) though it was in game 2 of a Bo3 match in Standard.
I also had an experience after winning game 1 and conceding game 2 (after multiple mulligans) it recorded the entire match as a loss without offering a game 3.
Thankfully, those were single-instance events.
That said, I've encountered just too many bugs in the past month (I'm on macOS Sonoma v14.3 23D56) for me to have confidence in Arena's stability atm.
Unfortunately, WotC's current bug reporting, tracking, resolution communications policies (atm) only serve to further enforce that opinion.
Wow. That sucks.
FWIW, I run Fabled Passage in several decks and just finished a 1 hour play session using Fabled Passage without encountering that bug.
I'm running Version: 2025.51.0.3347.1173794 on macOS Sonoma v14.3 (23D56).