following FD's rules apparently lmaoAt this point the logger should really be asking themselves:
"What am I actually even doing in open?"
following FD's rules apparently lmaoAt this point the logger should really be asking themselves:
"What am I actually even doing in open?"
At this point the logger should really be asking themselves:
"What am I actually even doing in open?"
Sometimes twice over:They are deliberately disrupting the gameplay of others with the intent of causing negative feelings by blatantly cheating.
AKA griefing.
At this point the logger should really be asking themselves:
"What am I actually even doing in open?"
Interdiction and PvP in general is not expressly an issue. Some PvEers may resent the lack of an Open PvE mode and/or the membership limits of Private Groups but that is another matter entirely.So is there a good form of interdiction, or is everything bad?
FD have essentially admitted that the current excesses of shield booster stacking was unintentional, therefore by their own book of definitions utilisation of it is an exploit and therefore cheating and an EULA breech by their own rule book.
Why do that when FD allow you to "menu log" in combat? lolBest possible way to avoid any kind of possible setbacks, or threat, is instead of clicking 'play', click the 'x' button and watch TV. But nothing too scary.
But then there's always the power button on your remote.![]()
Why do that when FD allow you to "menu log" in combat? lol
You make a good point, now if only all menu loggers would follow that advice!But menu logging requires like, 3-4 button pressed and waiting 15 seconds...!
If you don't click play, then you don't even need to wait.
Logic.
CMDR Cosmic Spacehead
Combat Logging (as FD define it) is not justifiable regardless of the mode you are in, Menu Logging on the other hand is fair and reasonable.I don't agree with combat logging in open because you consent to PvP the moment you click Open Play.
The problem with that stance is the Mobius groups already have hit the membership limits of Private Groups many times over and Solo does not grant the option of co-operative multi-player gameplay.If you don't want any risk of PvP, play in Solo or join Mobius.
I don't necessarily disagree with this principle; However, I think the general idea will never be done because some in the community seem to fear that Open mode would be abandoned sufficiently to declare it dead. FD could theoretically crack down harder on certain PvP behaviour patterns but doing so in a fair and reasonable manner is littered with complications. The 3.0 C&P/C&C changes were a good start and did so in an even handed way. There are other things that could be done in addition to that but whatever they choose to do there will always be some that object to it regardless.Personally, I think Frontier should have made a separate PvE server, and in that, you can choose to engage in PvP only if both of you consent to it, kind of like Borderlands where you can challenge a squad member to a fight and they can either accept or decline.
Combat Logging (as FD define it) is not justifiable regardless of the mode you are in, Menu Logging on the other hand is fair and reasonable.
Joining Open is not however granting a carte blanche consent to any and all PvP behaviours. FD created the Open environment obviously in the hope that people in general would not treat it like a PvP arena, what has transpired since release has shown that some PvPers fail to respect that hope/intent. The whole concept was doomed from the start, the moment you open the Pandora's box of allowing random PvP there will inevitably be some that push the boundaries of what people in general will tolerate.
The problem with that stance is the Mobius groups already have hit the membership limits many times over and Solo does not grant the option of co-operative multi-player gameplay.
I don't necessarily disagree with this principle; However, I think the general idea will never be done because some in the community seem to fear that Open mode would be abandoned sufficiently to declare it dead. FD could theoretically crack down harder on certain PvP behaviour patterns but doing so in a fair and reasonable manner is littered with complications. The 3.0 C&P/C&C changes were a good start and did so in an even handed way. There are other things that could be done in addition to that but whatever they choose to do there will always be some that object to it regardless.
Actually, it is you that is essentially wrong...menu logging and randomly killing players are both perfectly acceptable methods of playing the game.
FD say so.
For clarity's sake, this is, verbatim what it says in the link you provided:
"This is a quick update to let you guys know what we’re looking at regarding the issue of “combat logging”.
For clarity’s sake, “combat logging” is when a Commander ungracefully exits the game (e.g. using ALT + F4 then shutting down the game process) to avoid defeat, destruction and damage.
Commanders might use this exploit the moment they are interdicted or the moment before they are about to be destroyed.
Although this is flagged primarily as a multiplayer concern, the issues (and solutions) apply equally to the single player game.
First things first: we do consider this an undesirable exploit. It’s not “part of the game”.
Because we don’t have an all powerful server running the moment-to-moment game play simulation, there is no infallible arbiter to take control of a player’s ship when they ungracefully exit.
So what we’re doing is logging telemetry that will help us detect when this exploit is explicitly being used.
Right now, all we’re doing (and have already started doing) is looking at and implementing methods of collecting and analysing data.
At some point, however, we will start to take action against Commanders using this exploit. I can only suggest that you should avoid using this exploit if you want to avoid any penalties issued for its use. I'll just repeat: please avoid combat logging - we're taking this issue very seriously.
On a related, but separate track, we’re looking at introducing benefits to Commanders that persevere and stick it out through dangerous encounters, as well as general credit costs and rewards balancing.
I’m not quite ready to talk about these in more detail just now. Obviously though, they can never counter the potential costs of ship destruction, but we want to look at a range of disincentives and incentives both to counter this issue.
I hope this helps clarify our position a little."
__________________________________________________________________________________________________________________________________________________
Go through that word for word and show me expressly where he states that logging out via the menu in combat to, as he words it: "to avoid defeat, destruction and damage." DOES NOT COUNT.
Joining Open is not however granting a carte blanche consent to any and all PvP behaviours. FD created the Open environment obviously in the hope that people in general would not treat it like a PvP arena, what has transpired since release has shown that some PvPers fail to respect that hope/intent. The whole concept was doomed from the start, the moment you open the Pandora's box of allowing random PvP there will inevitably be some that push the boundaries of what people in general will tolerate.
The problem with that stance is the Mobius groups already have hit the membership limits of Private Groups many times over and Solo does not grant the option of co-operative multi-player gameplay.
I don't necessarily disagree with this principle; However, I think the general idea will never be done because some in the community seem to fear that Open mode would be abandoned sufficiently to declare it dead. FD could theoretically crack down harder on certain PvP behaviour patterns but doing so in a fair and reasonable manner is littered with complications. The 3.0 C&P/C&C changes were a good start and did so in an even handed way. There are other things that could be done in addition to that but whatever they choose to do there will always be some that object to it regardless.