This was in a much simpler time, before there was any black market for infinite (re)sale of cheating tools. That specific ‘security method’ is also long-since ‘bypassed’, and same goes for any updates to it.
It, again, also serves to give people a ‘false sense of security’, as would this. It only hasn’t been removed because it would invalidate existing on-disk cache, and make existing servers incompatible with updated clients, both of which are not a viable choice to make.
The point is, as said above, that at the time it was deemed a sensible option. The landscape changed, and now neither are sensible, but removing the old cache obfuscation is not viable.
Then go to these ‘comparable modifications’ if they’re so comparable and they serve your needs better.
Nobody even said this is ‘impossible’, we could easily do this, but a) the way you suggested is, suffice it to say, completely retarded (convoluted, unneeded, the brainchild of a person with worms for brains perhaps - it sounds an awful lot like a half-solution some other ‘competitor’ attempts would have implemented), and b) we won’t, as it would serve no goal other than lead to a false sense of security, and only lead to chances of regressions, which lead to idiots crying ‘stuff is broken’; bypasses, which lead to idiots crying ‘omg fix bypass’; it’d take time, which already is highly scarce; all in all there’s more downsides to implementing any such change (where we still won’t ‘lol restrict devtools fully’ based on a server variable, that’s just dumb as shit, at best we’d just disable nui:// from fetching assets from resources without ui_page if that’s not a thing yet as this is how random ‘dumpers’ work, but even that’d break compatibility perhaps with some resource on some private server of some streamer in a country where nobody speaks English).
As above, the only reason ‘we encrypt the cache/rpfs’ is a decision made based on the landscape four years ago, that would be hard to revert compatibly. There’s a gazillion parsers that bypass this as well as allowing downloading directly from a joined server, that would also be impossible to ‘fix’ compatibly, as well as lead to the same risk of regressions, continued bypasses and time-wasting as your precious feature would.
In the end, no matter what is done, nobody will be happy.
Again, let’s reiterate the scenarios for your feature:
- We implement this, you’re happy, but it regresses for a week, users will be crying in our fucking faces for a week while we hurry to figure out what went wrong but don’t have any repro as it only breaks on some rando-shit servers that we don’t have access to with the owners and players only being able to write in moon runes.
- We implement this, it works, you’re happy, but there’s a bypass, and people (maybe even you) will cry that we should add more anticheat for this bypass, which we might, but it regresses and leads to daily crying of ‘omg false baaaaaaan cfx we will sue you! you suck so hard’ without any way to reproduce.
- We don’t do this, and only you and the community you sent to vote-brigade this issue complain, but we’re saved from the risk of having crying from everyone else except every few weeks this topic comes up and we can just say ‘nah, this is intentional’ and 90% of people asking just don’t ask again.
See, not changing anything is the ideal solution.