The Feeble Diddle - Rev 163

Feedback anyone??

Ok not perfect, but glitchless.

Wow! Thanks! I've been wondering how perfect collisions worked for months.

You need to update the link to:
http://diddle.googlecode.com/files/Diddle%20Rev%2052.zip

If you're having trouble with collisions, I have a tutorial on basic rect-rect collision response here: http://pymike.pynguins.com/?page=tutorials&id=1

The basic idea is to move/check 1 axis at a time. (e.g. move X axis, check for collisions, move Y axis, check for collisions)

I'm really liking this game, especially the art. Looking forward to seeing it finished!

I should probably try the loading into groups thing. Are groups different from lists?

for now my text files are lines of "x_coord y_coord item_ID"

when you want to access data from terrain, terrain[0] == x_coord, terrain[1] == y_coord and so on.

when you want to loop through the whole group just do
for yada in terrain: yada.terrain

this should clean up your source code a bit

I'm still a bit new to pygames myself but heres some advice. Load your game objects in groups. Heres some of my source code for my game. It may not be the best method but it's fast and it's been working well for me.

#counts line in text file
terrain_loop = sum([1 for line in open("data/map1_terrains.txt")])

#loads raw terrain data into list... or was it an array? meh...
raw_map_terrains = [re.findall(r"\w+", line) for line in open("data/map1_terrains.txt")]

#Makes the group
terrain = pygame.sprite.RenderUpdates()

#adds to the group line by line
for i in range(terrain_loop): terrain.add(Map_Objects(raw_map_terrains[i], screen))


read http://www.sacredchao.net/~piman/writing/sprite-tutorial.shtml
it's an amazing tutorial with laods of examples

If anyone wants to contribute feel free to. Though it'd probably be a nightmare with how messy my code is.

Awesome. BTW you can host your zips on googlecode too. (Downloads tab > New Download)

Ok, I am using PySVN workbench and now have a googlecode page.

No no! Use googlecode! (http://code.google.com/hosting/) And svn is very simple:

cd gamedir
svn checkout googlecodeurl

Then to add your files...

svn add filenameorfolder
or
svn add *.fileextension

Then to upload:
svn commit -m "New version info"

BTW, your game is looking really cool. Keep working on it!

So for svn I need a server, I could probably make one, but it would probably only have a PIII processor, and 256 mb of ram, would that be sufficient? Or perhaps I could use the one that my mom hosts her website on? I can access it through ftp. I don't think that would work. Does svn seem like a little much? Or is this a bigger project than I thought? I guess I am going to need an svn if this program is going to have more than one developer. I am starting to learn svn, it seems pretty complicated.

Hey thanks, I think I'll try subversion.

Might I suggest using a version control system (svn being probably the easiest to learn) rather than copying the file over and over every time you change something. You can keep the log stuff in svn as well.
<br /><br />
Some of the phsyics and math etc are a bit weird, but I like where you are going with this. Keep at it!

Maybe I should use PGU for level editor and menus etc.?? I am going to get all my code working before rewriting it.

My code is just so messed up I might as well redo it in a different coding style.

your collision isn't very good. I am myself working on a platformer, and so far, here is my suggestion for collision:

if self.rect.right >= collision.rect.left and\
self.rect.right <= collision.rect.right and\
self.rect.left <= collision.rect.right:
if not self.on_ground:
self.rect.x = collision.rect.left-self.rect.width
self.canright = False
if self.rect.left <= collision.rect.right and\
self.rect.left >= collision.rect.left and\
self.rect.right >= collision.rect.right:
if not self.on_ground:
self.rect.x = collision.rect.right
self.canleft = False
if self.rect.bottom > collision.rect.top and\
self.rect.bottom < collision.rect.bottom and\
self._rect.bottom <= collision.rect.top:
self.y = collision.y-self.rect.height
self.curgravity = 0; self.on_ground = True
self.on = collision; self.dy = 0
if self.rect.top < collision.rect.bottom and\
self.rect.top > collision.rect.top and\
self._rect.top >= collision.rect.bottom:
self.dy = 0
self.y = collision.rect.bottom

just adapt for your program.

note: self.x and self.y are the same as self.rect.x and self.rect.y, dx and dy are direction x and direction y. You just add dx and dy to x and y every frame.

Fixed the fps (I originally turned it down to take a screenshot), added readme.

Cute, but limiting the FPS to 2 is a, uh, bad idea. Try clock.tick(30) or something more reasonable.

Thanks, I'll upload the updates soon. Probably should do more code commenting.

Sorry, it's game9.py the others are older versions

Remember: it's commas between tags.

What do you open? Is it game.py? game2? 3? A readme would be helpful. Also, it tries to import gameEngine, which isn't in the package, so please include it so it can be played!

General help notes:

kill() removes sprites from all groups.
have a collision buffer. for example, if you are moving at five pixels per frame, remember to check for collision up to five pixels in.