Engineering Under Threat - Open Letter etc
- Thread starter Gavin786
- Start date
No we don't.
It's because of seal clubbers that people resort to solo play. What the game needs is consensual PvP.
Set your flag to PvP - fair game.
No flag - only danger from NPCs.
I really enjoyed Freelancer. I don't recall the flight model being exceptional but two other games' did, Evochron and I-War I (and II). I still keep Evochron updated so I can enjoy its flight characteristics and build some stations.
There's a flag - you set it "on" when you click "open". No additional flags needed. Especially not "god" or "ghost" mode players flying around in open.
Seal clubbing is a non-issue in ED. First, given the size of the Galaxy, the chances of actually meeting a seal clubber is minuscule. Second, don't be a seal. Escaping is extremely easy. Third, if you cannot sleep because of the tiny chance of getting blown up by another player, there is a solo mode. EZ
I respectfully disagree.
My solution would preclude combat logging, and the chances of a random disconnection during a PvP battle is tiny. I, for one, never had one during 3000+ ingame hours, and I don't even have a very good Internet connection.
My connection does not make my instances laggy (it's not that bad), but I experience shadowrams much more often than other players I usually play with. This undoubtedly is a disadvantage for me, and I can recall several situations in which the random and unfair extra damage I suffered because of that eventually led to my meeting the rebuy screen. How is that more fair than having to rebuy my ship because the connection error made my game crash (which is an extremely unlikely situation)?
Thing is that it was my decision that the game is "PvPable" with my current connection. If I had experienced CTD's in every other instance, I surely would have decided that my connection was sadly not good enough to PvP in ED, simple as that.
Your solution is punitive, unprecedented, and regardless of your claims you can not guarantee the level of risk.
Ultimately, nope - your "solution" is nothing more than a punitive brain crash. No other on-line game imposes such an overly punitive solution either AFAIK.
[EDIT]I have a better idea - remove rebuy risk from PvP deaths (c/f GTA), I doubt FD will go for it but it would eliminate the alleged cause of combat logging.[/EDIT]
Last edited:
If you actually had read the comment you were replying to, you'd know that there is such a game, and it's ED itself, which can punish you through more frequent shadowrams, for instance. Or RNG based canopy loss, although that's at least completely random.
Nope - your logic is fundamentally flawed in reasoning and ultimately illogical and false.
I will re-iterate my earlier edit...
[EDIT]I have a better idea - remove rebuy risk from PvP deaths (c/f GTA), I doubt FD will go for it but it would eliminate the alleged cause of combat logging.[/EDIT]
Where was the logical flaw in my reasoning? I'm genuinely curious, because so far you've failed to point out a single logical flaw in it, just saying.
BTW I wouldn't mind if they removed the rebuy risk from PvP deaths (although I know of some people who would, like Morbad, for instance, and I can understand their reasoning against removing consequences), but speaking of logic, your solution wouldn't preclude combat logging like mine. Fair enough, there would be no reason to combat log, but people would still do it nonetheless.
There is no rationale to support insta-death on connection termination regardless of the circumstances - it does not happen in any other game with persistent assets and does not happen in ED currently - your claim is ultimately fallacious and the line of argument is moot.
My solution would remove the only alleged reason for it - combat logging by FD's definition is deliberate early termination of game connection to avoid rebuy - remove the rebuy and combat logging would no longer be a thing.
Ultimately, there is no legitimate reason to incur insta-death on connection termination regardless of the cause nor the circumstances.
You appear to be missing the 'root' of the argument - by no longer being in a conflict situation (be it by Combat Logging or just a dropped connection) a 'kill' has been stolen, and that is almost as painful as being kicked in the nether regions to some combat fans
Look, saying "your claim is fallacious" does not make it so.
There is a rationale to support insta-death on connection termination in order to avoid death in a multiplayer game: it's cheating. Whether it's happening in other games or not is utterly irrelevant.
Currently the game does punish you for having a worse than optimal connection: it can result in extra damage, which can lead to death and loss of credits.
Claiming that removing the rebuy would make combat logging nonexistent is false. It would be less omnipresent, I give you that, but some people would still do it either to keep their NPC pilot, or to annoy people, or just because why not.
Joy to all the fishes in the deep blue sea, joy to you and me.
There is always a bigger fish.
Time to take a moment to really appreciate the Gankers out there and lets have some gratitude.
They clean the ocean of the smaller, weaker fish, strengthening the whole, forcing everyone to get better. They provide an imperative critical role in the game ecology.
Lets make October 21 : Ganker Appreciation Day.
Lots of love to all our Gankers out there, keep up the great work.
Gavin786
Ummm, ok here's just a few of your previous quotes Cmdr, its kinda misleading tbh
![[PS4] Filthymick420](https://forums-cdn.zaonce.net/data/avatars/m/201/201444.jpg?1555738739){kind=avatar}
Not always. How much exploration data are you willing to give up to save face and not clog? But if you did choose to clog in an effort to save perhaps hundreds of millions in explo data that wouldn't be because of your ego, it would be because you did nothing to deserve losing all you hard work and efforts. And did what you had to do to protect your assets.
I'm not advocating for clogging to be accepted, but it shouldn't be misunderstood either
Here comes a hot take... the RESULT of engineering is fine. The path to get there is the issue. They need to lower how many possible mats there are, and make it so that after you unlock a mod, it can be purchased rather than re-engineering from the ground up every damn time.
All of my ships have some form of engineering, and the fun part is seeing which combinations of effects work well and which don’t. The fun is not in the gathering or sitting in the menu rolling for inconsistent advancement on the module.
if they made the system suck less, more people would use it
All of my ships have some form of engineering, and the fun part is seeing which combinations of effects work well and which don’t. The fun is not in the gathering or sitting in the menu rolling for inconsistent advancement on the module.
if they made the system suck less, more people would use it
Except there is no entitlement to a kill - this is not designed as a PvP gankfest type game, PvP kills are not worth anything of substance (over and above PvE kills), but that still does not change the simple fact that there is still no justification to penalise players who either have a game crash, system crash or some form of connection issue due to reasons outside of their control just because it happens to occur in a combat setting.You appear to be missing the 'root' of the argument - by no longer being in a conflict situation (be it by Combat Logging or just a dropped connection) a 'kill' has been stolen, and that is almost as painful as being kicked in the nether regions to some combat fans
FD have mostly ruled out "special" handling for PvP combat, and those that feel aggrieved by potentially a lost kill should report the incident and let FD judge whether the incident merits corrective action.
Last edited:
Not according to FD - their definition is the only one that matters.
[EDIT]The cause of forum complaints about clogging though seems to be entirely ego driven.[/EDIT]
Last edited:
Regardless, of the reasons - the point is the entire concept of insta-death on connection failure is too punitive because there are circumstances that can cause it that are outside of the individual's control.
Combat Logging as FD define it is subject to policing by FD and those that do it deliberately deserve any penalties FD feel are appropriate. Menu logging regardless of the circumstances is fair and reasonable - this has been re-iterated by FD a number of times.
This^^^
Being slightly rural in the UK... Windy day, stormy day, harvest time... Brown-outs, random power outages, the best in the last month being 4 power outages over 3 hours... Had I been playing and 'busy' I could have been accused of CLogging 4 times...
Would that have been true?
Exactly.
I find the claim that someone can play for 1000th of hours without getting a disconnect in combat highly dubious.
I can get 10 disconnects on one evening. I had 4 yesterday, 3... uhhh purple(?) Kraits an a yellow sidewinder I think (or maybe it was orange). The latter one during a pvp interdiction.
The number of crazy stuff, disconnects, blue tunneling, freezes, crashs, partly-disconnects (where some people can't see each other, while others can), mis-droppings(being interdicted and dropping in an empty instance, which is basicaly a disconnect), warping (where suddenly one ship moves 100km and can only be detected via wing beacon) I witnessed over the years could fill a book. And it definetly get much worse the more cmdrs are out there in a instance. And I know its not beacuse of my sh..y connecten (its so-so) beacuse I'm often on discord with other pilots and I know the experience the same problems.
I can deal with any number of gankers, no problem at all.
But if a disconnect would mean ship destruction, I'll perma-migrate to solo.