somsoc#29315
My feedback
88 results found
-
5 votes
An error occurred while saving the comment -
6 votessomsoc#29315
supported this idea
·
-
70 votessomsoc#29315
supported this idea
·
-
135 votes
An error occurred while saving the comment somsoc#29315
commented
Played in the Historic Shakeup event, lost two pips of rank for victory :/ There were no issues in the game.
somsoc#29315
supported this idea
·
-
25 votes
An error occurred while saving the comment somsoc#29315
commented
Might have to do with creatures or lands producing mana conditionally? And/or things like food sacrificing for mana?
I had Faeburrow Elder producing enough mana for me to sacrifice a food, which I needed to do in response to my own spell (to prevent death to life loss), but was not given the chance to respond after putting my own spells on the stack.
somsoc#29315
supported this idea
·
-
52 votes
An error occurred while saving the comment somsoc#29315
commented
Bump, still an issue.
Repro:
Demonstrate mostly easily versus the current Scute Swarm decks.Let opponent get a pile of triggers, tap all lands and and hit respond to all so you're 'F6d'. Watch both game clocks. Opponent won't lose any time on their clock, but you will lose 1-2 seconds per each of their triggers! Even though you cannot physically do anything quicker and you've auto passed all priority steps.
[Also note how ridiculous it is that when they have 40 scute swarm triggers you make us sit through all 40 of them and the game doesn't batch them into a single big trigger and just plop the token stack onto the board - just ask players IF and when they want to intercede in the trigger stack - if they don't, then handle all the triggers together].
This is abusable and it will cost people matches when the clock is tight.
An error occurred while saving the comment somsoc#29315
commented
This is still happening in the current version of the game. It's abusable and people are exploiting it to run down the clock when they aren't otherwise capable of actually winning the game. Or at least, maybe you'll win with 20 seconds remaining on turn 50 an hour and a half later, but they're counting on you conceding before that.
Previously, Resolve All quickly and efficiently ran through all the triggers. As of earlier this year, it slowed to a crawl when handling even rudimentary triggers. When players hit 'resolve all' scale the speed of the animations, effects, etc etc depending on how many triggers there are. And you can handle them all en masse as long as you go through and check in advance whether the triggers will actually cause any new triggers. A digital game shouldn't be MORE clunky than handling hundreds of triggers than paper but currently it is!
An error occurred while saving the comment somsoc#29315
commented
Bump for this. Never noticed before this update, however Arena is now pretty slow at resolving triggers when there's dozens of them on the stack. Too slow to be honest.
At any rate, when one or both players have hit 'resolve all' there's no way they should be losing clock for Arena's server latency.
I probably lost a few minutes in the game from the attached screenshot since I was trying to go wide versus 'Revenge of the Ravens', and every attack step generated a few dozen triggers *for my opponent*, but my clock was ticking down while Arena resolved them one-by-one.
I am sure that players are losing matches to this stuff, as it was, I might have ended up losing the next game to time but my opponent conceded to spare us both the agony.
somsoc#29315
supported this idea
·
-
Black screen on match start
-
Log20210129_054116.log 15 KB -
Captura de tela 2020-12-02 001303.png 132 KB -
Captura de tela 2020-12-02 001027.png 325 KB -
Captura de tela 2020-11-28 110832.png 362 KB -
Captura de tela 2020-11-27 175731.png 1842 KB -
UTC_Log - 09-18-2020 01.09.35.log 3 KB -
Log20200915_200105.log 23 KB -
2020-09-02.png 729 KB -
2020-08-31.png 1093 KB -
Log20200817_144311.log 234 KB -
Log20200816_201657.log 514 KB -
Log20200802_193259.log 67 KB -
Log20200704_164317.log 49 KB -
Log20200628_184519.log 39 KB -
IMG-20200625-WA0050[1].jpeg 1196 KB -
Log20200613_090208.log 22 KB -
Log20200525_205540.log 5513 KB -
MTGA 5_18_2020 11_46_12 PM.png 4599 KB -
MTGA 5_18_2020 11_46_05 PM.png 2794 KB -
Log20200514_190318.log 21 KB -
75274D8D-85F9-40BB-AD9F-7F62EA854BE6.jpeg 3317 KB -
Log20200423_223705.log 167 KB -
Log20200422_134718.log 3302 KB -
Log20200422_134053.log 259 KB -
Log20200419_174127.log 244 KB -
Log20200416_213542.log 157 KB -
Log20200413_151647.log 577 KB -
Log20200411_164634.log 486 KB -
20200313_105126.mp4 6224 KB -
Log20200213_113036.log 17729 KB -
Log20200212_191822.log 743 KB -
Black Screen.jpg 14 KB -
erro arena 2.png 203 KB -
erro mtg.png 158 KB -
erro.png 490 KB -
Log20200125_123023.log 653 KB
4,644 votesAn error occurred while saving the comment somsoc#29315
commented
Everyone should be really careful with downloading random .dll files (as in don't do it, only use official installers from trusted companies).
The black screen on start up does actually go away after a time (30secs - 1 minute) and you get into the game properly.
Maybe Arena's servers are overloaded or the path to them is congested which is causing the client to hang on loading while it waits.
-
-
268 votessomsoc#29315
supported this idea
·
An error occurred while saving the comment somsoc#29315
commented
This has been an issue for at least a month. We're beyond the point where this should be fixed.
Clearly the client has no problem reconnecting since we can hear the game sounds, but there is a bug with the loading process spawning a duplicate waiting screen after the game loads.
Wizards seem to like deleting threads reporting the issue but that doesn't actually fix the issue. Not a good look.
![IMG-20200625-WA0050[1].jpeg 1196 KB](/assets/221430715/IMG-20200625-WA0050%5B1%5D.jpeg){kind=link}
Colorless isn't a color...