Scheduling is a perfect example of what he SHOULD be doing - its broken down to generic classes, defined when their gameobject is assembled in editor or instantiated from script. They have multiple classes for accuracy, and don't try to deal with more than they need to at the moment. And the reason the scheduling system is so good, is because it wasn't built by Alex. It was built by the refactor programmer he bailed on. This is a vision of what could have been, my friends.
Club system is a similar overhaul, just rebuild it so club members, bonuses, levels, and interactions are separate elements you assemble into a whole club. A few sanity wrappers solve all your issues around abilities being available at the wrong time, nobody has to have any special case logic for pc club member over npc club member, and if the club leader dies you can just promote internally and not have all your interactions hard fail, if you're design calls for infallable clubs. As it stands its special casing as usual.
Weapons, once again is special casing that needs to be ripped down. Right out the gate, kill the lovely bit of boolean hell to define weapon properties. Why bool? These would conflict. Use an enum and set it in editor.
A weapon has some set of attack type or weapon class that determines animations, which the code does do, but as stringouts for some reason. Any weird special behavior like flaming, dismemberment, etc should be other components on the weapon gameobject, not an amalgamation. The parent weapon should ask its children to do anything they need to do during actions such as brandish, murder, etc and off you go, dynamic stackables without shit like this.
Stuff like suspicious items should be broken out into a component too, we see this duplicated all over the place, when a character who see's yanchan should just check "is anything on this character or a child of this character suspicious" by either asking the parent or checking the hierarchy itself. No piles of special case.
There's really no excuse to not be using object oriented design like this, where specific concepts, actions and behaviors are their own piece, with complex things like students built of many smaller blocks, even if you didn't know/weren't comfortable with the Unity Component based design approach (Which is just a visual builder version of object oriented design anyway). Makes prototyping and upgrading so much easier too, since you can just build a quick object script and slap it on as a new component and see if it behaves in a fun way.
