Collision Detection - A Lesson Learned

I'm... really disgusted with my collision detection system. It's terrible. I tested it. Things jitter, shake, and twitch, and I'm not even using physics. D:

*Sigh* I guess now I have to either redo everything using pygame.sprite... or have a really bad entry.

It's looking more and more like I won't finish.

Now I need to learn pygame.sprite in under three days.

*Hangs head* I wish I hadn't been so stubborn about coding everything the hard way. Now look at it. It's a mess. It's a horrible mess.

I'm debating whether I want to continue. I want to finish this game, but I'm not sure how badly I want to. I've got it stripped down to its core and I still can't get it to work.

I may not submit my entry. In the state it is in now, I don't want it out in the world with my name on it. I will be trying to rework the collision, but I'm not sure how quickly I can do that, and I still have to figure out the level generator.

I'm very pessimistic right now. I've looked over my collision code, and it would be extremely difficult to fix it, and the resulting code would either be a monstrosity, or take a day or two for me to get working properly, depending on whether I fix what I have or start over on the collision code. And implementing pygame.sprite, from what I know about it, means that very, VERY little of what I have code-wise, and even then only game constants, will still be usable.

I'm still thinking it over, but I may decide to forfeit. This project has been one disaster after another. I want to have an entry, I don't want to look like a twit entering in a contest and then giving up, but I don't know that I can finish. So I may be giving up.

It's been fun, though. And I'll definitely enter again, but this time around I don't think I'm going to be able to get it working in time.

Not sure how to end this message, but... That's it, I suppose. :(

----====----

I'm leaning towards giving up. If I do, I'll probably finish this game later, but I'll shelve the idea for when I've learned pygame.sprite.

It was really foolish of me to try to make a platformer without using it, but it's really counter to the way I'm used to thinking. I have a hard time with high-level libraries. :/

I really don't feel comfortable submitting this as-is, but the stress of trying to debug the collision engine may be getting to me.

I'm unsure of whether I can finish in time. I can't figure out pygame.sprite for the life of me, and I need it to do the collisions correctly. :/

Any good tutorials on sprites in pygame? Or should I just throw in the towel?
Feedback would be really appreciated.

----

I'm reading through a tutorial on sprites, and I'm also learning just how little Python I really know. ._.

I'm officially putting my project on hold for now. I haven't decided whether I'm going to forfeit, but it doesn't look like I'll be able to finish in time and not miss most of my homework.

It's been fun, guys. Hopefully it'll all go better next time around.

(log in to comment)

Comments

Hey, you still have a few days.. Try to get it somewhat working - even if you don't finish your game you'll learn alot. ^^