The player movement and the bouncier rims would be attributed to the "gameplay feeling different" after so many patches and updates.
Those are 2 of the telltale signs that we see damn near every single year. The devs aren't writing code to make those changes, they're more so "symptoms" of the over arching issue. That can be the nature of an API/engine/brain/whatever term you want to use.
You write code for ------------->[this]
and it unintentionally affects [that]<------------------
It's been that way since patches were a thing (for NBA 2K). Previously, we'd just have to deal with whatever came in the box, until next year.
You'd have to write in cheques and safeguards to prevent those same issues. But in code, sometimes the safeguard you write needs to be source (original) code in the program, which would mean re-writing NBA 2K's codebase to include those safeguards to make multiple patches not produce these issues....but on a yearly release schedule -- that's nearly impossible.

Comment