2 replies to this topic

[TopHatCat]

So over the past few games, I've actually had 2-3 people D/C in each. It was absolutely crushing, despite how well we played, we were just out numbered and out tonned.

Now I can't even begin to imagine how difficult/easy this would be to implement.
But I would love to see a system where, once you are destroyed, you can jump in to one of the disconnected Mechs and pilot that, bringing it back into the battle to help out your team.

Obviously my main concern is that at lower ranks, that light that always sprints ahead then dies instantly would end up in the well build Atlas and not be helpful at all, so I would recommend putting some restrictions in. Firstly, allowing players to choose which disconnected mech they take control of, second perhaps have some restriction where if you are dropping as a light, you can only choose a light/medium to take over, if you drop as a heavy you may pick medium/heavy/assault.... something like that. Obviously if the real pilot reconnected, you would get kicked out and he'd return to the cockpit.

My only concern would be, you'd need temporary weapon groups since everyones set up is different...

But basically yeah, I've had so many games now where we have been 2 Assaults down and I've so desperately wanted to climb out of my mediums cockpit and get into one of those things instead! Would be much more helpful to my team that way.

Perhaps I am just venting from a few bad games, but there is nothing worse than losing a really close fight.... only to change the death cam onto the last remaining team member. Who is a disconnected assault sat in base.... and you just have to sit there and watch whilst the enemy team hunts it down :/

[Zephonarch II]

This has happened PLENTY of times since 2012, back in 8v8 where it was far more severe for a disco to join a game. I'm for it personally because simply rejoining a game takes too much time and most people who stay disconnected throughout half the match usually stay that way. It would be the same as inactivity kicking and in the end it'd improve the fairness of most fights.

I think though there was one youtube video by FantasticTuesday, where he was spectating a disco'd Commando long long ago in MWO and a Centurion began playing with it. (Bumping into it; Wasting a perfectly good free kill) The Commando reconnected, and killed him. Lol... But really it took the whole match for the Commando to reconnect? We can have other memorable moments in MWO that don't involve inactivity Saving grace miracles.

Edited by Zephonarch II, 26 February 2016 - 09:57 AM.

[Ano]

Lovely idea though it may be, I think it's effectively impossible to implement, and would be pretty unfair.

Imagine: as you load into a match, your game client crashes. Or perhaps your internet connection drops momentarily and you have to re-log. And you get back to the match and someone else is piloting your mech.

So then you have decide after how much inactivity do we declare someone "absent" and their mech available for re-piloting. And who gets to pilot it -- first person to die? Person in the weight class?


IMO, that's all a bit much. It *is* a total PITA when you have a couple of discos on your team and even though the rest of the team does pretty well, it's just not good enough to win -- but perhaps with one more working mech, you would have. I just don't think there's a practically implementable way for your proposal to work