29 replies to this topic

[JohnnyC]

So even though the match is over and we've disconnected, we're stuck with our mechs "in game" until everyone exits the previous match?

Is that how this is working?

[Magik0012]

It definitely seemed to take a LOOOOONG time for me, even after staring at the post-game stats for a while.

[Gristle]

Averaging 45 seconds to get your mech back after a match. Please release the players mech as soon as they have exited the match.

[warner2]

Is this really how it works? I was wondering about it myself. The end of game screen does close itself after a time out, but yeah, if the mech really is tied up for the duration of the end of game screen being there, it's probably the wrong thing to do. The players mech should be released at the point they themselves have exited from the end of game screen.

Is this not obvious, why wasn't it foreseen, and done properly first time?

[Kaspirikay]

I've noticed a long delay after the last mech dies to the end screen popup time. Thats kinda annoying.

[Chavette]

Not at all if something, its shorter, it got shortened 2 patches back if im correct.

The end screen does have a bit high delay though.

[ElliottTarson]

This thread makes me giggle. You realize that mechs have ALWAYS stayed in game until the match instance closes right? That hasn't and probably won't change, you just have to wait an extra 10-15 seconds while someone looks at their stats. Problem? No.

[Tarman]

Oboy, this should turn into the next griefing qq.

PEOPLE ARE HOLDING ME HOSTAGE FOR LIKE 15 SECONDS

MY MECH LOOKED ALL RED IN THE MECHLAB

I WAS TRAUMATIZED GREATLY

[SI The Joker]

ElliottTarson, on 06 February 2013 - 05:50 AM, said:

This thread makes me giggle. You realize that mechs have ALWAYS stayed in game until the match instance closes right? That hasn't and probably won't change, you just have to wait an extra 10-15 seconds while someone looks at their stats. Problem? No.

You do realize that the session instance timeout has increased since they allow chatting at the end of the game now, right?

That makes the mechs stay in the match longer.

I started a thread about it in the patch feedback yesterday.

http://mwomercs.com/...08#entry1846708

To be clear, I'm not complaining about it either, I'm pointing it out in case it was not something that was meant to happen... you know... a bug?

Edited by SI The Joker, 06 February 2013 - 05:54 AM.

[ElliottTarson]

I do understand that. I also understand that It doesn't really make a difference, nor do I think it's really a bug. But if it is, then you've done right, no sense starting a General post about it.

[Kylere]

The delay has always been silly, now it is worse. If the match is over, and I exit it, the mech should be available then.

I suspect it is a move to get people to spend more C-Bills on modules.

[Shismar]

It definitely feels slower than before the patch. There is really no sense in artificially delaying the deployment with the same mech. Players who suicide or disconnect to farm cash are going to jump on the next mech anyway. So this just annoys those players like me who stay 'till the end and check out the end of match screen.

This delay is especially bothersome when I want to change loadouts after a match. I'd really like to see it gone.

[Frostbeast]

This annoys me, too

[Mercules]

Kylere, on 06 February 2013 - 07:10 AM, said:

The delay has always been silly, now it is worse. If the match is over, and I exit it, the mech should be available then.

I suspect it is a move to get people to spend more C-Bills on modules.

Probably not that sinister. More likely it is because their code simply locks the mech until the match instance clears. This is to stop people from jumping in game, suiciding, and then jumping into another game with the same mech. The code probably isn't that complex it just locks the mech out till the instance closes instead of checking to see if you are still in instance and the match is "done" but the instance still active.

[Kylere]

Mercules, on 06 February 2013 - 07:58 AM, said:

Probably not that sinister. More likely it is because their code simply locks the mech until the match instance clears. This is to stop people from jumping in game, suiciding, and then jumping into another game with the same mech. The code probably isn't that complex it just locks the mech out till the instance closes instead of checking to see if you are still in instance and the match is "done" but the instance still active.

yeah, but the suicides just flip mechs. I have one of all the modules, and two mechs I regularly play. I would not mind alternating rather than sitting around waiting, but it would require me to buy extra copies of the insanely overpriced modules.

I was referring to when it is done anyway, I see the end of match screens, I blink my eyes at all the garish little girl colors and exit it. The round was over, the match was scored, my mech should be available.

Now, if they want to give me a logical in game reason, "Jump Ship Recharging" or some such silliness i will take it and deal with it. Right now? It is just poorly coded. I admit to being obsessive compusive but last night I had more than one match that took over 4 minutes to free up my mech.

[Mercules]

The logical reason is:

We can waste time coding in the "Is he out of that screen?" check or simply leave it as is, expect adults to not whine over 15-45 seconds lost, and code something else the game really needs.

[Joseph Mallan]

Frostbeast, on 06 February 2013 - 07:50 AM, said:

This annoys me, too

Me too.

Mercules, on 06 February 2013 - 08:21 AM, said:

The logical reason is:

We can waste time coding in the "Is he out of that screen?" check or simply leave it as is, expect adults to not whine over 15-45 seconds lost, and code something else the game really needs.

Even though I want to agree with this! i get impatient too.

[Twelfth]

so slow

moo

[Mercules]

Joseph Mallan, on 06 February 2013 - 08:23 AM, said:

Me too.
Even though I want to agree with this! i get impatient too.

I do too but then I think to myself, "I should have my mech in a couple seconds here... next time though I am making good use of that time to wander into the kitchen and make a Johnny Jump-up. "

[Kylere]

Mercules, on 06 February 2013 - 08:21 AM, said:

The logical reason is:

We can waste time coding in the "Is he out of that screen?" check or simply leave it as is, expect adults to not whine over 15-45 seconds lost, and code something else the game really needs.

As an adult I can tell time and I promise you that 4 minutes is NOT 15-45 seconds. Anyone not a child realizes that fact.