So, are you guys Trillionaires yet?
- Thread starter Achibot
- Start date
I'd expect so, yeah. It'll have to be manual of course. You really have to pity the low level scrub working through that crap to figure out the NPC bonuses etc. #RealHeroes
Buy something with it, pronto. I'm thinking an A rated Corvette. Harder to take a ship from you than rolling back your bank account!
lol, yes, indeed, spend it all, quickly, lest it be taken away (ignore being 4 quintillion in the red, debt's fine if you can manage it because it's not like it'll affect rebuy! .. wait).
I like you, I really do, that's just evil.
Last edited:
What if you spend it all!!???
I've been looking for a few more imperial slaves for the mistress' sail barge, and I think you'll do nicely!
Real life database programmer here. No, it's not
To be fair I agree, when you're at the level of having to make manual database corrections then it's somewhat irrelevant what you have to remove. Assuming the query is made simple by credit amount alone, of course. I imagine it will still be a few days work for some young lad though, no real way to automate the actual correction.
What if you spend it all!!???
Most likely they would be left with a negative credit balance or debt of some kind that they would have to pay off. There is already debt mechanics in the game for when you need to pay a loan off for ship rebuys so it wouldn't be hard for them to remove the credits obtained from an obvious game error.
Something similar happened in Star Citizen when there was a bug for incorrectly low missile prices and players stockpiled hundreds of them, thinking that the worst that would happen is that the devs would simply take the missiles back. What CIG actually did was apply the correct prices retroactively to the purchases and suddenly players were millions of credit in debt. I'm sure they sorted it out in the end and just reversed the purchases but it was rather amusing and was a good cautionary tale about taking advantage of a situation that clearly wasn't intended.
Generally if something is an obvious game error there is a good chance it will be rolled back and this could easily put you at a disadvantage in some way. Even though taking advantage of the error might not considered an exploit there still needs to be some way to discourage players from taking advantage of obvious errors like this so some type of temporary inconvenience or setback would certainly be appropriate.
Oh brother. My huge CR balance is not even a rounding error to that!
Considering that FD was able to retroactively identify illegally modded modules and remove them up to a year after the Engineering exploit was used I have a new level of respect for what the devs can achieve by analysing the logs. In fact all they would need to do is look for any credit balance over a certain threshold and then analyze those specific accounts in more detail. It isn't generally possible to store more than about 35 billion worth of ships and that's assuming you're buying 35 fully-loaded Cutters at 1 billion credit cost each to fill all of your available ship storage slots. Essentially you would have no way to "launder" anything over 35 billion and the remainder would just be sitting as a massive credit balance in your account and be rather easy for the devs to locate.
Also, it's apparently a feature, not a bug, and the Space IRS will be a new powerplay faction in 2.4. They will deal with these issues in-game by auditing your credit balance to maintain the appropriate level of immersion with the new emergent storyline.
Spoiler Alert: Apparently 2.4 "The Return" actually referrs to your Federal tax return, and if you don't file it correctly, the Thargoids reposses everything you own.
Last edited:
Nah, it would have been more like you described in your second sentence, a query of all modules (ie database entries) that exceed the current maximums (including maximum possible side effect bonus). In point of fact I believe people got away with certain cheat mods that happened not to exceed those parameters.
You also have the emerging reality that keeping logs for that long would generally be inadvisable under Data Protection rules. On top of being a massive storage burden. Maybe they stretch that far back, but the logistics and general best practice would suggest it's unlikely.
Apparently they keep the logs for quite sometime (at least a year) since they were able to identify the Engineering exploit over at least a one year period. Whether mission logs are kept to the same level of detail as Engineering logs isn't clear but they are obviously going to have to do something about it. There is no way they are letting players keep hundreds of trillions of credits (or whatever they bought using those credits before the bug was identified). If necessary they could even rollback an individual player's account to just prior to the 2.4 launch if they had no other option. We know that they routinely backup player account data so that would be rather easy for them to do. I'm sure there would be the occasional player who would complain about their legitimate "progress" that would be lost with a rollback but that just teaches them not to accept a ridiculous 200 trillion credit mission and think there won't be any consequences (much like the consequences for exploiting the Engineering exploit if you also lost legitimately modded modules).
Last edited:
Nah all they have to do is identify which missions had crazy payouts and join on the commanders who took those mission rewards. Data protection rules don't apply to proprietary data, which this is, they can keep logs of everything they want. It really doesn't take much storage space on a database to do that.
The logging system is transactional, as evidenced from logs kept on client machines, meaning that all client-server interactions are logged for some time. My point was that referencing them would have been unnecessary since, by definition, cheated mods were mods that exceeded the potential of non-cheated mods. All that was necessary was to search the current database for such mods, a fairly simple query to craft. Mods that satisfied that query would be deleted, presumably to be replaced by default mods to maintain database integrity. That is so much simpler than creating a script to interrogate terrabytes of log files for the same information, even assuming they are inclined to keep such detailed logs over such a duration, which is unlikely.
That's certainly wrong. Data protection applies to all data which is "personally identifiable". All data is proprietary, by definition, to the person/business entity that created it. You create it, you own it. But you are still held to a legal standard as to when it is appropriate to keep, at what detail and for how long. The more anonymous data is the less it is restricted. This is literally a huge part of my job and in 5 years it's a job that 4 or 5 people will be doing in my place, such is the direction the legislative environment is tracking, at least in Europe.
That applies to consumer data, not proprietary internal data. You do not own your commander's data, FD does. Data about what you do in game is not data about you, you don't own that they do. Just because it can be tied to an account that's "personally identifiable" isn't the issue, you make it sound like they'd have to delete our accounts after a certain point because they can be tied to persons.