Here's an idea. It's something nearly all programmers do before releasing their code. They test it first. You click "New Game" and you play it all the way through, and when you hit a bug, you fix it, then do it again until all of the bugs are gone, then you release it and give it a beta version number (0.1 or something). When your game gets to its last version, you have others test it, and you fix anything they find. When they have certified it, you give it "Version 1.00".
I am amazed at the bugs that weren't accidents or typos, but outright repeated coding syntax errors, especially incorrect color definitions. One is a bug, two or more are coding errors. Incorrect image name? A bug, a typo. Many incorrect image names? Laziness. Did you even try to play it through? A good programmer never ever trusts his code. Code must be tested.
Your game has great potential and is interesting, even from the start. Which is a rarity. Don't let the need to release quickly tarnish a good game. Testing is just as important as making it. Keep up the good work, but please improve your quality control.