Just wondering if the assesment is based on the actual source code? I've done a bunch of local modding by decompiling the Assembly-CSharp, and the switch/goto statements looked like build/compiler optimizations. If so, I'd bet the actual source code is probably better.
In short: My answers were based on the decompiled aspect - although the whole goto/if/else/hash chaos is certainly due to compiler optimizations from (very highly likely switches)
Doesn't change the fact that it is still all shoved in a single function with a "giant" switch statement and additional code inside, which could've been handled VERY differently.
And yeah, the youtube aspect is likely exaggerated - and the actual souce will certainly look cleaner as it will obviously be a bit more readable than the whole goto/if/else chaos with hashes and whatnot.
It is a big point that
COULD be improved upon, but the dev seems content with it (for now) - I do bet however, if he does plan on adding a lot more (or ends up doing a lot more than planned even), it will cause issues as it will get more and more difficult to oversee it if it's a massive switch statement and once that point is reached, it will get even more difficult to change it up to be easier to expand upon. (The biggest caveat to it currently is that while knowing exactly how it's all setup, you can expand it, but once you want to change it up and it gets a bit too big, it'll feel like a massive chore)
Then again, the dev did a lot of improvements over the time IIRC and from the previous game.
So while it sounds harsh, the dev still does a great job and obviously the actual source looks a lot better yet (until he adds a bit too much, then it'll massively slow down more and more in terms of updates until it is addressed, if at all)
Though I have to add that my view is from several versions back, things MIGHT have changed by now too.