The Path of the Game Dev — Day 18

Saving progress…

— —

Just another day slogging through this boss, but I think I’ve gotten through the worst. I worked primarily on getting the boss to actually cycle through its attacks. Yet another thing I thought to be simple but actually computer breaking if you get it wrong.

I made a lot of mistakes early on in the day (and what carried over from yesterday). I had a lot of problems like starting coroutines when they shouldn’t be starting, not using enums when beneficial, and forgetting to put colliders and rigid bodies on some prefabs. When the boss was spawning infinite lasers I freaked out and stopped Unity before it crashed. Then I went to work trying to figure out why.

(Side note: don’t put coroutines in Update, kids)

At first I thought: maybe it’s because I haven’t been writing it all down? But no, that wasn’t right. It was all there in pseudo-code. I rewatched the GameDevHQ videos on enums and that brought some clarity back but, as expected, didn’t solve everything. Trial and error with a handful of Google research it was, then.

A lot of today was running the game, getting to a certain point, and errors popping up. So while debugging is a part of the process, I often found it a challenge to get through when I didn’t know what the cause of the problem was. When there were no squiggly red lines in Visual Studio, what was I supposed to do? As someone completely new to C# who knows the bare minimum of HTML, I still struggle with the terminology and trying to decrypt error codes can take as much time as trying to debug them.

Let’s recap everything from the Phase 2 checklist:

  • New Enemy Movement — check
  • Player Ammo — check
  • Wave System — check
  • Negative Pickup — check
  • New Enemy Type — check
  • Balanced Spawning — check
  • Enemy Shields — check
  • Aggressive Enemy Type — check
  • Smart Enemy — check
  • Enemy Pickups — check
  • Pickup Collect — check
  • Enemy Avoid Shot — check
  • Homing Projectile — check
  • Boss AI — almost done!
Just a bit of the boss

Soon. Soon it shall be done.

Biggest takeaways from the day: Sometimes you don’t get it. Sometimes you don’t get it for a long time. Sometimes you don’t get it and you mess with it and it works out.

— —

Progress saved!

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The New Photos Picker in iOS 14 -Part 2

Let It Crash: Creating an Example Supervisor in Elixir Using OTP

Reverse Geocode a Location in C/C++

Introducing Snorkel, the Dive Design System

Drawbacks of AWS Code build

The Benefits of Using the Cloud :

Configuring HTTPD Inside Docker Container.

Voice Recognition offline on Dragonboard with PocketSphinx

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Gabrielle Igarta

Gabrielle Igarta

More from Medium

Procedural Content Generation through a Data-Driven Approach

NO.4 Rhapsody—About a small party game I made

Using a height map and pixel displacement to texture a plane

Atlas Terrain Editor for Unity 3D