Sure it's silly, a company as big as R* should have never made this mistake but some dude figuring it out AND R* implementing the fix AND him getting rewarded...if only it was like this all the time
There is a good writeup of the details
here.
TLDR; Parsing of some JSON data for in-game purchases. The parsing code is flawed in design and the execution time grows exponentially with increasing data sizes. When the developer wrote this, it ran fast with the test data, then gradually got slower over time with more data, but only significantly when the data got really big. That's the thing when you have something with exponential growth that starts very slowly, it takes a while before the problem reveals itself.
I've fixed problems in legacy projects myself that had the exact same type of problem; string parsing with exponential run time.
Impressive done by the fan/moddet. But I also think that it is a good move from Rockstar to recconice the games fans mods that can improve the game.
Maybe other developers can learn from this. Work together with the community.
Yes, there are really only benefits from embracing the fan base. They will provide a lot of QA, improvements and advertisement for the product, all for free!
I mean there has been a lot of bug released games over the years and I have had my fair share of games not running properly or crashing. So I know only to good how annoying and depressing a game can be.
If these companies simply stopped trying to obfuscate/"encrypt" the compiled binaries, removed anti-cheating bloatware and various anti-piracy measurements, numerous games would probably gain a lot of performance immediately (especially loading times), and probably eliminate of a lot of obscure bugs too.
Beyond that, game engines are generally too bloated. And there is no good reason why loading times should be several minutes on a modern CPU and even a SATA SSD. Even a single thread on a mid-range CPU will be able to decompress gigabytes of textures in a matter of seconds, if it takes significantly more than that, then the CPU is probably busy in a
"speed-up loop".