Hey all!

I am sure we all had that one bug we just could not squash out in time before submission anymore and it drives us insane.

- For me it was a small array error (accessing an non-existing index, douh!) that caused my spawn code to fail every now and then, leading to  one of the special tiles being spawned in map origin instead. Not a big deal and certainly not a game breaker. Worst case is, that you have to repeat the level.

- During production I spent quite some hours on a rotation bug, which turned out to be gimbal lock. Guess you will always have to experience that once in your indie dev life, but hey, I solved that one with quaternions.

All in all, it wasn't so bad after all. Sure at first I wanted to submit a patched version ( I have it ready at hand), but then again, no one bats an eye about a small bug, if the rest is dope!

What are your crimes?

Wanna check out my game regardless?

https://itch.io/jam/gmtk-2019/rate/462667

-Hermicrab

Mine is that sometimes the bullet doesn't always hit the enemy even though it clearly hit them. Here's the link to my game: https://mark-auman.itch.io/one-shot-in-the-chamber

Here's bug in my roguelike called Backpackless that drives me just aarrrrgh: I've forgotten to code the check for the arrows to end :(

The player can obviously abuse this bug to win (bows are pretty powerful weapons).

The most painful thing was I noticed the bug in the period when itch.io was down after the deadline, so I could've fixed it and uploaded the correct version, but I decided that it would be unfair so I didn't.

I have a screen based game, and you transition from room to room by going off the side of the screen.  I also have a dash ability that warps the player forward 100 pixels.  The problem is if you dash off the side of the screen, it won't preserve the leftover pixels in the dash if you're right at the edge of the screen.  It's annoying, but it's not the worst, and to fix it I would have had to deal with collision which would have taken some time when I was already very low on it, and then because I was editing collision I might have just ended up causing more, worse bugs, so I decided to just leave it.

My game doesn't actually adjusts the health ui correctly when taking more than one damage from an attack. People think they get oneshoted at half health. Thanks I hate it.

A very simple one: forgetting to include the win screen :D we attribute this to making the game difficult enough that we barely ever won during playtesting, but then again the point was that it should be hard :)

To try and find this crime, check us out here:

https://itch.io/jam/gmtk-2019/rate/463231

This horrible and shameless visual glitch: 

Not sure where it comes from but it's there on every levels for the WebGL build if you use chrome or firefox. It has to do with OpenGL 2.0 since it's not doing that on 1.0.

The bane of my life.

I managed to squash every technical bug, but i left in text that indicates the game saves, when it does not save at all(something i had to cut). So infuriating!

https://itch.io/jam/gmtk-2019/rate/462355

Ours is pretty simple, though it gave us a good laugh when we first encountered it: in our game, you use a projectile which can bounce off of walls, which is accompanied by a sound effect. However, due to an oversight in how we calculate collisions, if the projectile hits a corner, the sound is played multiple times in the same update, which results in an unexpectedly loud, distorted version of the effect.

Another one would be, to not duplicate code the enemies' bullets are actually just enemies who travel in a straight line. However, due to the way we code collisions between enemies (who are repelled from one another, so they don't stack together), this results in enemies being slightly pushed away by bullets (and not the other way around). We decided to keep that in as well, also gave us quite a laugh when we discovered, what is happening ;)

If anyone is interested in the game, here's the link: https://itch.io/jam/gmtk-2019/rate/462587

Not so much insane, but there's a small bug in the spawn code handling the enemies that bugs me for not noticing until later.
Long and short of it, I used a few random numbers to specify how many spawn, where, and what type. It was supposed to spawn two types equally, but a small oversight changed equal 4/9 chance into 4/10 and 5/10. Literally one digit, off by one, and the larger, enemies are spawning way more than they should.
I also got the lower bound of spawning one type of enemy wrong, so it likes to bounce into the floor on occasion ^^;

A lot of people say my game is difficult, and I wonder if this is part of the why.

On our final boss room, the boss skulls blended in with the pitch black background and you couldn't see them! not really a bug, but it was annoying!

mine broke its textures in the final official jam version so it looks horrible. Also the fireballs were way too fast...  but with itch spazzing at the end i couldn't test it online so i didn’t catch it.  Made an update after the fact that took less than an hours worth of work...  

The bug i submitted with was that the window for "You win" COMES out when you repeat the game by pressing play again for some reason xD

Me know it all knows the truth