38 replies to this topic

[Mazzyplz]

just leg them instead lol!

no actually i have been there, i have gone to a lot of trouble to reconnect only to realize a light mech was actually looking for discos to kill........ not fun; i sent a few expletives his way (probably shouldn't have) - but it was really the fault of MWO client crashing out of the blue as it does.

i would tell players not to go to the enemy's spawn at the beginning of the game to farm discos while the main force is doing a nascar lap...

if they disconnect in the middle of the field then shoot them dead, bad luck.. whatever

but if you are that raven that starts off the game looking to farm a disco at their spawn then i have no sympathy for your dirty maneuvers; hope you get legged early on!!

Edited by Mazzyplz, 08 June 2015 - 11:19 PM.

[Sarlic]

This is why i mostly dont bother to come back and join the game.

Always lame e-penises who are going for the easy kill.

[PhoenixFire55]

lol ... and you think those discons will show mercy to you in same situation? Yeah, right ...

This is war. You kill or you get killed, simple.

[Ace Selin]

KIll them, they may not ever come back.

[Chuck Jager]

I loose more games to our "scouts" running around in the back of the enemy to only get killed or never add any valuable info or damage to our main battle. The worst is when they light up a DC and the whole unit makes a U turn for it. "Removing a threat" and "scouting" are code for pad my e-ping.

[MeiSooHaityu]

I personally don't have a problem attacking and killing a disconnect if I come across them. Yes it is a bit crappy, but this is war, and war is hell .

Why leave an enemy mech healthy so that he could reconnect late game fully healthy when the remaining combatants (who have been there from the start) are beat up, cored, and relatively easy pickings for a healthy and fully loaded mech? Often matches don't come down to this, but some do. Why take the gamble? It stinks to be the disco, but that's just the breaks.

Nope, if I see an enemy mech (disconnect or not), he's getting destroyed.

Edited by MeiSooHaityu, 09 June 2015 - 04:24 AM.

[HoundOfCullan]

I hope I play you all the time then. I'm going to run into you base and DC. I'll win every game.

[Raggedyman]

Fenrisulvyn, on 08 June 2015 - 07:04 PM, said:

So I am no longer going to vulture disconnects. You can join me or not, but its simply not sporting and just pisses off a player base that we need to increase, not run off.

DCs suck, but they are also a part of the game and I would really rather not present people with a 'get out of jail free' card or promote another utter-cobblers 'ooooh, that way you play just isn't sporting, even though it's fully within the rules of the game'.

Besides, if I've managed to get past the active enemy we are too far into the game for the DC to actually have any major impact on things and if I DC the last thing I want to have happen is log back in just to have a circle of reds all go "finally, where were you???" as they core me out in 1 second.

[Catra Lanis]

It's kind of you OP but if someone ragequit permanently because of that chances are pretty good he wasn't going to stick around anyway.

[JC Daxion]

If your the kinda person that Rages because you were killed when DC.. they might want to play offline only games..

Yea, it is annoying when you DC as the mission launches and you come back with in the two mins to find a dead mech.. But come on, let's be serious.. you did nothing that match, click quit, and load up a new mech, or just watch the match and help your team by talking them through it.


For every 1 guy that comes back from a DC, there are 100 that don't.. I can't even count the amount of matches i have had to hunt the last DC guy, or told the team where our DC was.. On the flip side.. in a night i might see 2-4 actually log back in from a DC.

this entire thing is a non-issue.. and like the other guy said, if this makes you rage.. chances are you are going to rage about way more things than this. Game is better off with people that don't rage about the small stuff..

[MechWarrior3671771]

"loose more games to our "scouts" running around in the back of the enemy... something something e-ping"

Read the OP. Its Conquest only. One of the few modes where scouts have a legit reason to get deep behind enemy lines early in the game.

[MechWarrior3671771]

"I'm going to run into your base and DC"

This is just for DCs at spawn, ya goof

[Sgt Minuteman]

What I would like to see is at the end of a match if there is one mech left, the clanners all stop and challenge the remaining enemy mech to one on one Zellbrigen style combat for an honorable death. It was just cool to experience that kind of code in an online game back in the day...I always was IS, but it made me have a little more respect for the Clan way of life. Clan players need to start following the codes of conducts to develpe a "culture ' in MWO.

For those who do not know what i refer to: Zellbrigen Zellbrigen is the body of rules governing duels. These rules dictate that such actions are on-on-one engagements, and that any warriors not immediately challenged should stay out of the battle until an opponent is free.
Once a Clan warrior engages a foe, no other warriors on his side may target that foe, even if it means allowing the death of the Clan warrior. Interfering in a duel by attacking a foe that is already engaged constitutes a major breach of honor, usually resulting in loss of rank, and also opens the battle to a melee. Some rules are:

• Challenges are refused by not returning fire.
  
• ​Warriors may not disengage from an challenge until one unit or the other has been destroyed or accepted hegira.
  
• ​ Warriors may choose to engage multiple Warriors, provided their targets have not already accepted a challenge from another Warrior.
  
• Units which have shut down as a result of overheating are fair targets unless they are prone as the result of a failed PSR or have surrendered.
  
• Physical attacks are forbidden against warriors unless no other direct fire weapons are operational.

Edited by Sgt Minuteman, 09 June 2015 - 06:35 AM.

[Mazzyplz]

Sgt Minuteman, on 09 June 2015 - 06:20 AM, said:

What I would like to see is at the end of a match if there is one mech left, the clanners all stop and challenge the remaining IS to one on one combat for an honorable death. It was just cool to experience that kind of code in an online game back in the day...I always was IS, but it made me have a little more respect for the Clan way of life.

did that really happen? what game was it

[Saint Scarlett Johan]

If I DC out of a solo match, I just grab another mech and launch into another match. Every time I finally reconnect to a solo, I'm missing my head, so I don't bother anymore.

Group is different because some buddies will guard my mech as a come back in.

[Bilbo]

You generally have to kill them to finish the game in a timely manner anyway. Might as well do it sooner rather than later. I've come back from DC to spectator mode before and it's really not that big a deal. I kind of expect to be dead considering the time it takes to get logged in and rejoin the match.

[Piney II]

It's funny to watch someone work over the easy kill DC while they ignore the live mechs........even more humorous when they killed doing it.

[Bilbo]

Piney, on 09 June 2015 - 07:03 AM, said:

It's funny to watch someone work over the easy kill DC while they ignore the live mechs........even more humorous when they killed doing it.

If they spend so much time farming damage they deserve to be killed. More important things to do than piecemeal a DC.

[JoJoxy]

Smith Gibson, on 08 June 2015 - 07:26 PM, said:

Remember it's not the players fault he disconnected. It's PGI's poor programming.

We just have to decide which is more important, emphasizing the problem by killing disconnects until PGI fixes it.

or,

Soothing the problem by refusing to kill disconnects so we don't lose even more players to rage quitting but then have PGI ignore the problem as not bad enough to be worth fixing.

Yeah its most definately PGI's fault that my sucky ISP and/or router decide every few hours it is time to reconnect my DSL.
Packetloss in networks PGI has no control over is also their fault of course.

Don't get me wrong, the occasional CTD might be due to bugs in MWO. But there are other variables at play, like the myriad of hardware and driver combinations out there.