FDev, you just upset a *lot* of people.

Status
Thread Closed: Not open for further replies.
Still, never mind eh?

Its like the ED version of this:

cillitbang-logo.png
 
I'm glad the exploiters were punished. I'm even more glad that my 1 very high roll on my FSD was untouched. I spent 2 months grinding for level 5 materials and rolls. I hadn't even heard of the exploit at that time (for which I'm also glad, otherwise I might have been tempted).
 
Got to say that I was impressed enough by the action FD took that I bit the bullet and finally purchased the Horizons update just to show them some support. Kudos FD a thoughtful and balanced response to an embarassing episode.

I agree, I'm impressed and more than a little surprised that FDev finally grew a ball and took action against an exploit.
But I also agree with the RNGineer exploiters that its time FDev grew the other ball and took action against clog exploiters. They could start by shadow banning some of the people on here that are highly vocal about doing it
 
I know the OP has somewhat apologized for suggesting FDev were excessive in modification removal when they weren't, but if FD were to remove all engineering modifications where just one was done through using the exploit I'd be happy about that, it would be well deserved. I knew about the exploit for a good few weeks before it was publicised fully and then dealt with but I chose not to use it, felt like it would undermine all the hard work I'd put in before then for one thing, and I'm sure a lot of other players felt the same way, and still have their engineering efforts to show for it :p
 
Last edited:
I agree, I'm impressed and more than a little surprised that FDev finally grew a ball and took action against an exploit.
But I also agree with the RNGineer exploiters that its time FDev grew the other ball and took action against clog exploiters. They could start by shadow banning some of the people on here that are highly vocal about doing it

I think now FD have done this, now is as good a time as any to start clamping down on multiple exploits going forward Clogging included.... That said it will take work from FD to fix things their end. Crack train for instance is obvious exploit but the game makes it far too easy to do. I am no coder but FD manage to have a cooldown on base scans for firmware, maybe things like the above coukd work similar?
 
…They could start by shadow banning some of the people on here that are highly vocal about doing it

While I agree that actions against combat loggers are needed, I strongly disagree with your comment that FD should shadow ban players for comments on this forum.
In game punishment for in-game actions. Out of game punishment for out of game actions.

Promoting the use of an exploit should, if anything, result in a forum ban (timed). Personally I prefer an open and unrestricted discussion - no forum bans for participants with opinions I don't like.
 
I think now FD have done this, now is as good a time as any to start clamping down on multiple exploits going forward Clogging included.... That said it will take work from FD to fix things their end. Crack train for instance is obvious exploit but the game makes it far too easy to do. I am no coder but FD manage to have a cooldown on base scans for firmware, maybe things like the above coukd work similar?

Almost all these exploits are due to lack of persistence when re-logging or switching mode. I quite sure FD will address this in the upcoming 'core updates'.
 
While I agree that actions against combat loggers are needed, I strongly disagree with your comment that FD should shadow ban players for comments on this forum.
In game punishment for in-game actions. Out of game punishment for out of game actions.

Promoting the use of an exploit should, if anything, result in a forum ban (timed). Personally I prefer an open and unrestricted discussion - no forum bans for participants with opinions I don't like.

Let me rephrase it.

They could start by investigating and shadow banning some of the people on here that are highly vocal about doing it, unless they were just forum trolling, which I find very doubtful regarding a few that I cannot name in case of shaming.
 
I wasn't using this exploit, and I see no point of using it anyway (ED is largely a single player game with voluntary PvP anyway so you're really only cheating yourself).

The rolls had to be removed, but in my opinion there's no reason to be punitive about it.

I hope that removing all modules with the same ID wasn't to punish players, but because they didn't have data to do a more specific approach. Considering that they didn't just wipe all modules from such accounts suggests to me that they did look at the data and do their best to target only the exploited rolls the best they could.

ED devs, could you perhaps detail why you took the approach you did, perhaps detailing the data you had and why a more specific approach was not possible?
 
Let me rephrase it.

They could start by investigating and shadow banning some of the people on here that are highly vocal about doing it, unless they were just forum trolling, which I find very doubtful regarding a few that I cannot name in case of shaming.

There's often no link between CMDR and forum name that could be exploited to try and get the innocent banned.

What about menu logging, which is totally legit any clampdown on cable pulling and loggers are likely to just to switch to using the menu.
 
ED devs, could you perhaps detail why you took the approach you did, perhaps detailing the data you had and why a more specific approach was not possible?
I very much doubt you'll get a response to that request. FD don't want the cheaters to know what data they have and don't have.

But I disagree with you on the punitive bit. There's every reason to be punitive. The point is to make them think twice about cheating next time.

I hope FD keep tabs on some of the worst offenders. They may even learn of new exploits that way.
 
Last edited:
I wasn't using this exploit, and I see no point of using it anyway (ED is largely a single player game with voluntary PvP anyway so you're really only cheating yourself).

The rolls had to be removed, but in my opinion there's no reason to be punitive about it.

I hope that removing all modules with the same ID wasn't to punish players, but because they didn't have data to do a more specific approach. Considering that they didn't just wipe all modules from such accounts suggests to me that they did look at the data and do their best to target only the exploited rolls the best they could.

ED devs, could you perhaps detail why you took the approach you did, perhaps detailing the data you had and why a more specific approach was not possible?

It's been explained by FDEV, as I understand it they can identify blue prints that have been exploited but not the individual exploited module. So say you have five ships all with G5 dirty drives and you exploited one of them, they've reset all your G5 dirty drives on all ships including modules in storage. But left any other modules/drives alone. If you've exploited everything everything is reset, if you've exploited nothing nothing is reset.
 
Last edited:
There's often no link between CMDR and forum name that could be exploited to try and get the innocent banned.

What about menu logging, which is totally legit any clampdown on cable pulling and loggers are likely to just to switch to using the menu.

My views on menu logging have no bearing on it, FDev introduced it, its not classed as an exploit.
Lots don't use the menu log atm because its 15secs of vulnerability, which in may cases is enough.
 
Let me rephrase it.

They could start by investigating and shadow banning some of the people on here that are highly vocal about doing it, unless they were just forum trolling, which I find very doubtful regarding a few that I cannot name in case of shaming.

Don't agree with banning people because of what they say; only for what they do.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom