I have no idea, I don't work on the game. The fact is, you don't know either. There could be any number of reasons that made sense at the time, that actually still make sense now despite the issues, or that were always stupid. The game might be far better today if they had designed it a different way. But we don't know any of this. What I do know is that when I inherit people's code and have to maintain it, they've often made decisions that seem to be incredibly stupid and harm performance in a variety of ways. Sometimes, it's as simple as that and they can be fixed. Other times, it becomes clear that there was a method behind the madness and I'm stuck with it. Still other times, I "fix" things assuming I know better, and end up having to fix the catastrophic errors I just introduced due to not fully understanding every aspect of the code. I've learned not to do that lightly.
I'm not saying you're wrong. I'm saying you can't possibly be certain that you're right, yet you're acting like your word is gospel.



Reply With Quote


