R52 Patch: Really?!?

MarvelMan
MarvelMan Posts: 1,350
edited May 2014 in MPQ General Discussion
So, I had been putting off downloading the R52 patch since I was on cell (home internet was down from Thursday night to late last night). This morning I pull up the app walking into work, go to my high point match in the Sim to try to get the Devil D done before the refresh. I figured it was high time to finally attempt that node in hard so I boosted with b/p, g/b and +all. I got into the match before seeing the update message again. Things were going better than anticipated (go go boosts!): knocked down the assn, had DD himself down to ~1k and the other goon to <500 then the game kicked me with the forced update message meaning I lost that match. Boosts down the drain plus I had to use 3x health packs on the heros. The timing is ridiculous, there is no reason to force it DURING a match. /rantoff

Comments

  • Preach it loud!
  • Huh. I've never seen it force an update (at least on iOS). I always say skip until I'm done playing for a bit. I know there are listener APIs for android that can force an update.

    While I find it hard to empathize with you on the forced patching (you did kind of bring that on yourself - I've updated over 3G before, it's not terrible), I do feel more empathy with you that you've been without home internet for over 4 days. That's really rough.
  • No remorse. I get your home wifi may have been down but depending on the patch you can gain tremendous advantages over other people by not patching. The potential abuse outweighs the advantages. I get they could have a startup lockout and not midgame though.

    Patch making 12 strike tiles for your own team and none for the opponent comes to mind.

    Man I hate typing on stock Android kb...
  • It's still not "fair" that it happens in the middle of a match though. And be that there may be some kind of advantage...at least let the poor guy finish the match first then force and update. my gut feels for the OP, or it's indigestion.
  • Sorry, but they shouldn't force through the patch midday on the final day of a 7.5 day PVE. It could have waited until tomorrow. Especially since this patch also potentially requires an IOS update.
  • jojeda654
    jojeda654 Posts: 1,162 Chairperson of the Boards
    Riggy wrote:
    While I find it hard to empathize with you on the forced patching (you did kind of bring that on yourself - I've updated over 3G before, it's not terrible)

    OP may not have an unlimited mobile connection. If the update was released near the end of the bill cycle, then downloading the update might have used up the remainder of the data plan.
  • MarvelMan
    MarvelMan Posts: 1,350
    My complaint is not that they forced me to update, or even really that I lost my boosts/health packs as I get that it has to happen at some point to keep everyone on the same page, but that it occurred mid-match. There is just no logic that it can be triggered then rather than upon first connection, which had to occur to show me point losses in DO PVP plus it pulled current match values, or after the sync post match.


    side note: yeah, no home internet has been a pain. It did foce me to get reacquainted with that warm ball in the sky so I guess that is a plus. And i got to see some lighting from a thunder storm one evening.
  • I think the way it works is, when the patch is initially released they make the update optional, to give people a chance to update at home so they don't use mobile data. Then after a few days they make it mandatory so people can't abuse it. Seems like they hit the button while you were in a match. Sucks, but they did give you fair warning.
  • I guess my question is whether D3 forced an update via the app itself, in which case, yes it would have been nice to not have it happen mid-match; or alternatively was this just a "XX hours after the patch was released, it automatically forces an update" in which case it's the system and not the app that forced the update (as the system wouldn't know what you were doing in the app, just that it needed to force a patch).
  • MarvelMan
    MarvelMan Posts: 1,350
    Riggy wrote:
    I guess my question is whether D3 forced an update via the app itself, in which case, yes it would have been nice to not have it happen mid-match; or alternatively was this just a "XX hours after the patch was released, it automatically forces an update" in which case it's the system and not the app that forced the update (as the system wouldn't know what you were doing in the app, just that it needed to force a patch).

    I would guess its an XX hours after release scenario, but you would think they could include an if that waits til after a match is done if there is one in progress at that point.
  • MarvelMan wrote:
    Riggy wrote:
    I guess my question is whether D3 forced an update via the app itself, in which case, yes it would have been nice to not have it happen mid-match; or alternatively was this just a "XX hours after the patch was released, it automatically forces an update" in which case it's the system and not the app that forced the update (as the system wouldn't know what you were doing in the app, just that it needed to force a patch).

    I would guess its an XX hours after release scenario, but you would think they could include an if that waits til after a match is done if there is one in progress at that point.
    From a programming perspective, there are APIs that the developer could use to force an update but could be intelligent enough to not force the patch if <some condition> i.e. if they're in the middle of a match.

    However, if it's a system feature, the OS itself has no real contextual knowledge of what you're doing inside the app - it just knows that the app is running and doesn't even know what a match is, let alone that you're in the middle of one. It just knows that the patch was released say 36 hours ago and that it is now mandatory to kill the app and force an update.

    So if it's this latter kind of update, there's not much that can be done about it and it sucks. I'm mostly just pursuing this out of curiosity to see how it was implemented.
  • What would be nice is if they would not always penalize you when you get booted out of a match. Even if it was only once a week, it would be nice to not have to use health packs just because something happens to your connection in the middle of a match.
  • Spoit
    Spoit Posts: 3,441 Chairperson of the Boards
    Why not check (and force if necessary) before allowing him to start a match then?
  • start of game client would be more efficient, having additional checks and balances in between matches only slows things down.
  • If a patch is set to automatically update XX hours after release then having that timeframe included in the description (on forum as well as app store/steam equivalent) *from the start* seems like it would solve a lot of this kind of issue.

    I've seen messages like that included in all kinds of apps on both apple and android systems - and I always appreciate the courtesy from the devs who do so, even if it's not going to affect me personally. Someone without easy access to wifi atm can do the maths and work something out to suit their situation in the given timeframe - which seems more reasonable than some arbitrary behind-the-scenes mechanism activating regardless of circumstance.
  • ClydeFrog76
    ClydeFrog76 Posts: 1,350 Chairperson of the Boards
    I've had it forced on me before, too. Didn't even buy me dinner first.
  • Had the same thing happen to me some time ago, turned off automatic updating in the Play Store for MPQ after that. Didn't happen again, so might be an Android issue (and not the app).
  • MarvelMan
    MarvelMan Posts: 1,350
    Doombot77 wrote:
    Had the same thing happen to me some time ago, turned off automatic updating in the Play Store for MPQ after that. Didn't happen again, so might be an Android issue (and not the app).

    Im on iOS so your experience makes it sound more app centric than environment.