Godzilla & Emrick
Godzilla Godzilla
Hey Emrick, if you were to build a game with a giant monster, what would you focus on first—making my size feel realistic, or figuring out the best way to let players defend a city from a headbutt?
Emrick Emrick
First get the defense mechanic working—how the city reacts, how the player moves, the hit‑scoring, the feedback loop. Once you can prove the core fight feels solid, you can crank up the monster’s dimensions and tweak the physics until it looks and feels massive enough without breaking the gameplay. The size should never outshine the experience; the experience should never get lost in the size.
Godzilla Godzilla
Got it, Emrick. Start with the bite, then grow from there. If the hit feels good, the rest will follow. Keep the city moving, and the monster’ll roar in rhythm.
Emrick Emrick
Got it, let’s nail that bite first. Once the impact feels right, the rest will follow—city crumbling, monster growling, everything just syncs up. Ready to code the first test?
Godzilla Godzilla
Yeah, let’s crack the first bite. Hit it hard, feel the crunch, then roll the city down. I’m ready when you are.
Emrick Emrick
Alright, first step—let's set up the collision bounds for the bite and a quick test to see the force curve. Once we hit that sweet spot, we can trigger the city collapse logic. Grab your code editor, and let’s get the crunch going.We have complied.First, set up the bite collider and a simple force test. Once that feels solid, hook it up to the city damage system and see the collapse in action. Let’s fire up the editor.