The main difference in this situation is that if someone starts to charge FSD for high-wake, they can still have malfunctions that cause them to restart the high-wake; this has happened to me multiple times in PvP situations. The log-out timer saves you from any potential malfunctions.
Food for Thought : Possible Solution to Combat Logging & Stacking of Missions?
- Thread starter Cmdr Eran Mintor
- Start date
The main difference in this situation is that if someone starts to charge FSD for high-wake, they can still have malfunctions that cause them to restart the high-wake; this has happened to me multiple times in PvP situations. The log-out timer saves you from any potential malfunctions.
Robert Maynard
Volunteer Moderator
Presumably that would only be for situations where the player was under-fire from another player?
Don't see why it matters what you was under fire from ... people cheating death (PvE) are just as bad.
Robert Maynard
Volunteer Moderator
Indeed - however, why impose a mode restriction when no other players were involved?
You don't know the circumstances behind the combat scenario - I can think of a few that involve other players but you come under fire by an NPC. IMO if something like this was to be implemented it would have to be a force to solo (With appropriate message when you log on to explain why - that's the important bit)
Edit:
If they were with friends, for example, and are locked out for 15 mins it might make them think twice especially if they want to rejoin their friends. The problem here is not just limited to PvP-Combat exploiters but people doing it in general. I take deaths on the chin and wipe my char as a result
Last edited:
I'm sorry but this is an absolutely terrible idea in my opinion.
Let's take a look at yesterday. I was able to make it home from a trip and even found time to play for a couple of hours.
The first interruption was for dinner, obviously I log out for this. Only took ten minutes to eat but I'd still be waiting for 5 under your idea.
Next was to take a phone call on the land line. I log out for these as they may go on for some time but it was only a quick call so I'd have to wait for 10 minutes with your idea.
Then a friend popped round to see if he could borrow a drill. Logged out of course, took 5 mins to get him sorted but I'd still be waiting 10 minutes with your idea.
Out of the two hours I had 25 minutes of them would of been spent waiting if your idea was to be used. So no, I do not like your idea at all, it would be a huge reason to just never play the game again.
Last edited:
15 minutes ? No.. here is not london.. isp sometimes sucks n internet can go crazy dc like shiz..
I play solo for few hours n then my friend text me to help him in group mode,.. 15 mins wait? No.. he can find someone else to help him..
Or someone invite me to do some crazy canyon race in open, .. 15 mins wait..
You really wanna punish mode switching for combat logging? Or you just jelly for some 8 years old kid flying corvette?
This is bad idea, many players will get penalized for other things than combat logging..
I play solo for few hours n then my friend text me to help him in group mode,.. 15 mins wait? No.. he can find someone else to help him..
Or someone invite me to do some crazy canyon race in open, .. 15 mins wait..
You really wanna punish mode switching for combat logging? Or you just jelly for some 8 years old kid flying corvette?
This is bad idea, many players will get penalized for other things than combat logging..
Another thread on CL with another suggestion that doesn't work
I am sure it's been mentioned by now, but it's this simple:
-If you want to impose this log-in timer to every instance of timer logout or connection dropping there will be a hell of a lot of ticked off players whose router had a short fit or something
-If you want to impose it only on people that use the 15 sec timer, you aren't even close to stopping combat logging. People will still use alt + F4, or task manager, etc. etc., to quit the game. No-one combat logs using the 15 sec timer.
Sorry bud!
I am sure it's been mentioned by now, but it's this simple:
-If you want to impose this log-in timer to every instance of timer logout or connection dropping there will be a hell of a lot of ticked off players whose router had a short fit or something
-If you want to impose it only on people that use the 15 sec timer, you aren't even close to stopping combat logging. People will still use alt + F4, or task manager, etc. etc., to quit the game. No-one combat logs using the 15 sec timer.
Sorry bud!
Last edited:
Robert Maynard
Volunteer Moderator
You don't know the circumstances behind the combat scenario - I can think of a few that involve other players but you come under fire by an NPC. IMO if something like this was to be implemented it would have to be a force to solo (With appropriate message when you log on to explain why - that's the important bit)
Edit:
If they were with friends, for example, and are locked out for 15 mins it might make them think twice especially if they want to rejoin their friends. The problem here is not just limited to PvP-Combat exploiters but people doing it in general. I take deaths on the chin and wipe my char as a result
While the circumstances behind the combat scenario can only be guessed at, the game "knows" whether there were any other players in the instance - that was my point.
A more fundamental issue is present: what is being proposed is to ban players to Solo for using a game feature that Frontier themselves included in the game.
I don't think you read/understood the suggestion. It has to do with the combat timer so unless all the times you mentioned were in the middle of combat you would've been fine. Even if it was, the 15 minute time was a general idea. It could be shortened to something more suitable like 5-10 minutes. I hope you read the whole thread.
- - - - - Additional Content Posted / Auto Merge - - - - -
Again this has to do with combat timer, not logging to menu when docked or not involved in combat. Please be sure to read the whole thing.
- - - - - Additional Content Posted / Auto Merge - - - - -
Another thread on CL with another suggestion that doesn't work
I am sure it's been mentioned by now, but it's this simple:
-If you want to impose this log-in timer to every instance of timer logout or connection dropping there will be a hell of a lot of ticked off players whose router had a short fit or something
-If you want to impose it only on people that use the 15 sec timer, you aren't even close to stopping combat logging. People will still use alt + F4, or task manager, etc. etc., to quit the game. No-one combat logs using the 15 sec timer.
Sorry bud!
Has nothing to do with connection drops or alt+f4 (alt f4 is illegal by FDev). Seems a lot of people are failing to read.
Last edited:
It's got everything to do with this? I am reading perfectly well.
People combat log using alt F4. Or task manager. Anyone stupid enough to combat log by flying in a straight line for 15 seconds while the timer runs down deserves the ruin their ship encounters.
If you want to penalise "sudden" drops in connection, you're also penalising those who have legit connection drops. I have them regularly, and often not at my end. Sometimes the game just goes "nah bud" and kicks me to menu. If I have a 15 min timer when that happens each time, Elite would get uninstalled.
Killing another player it's not "griefing". We have ships and weapons, and i choose to use them. If you don't want to use the weapons against another commander it's your choice not mine. It's like you told some FPS player it's forbidden to kill another players
PS: i really love FPS games and i play ED like very big FPS game with space ships.
Should a player disconnect - let the victor decide his fate.
FD already have loser's save, FD servers asks what the victor did to the vanquished then applies it to his save (death for example). Much simpler. No more combat logging, only pain.
FD already have loser's save, FD servers asks what the victor did to the vanquished then applies it to his save (death for example). Much simpler. No more combat logging, only pain.
How many uninstalled diablo III or any other MMO where DC in combat likely to be cause of death?
Last edited:
Eh? Not sure what you mean. I'm pointing out that if you introduce a 15 min timer until you can log in every time you have a legit connection drop I wouldn't play the game.
Asking the victor what happened...really? Sounds like looking after a kindergarten more than a bunch of gamers
"So CMDR Brian...tell me what he was doing unfairly. Do we need to send him to the naughty station?"Edit: Maximum kudos to ED if they introduce a Naughty Station or Naughty System.
Last edited:
Do not think that 15min timer would be a solution. I defined simpler one above. Simpler one = right one.
You failed to understand that "asking" means - query to victor's client.
Last edited:
Saying ''Serious?'' doesn't make your point any more valid. And yes you got a phone call wrong number now wait 15 minutes. Play something else or watch something else, maybe play with that kid of yours.
Yes I read the entire thread. In my post I mentioned I was only able to play for two hours. As I knew there would be interruptions I played in solo mode. The second time I had to log out I was in combat - but RL is more important than the game and I also knew the risk of leaving the ship effectively prone in combat. Thankfully the AI is so poor right now my armored MK3 was able to survive.
Also a note: Alt+F4 is not illegal, it is a condition in a contract from a company that is very questionable due to the contract we already have with Microsoft for operating the Windows OS and all of it's features, one of which explicitly allows for a process to be stopped via this method. The EULA (contract) from Microsoft is not open to modification by a third party. There is absolutely no law covering this only a of contracts - hence it is not illegal.
They may put something in game but that doesn't mean it has to stay. Frontier included missiles at the start - now look at them.
Fact remains - bypassing death (by means of using 15s and/or exploit Alt-F4) should be discouraged. The obvious way it so put people in solo so they can't affect others by their game choices.
Uhm...I was kinda making the same point about the 15 min timer not working...
Yeah, I am failing to understand your proposal. But tbh bud, it's because you're not being completely clear.
1st part - I can disconnect you from my client .. then I choose to kill you
Remember : anything on the client side can't be trusted and as there isn't an independent arbiter (P2P links not P2S) your suggestion won't work.2nd part - Diablo 3 keeps you in game for 10s. In hardcore - many deaths (permanent) In Path of Exile - instant disconnect on Alt-F4. Watched many "hardcore" streamers abuse that to the point I had to ask (and was banned for it) "why play hardcore if you're going to cheat death"