To the people who are defending the client: Yes you can get on and play games sucessfully, but that should not be our only expectation. A piece of software should be a reflection of the revenue that it generates. The current client is something that you would expect out of a startup company trying to get their foot in the games industry and doesn't have the revenue to develop or support a high end piece of software. With a company at the level of Hasbro and the longevity of MTGO we should not have to settle for a mere functional game and have to overlook things like ascetics, ease of use, or technical issues like memory leak.
My thoughts exactly, sure, the client works, but we are setting our standards pretty damn low if "it lets me log in and play magic" is our only expectation. For what we are paying for this product, we really should expect more, not just bells and whistles, but polish, features and usablility.
Sadly though, while people are willing to just accept it for what it is, there is never going to be any change, why would they invest in it if people are just going to play regardless. The only thing that would see change would be a reduction in revenue.
To the people who are defending the client: Yes you can get on and play games sucessfully, but that should not be our only expectation. A piece of software should be a reflection of the revenue that it generates. The current client is something that you would expect out of a startup company trying to get their foot in the games industry and doesn't have the revenue to develop or support a high end piece of software. With a company at the level of Hasbro and the longevity of MTGO we should not have to settle for a mere functional game and have to overlook things like ascetics, ease of use, or technical issues like memory leak.
Yes this exactly. By now I figured I would only see cards in my hand, and actual 3D models on the play field.
Everyone always brings up the coders. The coders likely are not the problem.
That would depend on the issues.
I, having never dabbled in MTGO, wanna know what are the issues
- Is the client doing things noticeably inefficiently?
- Is the client doing things in such a way where it lags un-necessarily, causing massive performance issues?
- Is it not optimized as much as it could be
- Is the client bugging out and glitching in certain areas?
- Do updates break things inexplicably?
I, having never dabbled in MTGO, wanna know what are the issues
- Is the client doing things noticeably inefficiently?
- Is the client doing things in such a way where it lags un-necessarily, causing massive performance issues?
- Is it not optimized as much as it could be
- Is the client bugging out and glitching in certain areas?
- Do updates break things inexplicably?
I am curious.
Yes on all accounts, but all this tells you is that it's an old piece of software probably covered in mountains of bandaids. It may have been how we wrote software 10 years ago (think waterfall if you know programming) and now MTGO is stuck with it.
Yes on all accounts, but all this tells you is that it's an old piece of software probably covered in mountains of bandaids. It may have been how we wrote software 10 years ago (think waterfall if you know programming) and now MTGO is stuck with it.
It will never get better barring a rewrite.
We're talking about V4 here, which is apparently their new 'latest and greatest' and they needed to get outside help in to stop it from being a laggy mess (in the collection screen mainly)
Yes on all accounts, but all this tells you is that it's an old piece of software probably covered in mountains of bandaids. It may have been how we wrote software 10 years ago (think waterfall if you know programming) and now MTGO is stuck with it.
Seems to me that it isn't so much the age of the program as the upkeep and development of the source code, and at least partially those leading the project who could implement practices that at least reduce if not eliminate the "band-aiding" that had been going on, is going on, and as a result a lot of the issues that had been popping up... is that close or way off?
Seems to me that it isn't so much the age of the program as the upkeep and development of the source code, and at least partially those leading the project who could implement practices that at least reduce if not eliminate the "band-aiding" that had been going on, is going on, and as a result a lot of the issues that had been popping up... is that close or way off?
I think V4 (the newest version) suffers alot from its initial design having some really really weird decisions, and the development team having to try to work around those issues to try to make things workable, instead of scrapping parts of the client and starting again. I suspect this is because whoever did the initial design is still on the team and is refusing to let them really fix the issues (too attached to their creation) but I could be wrong there.
The other major issue is the platform they chose to use to develop the client (WPF) is:
- Probably not really designed for this kind of use
- Has more or less been discontinued by Microsoft
- Seems to be quite specialised when it comes to making this work well within the framework, and they just don't have the talent on staff with the experience necessary to make it work well. As can be seen by the fact they needed to bring in an external team to optimise the client.
- Even after that optimisation, its still not really (in my opinion) as responsive as it should be and there are (again, in my opinion) alot of weird design choices still evident.
- Lastly, this framework is windows specific, which means you wont see it native on anything MAC (I assume it wouldn't be possible to port to iOS or android either.
Its just overall a really really weird choice of platform to use, I can only assume that there was some specific feature it has that someone really wanted to use, or perhaps its like Visual Basic, easy to quickly throw together something that works, more difficult to make something that works well.
I'm on version 3.4 and have never noticed any of these problems. I may have crashed once or twice but it never lead to any problems. I hate the new beta though.
I'm just wondering what I agreed to in the EULA says anything about the event that MTGO completely goes under and shut down. "Thanks for your 100's of dollars, bye" type thing. I'm pretty invested in this, but I'm playing less and less these days.
u would think since it IS 2014 that they are able to upgrade the client to something simiar to heartstone client. I love the ease of access of the heartstone client. Minus the fact the art looks very kiddy, if MTGO can become something like that, more people would care and play it.
I remember getting 1 reply after submitting for compensation that I'm crashing too often and that they would not compensate me. Apparently its my fault their crappy client closes itself mid draft and then for some odd reason sees me as being online and wont let me login. I submitted another compensation report after that quoting the previous "customer reps" reply and immediately got a full apology from another person and instant reimbursement.
At least they are fast with those band-aids to keep us "content"
Wow that is a serious bug! Just when everybody wonders what will happen in Modern after the DRS ban, Melira Pod gets soft-banned. A full week of MTGO tournaments will be a joke.
They only fix things during downtime, so we don't even know which downtime it'll get fixed.
They didn't fix the Jace bug for ~2 months? And there was a freaking MOCS going on, and people lost because of it.
I could see them not doing anything about it for a while.
It looks like they finally fixed the floating mana bug, so people can now play scapeshift again Fixed: Effects such as Extort or Pact of Negation that require mana now work properly when a player has mana in his or her mana pool.
It looks like they finally fixed the floating mana bug, so people can now play scapeshift again Fixed: Effects such as Extort or Pact of Negation that require mana now work properly when a player has mana in his or her mana pool.
Uh? I didn't know that. That explains why I didn't encounter Scapeshift recently.
Yeah, mana leak and curse catcher were basically counterfluxes vs a scapeshift player floating mana, they could not pay for taxing counters.
These people are idiots. I have no idea how you could possible make one glitch cause the others as they describe if you have remotely competent code. For example, starting life total should be a constant, rather than loading it from memory/server. They seriously need to scrap their entire architecture and rebuild it competently.
I really don't get the hate. Does the client work? Yes. Can I log on, any time, and play some cards? Yes. Just because something doesn't have whatever you believe to be some "zomg must-have feature" (that likely isn't even as "must have" as you adamantly believe), doesn't mean that it's a bad client.
You have very low standards. Do you live in a cardboard box?
Not sure 3drinks or I will follow you. One makes it as social as you want to. Most people will start/join a game, will not say hello or gg, just play the game, and leave. In other games, people will comment on cards, synergies, strat, etc.
It should either automatically use the colorless mana or prompt you to choose what mana you want to use for the colorless cost.
I would try to replicate this in solitaire. If it happens again, try messaging an ORC and see what they say, then if they tell you it's bugged you can report it.
so they make the *****tiest changes they can, then raise them back up when people complain, but they make the "new" change worse than we originally had it
One day I hope to find a job where I can constant fail to deliver the product I am paid to deliver, but never be in a position where I am in danger of getting fired.
Seriously, I don't give a damn if these issues are different to what was happening before, its still yet another failed MOCS finals.
One day I hope to find a job where I can constant fail to deliver the product I am paid to deliver, but never be in a position where I am in danger of getting fired.
Seriously, I don't give a damn if these issues are different to what was happening before, its still yet another failed MOCS finals.
Congress is calling your name then.
Seriously though, its getting pretty embarrassing whats happening with MTGO, but sadly nothing will stop WoTC's MTGO department from being the biggest screw ups that they can possibly be. It almost feels like their goal is to be as bad as possible.
Private Mod Note
():
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Maybe they're actually going to build something that looks like it belongs in 2014 instead of 2004?
Doubtful, but I can dream right?
My thoughts exactly, sure, the client works, but we are setting our standards pretty damn low if "it lets me log in and play magic" is our only expectation. For what we are paying for this product, we really should expect more, not just bells and whistles, but polish, features and usablility.
Sadly though, while people are willing to just accept it for what it is, there is never going to be any change, why would they invest in it if people are just going to play regardless. The only thing that would see change would be a reduction in revenue.
Yes this exactly. By now I figured I would only see cards in my hand, and actual 3D models on the play field.
That would depend on the issues.
I, having never dabbled in MTGO, wanna know what are the issues
- Is the client doing things noticeably inefficiently?
- Is the client doing things in such a way where it lags un-necessarily, causing massive performance issues?
- Is it not optimized as much as it could be
- Is the client bugging out and glitching in certain areas?
- Do updates break things inexplicably?
I am curious.
Yes on all accounts, but all this tells you is that it's an old piece of software probably covered in mountains of bandaids. It may have been how we wrote software 10 years ago (think waterfall if you know programming) and now MTGO is stuck with it.
It will never get better barring a rewrite.
We're talking about V4 here, which is apparently their new 'latest and greatest' and they needed to get outside help in to stop it from being a laggy mess (in the collection screen mainly)
Seems to me that it isn't so much the age of the program as the upkeep and development of the source code, and at least partially those leading the project who could implement practices that at least reduce if not eliminate the "band-aiding" that had been going on, is going on, and as a result a lot of the issues that had been popping up... is that close or way off?
I think V4 (the newest version) suffers alot from its initial design having some really really weird decisions, and the development team having to try to work around those issues to try to make things workable, instead of scrapping parts of the client and starting again. I suspect this is because whoever did the initial design is still on the team and is refusing to let them really fix the issues (too attached to their creation) but I could be wrong there.
The other major issue is the platform they chose to use to develop the client (WPF) is:
- Probably not really designed for this kind of use
- Has more or less been discontinued by Microsoft
- Seems to be quite specialised when it comes to making this work well within the framework, and they just don't have the talent on staff with the experience necessary to make it work well. As can be seen by the fact they needed to bring in an external team to optimise the client.
- Even after that optimisation, its still not really (in my opinion) as responsive as it should be and there are (again, in my opinion) alot of weird design choices still evident.
- Lastly, this framework is windows specific, which means you wont see it native on anything MAC (I assume it wouldn't be possible to port to iOS or android either.
Its just overall a really really weird choice of platform to use, I can only assume that there was some specific feature it has that someone really wanted to use, or perhaps its like Visual Basic, easy to quickly throw together something that works, more difficult to make something that works well.
http://www.twitch.tv/darkest_mage/b/500512333?t=379m15s
we're going to be screwed for a while
I remember getting 1 reply after submitting for compensation that I'm crashing too often and that they would not compensate me. Apparently its my fault their crappy client closes itself mid draft and then for some odd reason sees me as being online and wont let me login. I submitted another compensation report after that quoting the previous "customer reps" reply and immediately got a full apology from another person and instant reimbursement.
At least they are fast with those band-aids to keep us "content"
https://twitter.com/kaOz_Zeh/status/433749169740587009
They only fix things during downtime, so we don't even know which downtime it'll get fixed.
They didn't fix the Jace bug for ~2 months? And there was a freaking MOCS going on, and people lost because of it.
I could see them not doing anything about it for a while.
It looks like they finally fixed the floating mana bug, so people can now play scapeshift again
Fixed: Effects such as Extort or Pact of Negation that require mana now work properly when a player has mana in his or her mana pool.
Yeah, mana leak and curse catcher were basically counterfluxes vs a scapeshift player floating mana, they could not pay for taxing counters.
https://twitter.com/mtgworth/status/434071621368680449
amazing they're fixing things now instead of patch day
If this kind of stuff is still happening they really should be pushing back BNG pre/release events until it's fixed.
Practice for Khans of Tarkir Limited:
Draft: (#1) (#2) (#3) (#4) (#5)
I totally agree. It will make people pretty angry if this happens in tournaments bigger than a daily.
Not sure 3drinks or I will follow you. One makes it as social as you want to. Most people will start/join a game, will not say hello or gg, just play the game, and leave. In other games, people will comment on cards, synergies, strat, etc.
I buy HP and Damaged cards!
Only EDH:
Sigarda, Host of Herons: Enchantress' Enchantments
Jenara, Asura of War: ETB Value Town
Purphoros, God of the Forge: Global Punishment
Xenagos, God of Revels: Ramp, Sneak, & Heavy Hitters
Ghave, Guru of Spores: Dies_to_Doom_Blade's stax list
Edric, Spymaster of Trest: Donald's list
I would try to replicate this in solitaire. If it happens again, try messaging an ORC and see what they say, then if they tell you it's bugged you can report it.
http://www.wizards.com/Magic/Magazine/Article.aspx?x=mtg/daily/other/02172014/ptqmagic2015
and a qp for the top 8 of the mini PEs
http://community.wizards.com/content/blog/4059186
so they make the *****tiest changes they can, then raise them back up when people complain, but they make the "new" change worse than we originally had it
Seriously, I don't give a damn if these issues are different to what was happening before, its still yet another failed MOCS finals.
Congress is calling your name then.
Seriously though, its getting pretty embarrassing whats happening with MTGO, but sadly nothing will stop WoTC's MTGO department from being the biggest screw ups that they can possibly be. It almost feels like their goal is to be as bad as possible.