Just found a massive bug in my entry that was causing slowdown for many people, caused by one stupid line of code! I was drawing shadows over every tile on the map instead of just the ones that were on screen, guh
Uploaded a fixed version now though. I think that's ok in the rules, but I've left the buggy version up too just in case.
I think that you're fine to upload fix updates, at least I hope so (because I've uploaded 3 updates so far
)
Every Ludum Dare entry page shows the rules on post-compo fixes:
MY GAME CRASHES, IS UNBEATABLE, OR I MADE A TYPO: We allow you to fix crash or win condition bugs after the deadline (in a sense, like “porting” to support more players). We also allow “typo” bugs. I.e. A true that should have been a false, a word that should have been a different word, very tiny changes that you would have caught if you had more sleep. We leave this open to interpretation, but generally speaking your game should be identical to the game you submitted. No new features, just things you messed up last minute. Typos.
Whether or not you're allowed to fix it depends on the severity of the problem and the amount of code affected.
A clear example of a bug that's allowed to be fixed is a bug I had in my previous LD entry,
World of Minimalism: you could make a tile solid by checking the 'solid' box, but unchecking the box didn't make the tile non-solid again. This would lead to someone inevitably making the starting tile solid (ended up happening a couple times) and players not being able to fix it, making it impossible to even move. Tiny amount of code, game-breaking effect.
An example of a bug you're not allowed to fix is the major bug in my
current LD entry where you get stuck in the floor occasionally (until you jump or move in the other direction). It's very annoying, but the game is perfectly playable. It took some serious debugging to find out when exactly the bug occurs (not entirely sure about the REASON the bug occurs), and the easiest fix (which I ended up using for the post-LD version) was to write some code to check for the condition that would trigger the bug and escaping that condition (the bug only triggers exactly on the border of tiles, so I just move the player's X position by 1). (The 'proper fix' would be to just rewrite my shitty physics code.)
It took significant effort to resolve an issue that made the game less fun. I would've fixed it during LD if I had the time, but unfortunately, I didn't - shit happens, that's how LD works. My entry is judged by what I did in 48 hours, not by what I did in 48 hours and then another day for fixing stuff.
Community
