• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

Solid Objects in Pygame

5 posts in this topic

Hello, everyone. I have a little bit of programming experience, having messed with Python on and off over the years. I'm just now getting my feet wet in game development, and I've already run into a problem.


I want to make a simple maze game. The object of the game will be to navigate a white square from the upper-left corner of the screen to the bottom-right corner, through a simple maze. The problem I am having is this: how can I prevent the square from simply passing through the walls of the maze? Clearly, I need some way to make the walls "solid" so that the square cannot pass through them.


My first solution was this: every pixel occupied by a wall is stored in a huge list, as is every pixel occupied by the square. Each time the player presses an arrow key, the game checks to see if the pixel that the square is about to move into is occupied by a wall. It does this by taking each pixel occupied by the square, and checking it against each pixel occupied by any wall. If there are no "matches," the square moves. So, in pseudocode:


list1 = list of all pixels occupied by square

list2 = list of all pixels occupied by maze walls


if the user presses the "left" button:

     Check to see if there are any "matches" between any pixel to the left of a pixel in list 1 and any pixel in list2

     If there are any matches: the square stays stationary

     Otherwise: the square moves


Although I got it to work, it was very slow. Can anyone give me a better method to keep track of where the walls and square are? More importantly, can anyone share some general principles for keeping track of objects on screen?

Edited by Pneum

Share this post

Link to post
Share on other sites

If the walls are all square, then you can just use a tile grid.

grid = [
	[True, True, True, True],
	[True, False, True, True],
	[True, False, False, True],
	[True, True, True, True]

In a way, this is similar to storing the actual pixels, but using 16/32/64...(whatever your tile size is) times less space. This does mean that when rendering you need to make sure to multiply by tile size:


for y in range(grid):
	for x in range(grid[y]):
		# isSolid for here could just return the cell because the true/false represents its solidity
		# But if you want to change what data you store about each cell, then it's good to already have this in its own function
		if (isSolid(grid[y][x])): 
			# I don't know Pygame's API
                        drawRectangle(x * TILE_SIZE, y * TILE_SIZE, TILE_SIZE, TILE_SIZE, CELL_COLOUR);

For the physics, you need to step x and y individually. A good guide for this is in "the guide to implementing 2d platformers" (although it says platformers, it still works in top down, and it's a good read too if you want to make a platformer next).


Share this post

Link to post
Share on other sites

Thanks for the advice, both abstract (SeraphLance) and concrete (dr01d3k4). I'll take it on board.


Share this post

Link to post
Share on other sites

Hello, all. I've taken your advice on board and found some success with it, but I've had a new problem. I created a game where one could move a rectangle around by pressing up, down, left, or right. The floor is "solid," and I successfully programmed the game to stop the rectangle from moving through the floor. However, I've run into a problem again: the movement works fine for the first few button presses or so, but after that, a glitch happens where the rectangle will refuse to move at all. Here's the code, if anyone can take a look at it:

import pygame

# Define some colors
BLACK    = (   0,   0,   0)
WHITE    = ( 255, 255, 255)
GREEN    = (   0, 255,   0)
RED      = ( 255,   0,   0)


#Set the width and height of the screen [width,height]
size = (700,500)
screen = pygame.display.set_mode(size)

pygame.display.set_caption("Jumping Square!")

#Loop until the user clicks the close button
done = False

#Used to manage how fast the screen updates
clock = pygame.time.Clock()

def generatetiles(x,y): #Generates a tile grid, implemented by a matrix
    countx = 0
    county = 0
    indices = []
    while countx < x:
        countx += 1
        county = 0 #reset y coordinate count each time
        while county < y:
            indices[countx - 1].append(0) #0 means an unnoccupied tile. Initialize to an empty grid.
            county += 1
    return indices

Tiles = generatetiles(70,50)

class stationaryobject: #Hitbox for anything that stays still
    def __init__(self,x1,x2,y1,y2): #x1/x2 and y1/y2 specify corners of hitbox
        countx = x1
        county = y1
        while countx <= x2: #Since x2 is counted up before it's used, we use <=
            county = y1
            countx += 1
            while county < y2 + 1:
                Tiles[countx-1][county] = 1
                county += 1

class moveableobject:
    def __init__(self,x1,x2,y1,y2):
        self.occupiedtiles = {}
        countx = x1
        county = y1
        while countx <= x2:
            countx += 1
            county = y1
            while county < y2:
                Tiles[countx-1][county] = 1
                county += 1

    #define methods to scan the top, bottom, left and right sides of the object's hitbox to return data for movement.
    def scanleftside(self):
        firstxcoordinate = self.occupiedtiles.keys()[0]
        return {self.occupiedtiles.keys()[0]:self.occupiedtiles[firstxcoordinate]}
    def scanrightside(self):
        lastxcoordinate = self.occupiedtiles.keys()[-1]
        return {self.occupiedtiles.keys()[-1]:self.occupiedtiles[lastxcoordinate]}
    def scantop(self):
        top = {}
        for xcoordinate in self.occupiedtiles:
            top[xcoordinate] = self.occupiedtiles[xcoordinate][0]
        return top
    def scanbottom(self):
        bottom = {}
        for xcoordinate in self.occupiedtiles:
            bottom[xcoordinate] = self.occupiedtiles[xcoordinate][-1]
        return bottom

    def moveleft(self):
        leftside = self.scanleftside()
        xcoordinate = leftside.keys()[0]
        blockedflag = 0
        for ycoordinate in leftside[xcoordinate]:
            if Tiles[xcoordinate-1][ycoordinate] == 1: blockedflag = 1
        if blockedflag == 0:
            rightmostxcoordinate = self.occupiedtiles.keys()[-1]
            leftmostxcoordinate  = self.occupiedtiles.keys()[0]
            del self.occupiedtiles[rightmostxcoordinate]
            for ycoordinate in Tiles[rightmostxcoordinate]: ycoordinate = 0
            self.occupiedtiles[leftmostxcoordinate-1] = self.occupiedtiles[leftmostxcoordinate]
    def moveright(self):
        rightside = self.scanrightside()
        xcoordinate = rightside.keys()[0]
        blockedflag = 0
        for ycoordinate in rightside[xcoordinate]: #Check coordinates to the right of the current right side to see if they're occupied
            if Tiles[xcoordinate+1][ycoordinate] == 1: blockedflag = 1
        if blockedflag == 0:
            rightmostxcoordinate = self.occupiedtiles.keys()[-1]
            leftmostxcoordinate = self.occupiedtiles.keys()[0]
            del self.occupiedtiles[leftmostxcoordinate]
            for ycoordinate in Tiles[leftmostxcoordinate]: ycoordinate = 0
            self.occupiedtiles[rightmostxcoordinate+1] = self.occupiedtiles[rightmostxcoordinate]
    def moveup(self):
        top = self.scantop()
        ycoordinate = top.keys()[0]
        blockedflag = 0
        for xcoordinate in top:
            if Tiles[xcoordinate][ycoordinate-1] == 1: blockedflag = 1
        if blockedflag == 0:
            for xcoordinate in self.occupiedtiles:
                del self.occupiedtiles[xcoordinate][-1]
                Tiles[xcoordinate][-1] = 0
                self.occupiedtiles[xcoordinate] = sorted(self.occupiedtiles[xcoordinate])
    def movedown(self):
        bottom = self.scanbottom()
        ycoordinate = bottom[bottom.keys()[0]]
        blockedflag = 0
        for xcoordinate in bottom:
            if Tiles[xcoordinate][ycoordinate+1] == 1: blockedflag = 1
        if blockedflag == 0:
            for xcoordinate in self.occupiedtiles:
                del self.occupiedtiles[xcoordinate][0]
                Tiles[xcoordinate][0] = 0
                self.occupiedtiles[xcoordinate] = sorted(self.occupiedtiles[xcoordinate])

player = moveableobject(1,2,3,6)
square = stationaryobject(34,39,44,49)
floor = stationaryobject(0,69,48,49)

# -------- Main Program Loop -----------
while not done:
    # --- Main event loop
    for event in pygame.event.get(): # User did something
        if event.type == pygame.QUIT: # If user clicked close
            done = True # Flag that we are done so we exit this loop
        if event.type == pygame.KEYDOWN:
            if event.key == pygame.K_LEFT: player.moveleft()
            if event.key == pygame.K_RIGHT: player.moveright()
            if event.key == pygame.K_UP: player.moveup()
            if event.key == pygame.K_DOWN: player.movedown()
    # --- Game logic should go here
    # --- Drawing code should go here
    # First, clear the screen to white. Don't put other drawing commands
    # above this, or they will be erased with this command.

    # --- Go ahead and update the screen with what we've drawn.
    # --- Limit to 60 frames per second
# Close the window and quit.
# If you forget this line, the program will 'hang'
# on exit if running from IDLE.

I've tried to solve this problem by setting the movement methods to print the value of "blockedflag" each time the user presses a button, to make sure that the rectangle was not being blocked unnecessarily. No such luck: "blockedflag" always returned 0, unless the square was pressing against a hard surface (which means that the blockedflag value is working the way it should). I also tried printing the global tile matrix ("Tiles", defined on line 36) each time the user moved, to make sure that the values stored in that matrix were being deleted correctly (they were). So what gives? Can anyone point to a flaw in this code that my dumb eyes seem to have missed?

Edited by Pneum

Share this post

Link to post
Share on other sites

I'm not entirely sure what you're doing. Your code is hard to read and follow, and has lots of duplicated code.

I made this example that shows moving the player 1 tile at a time (the collision for this is a lot easier).

import pygame;
from random import randint;

BLACK = (  0,   0,   0);
WHITE = (255, 255, 255);
GREEN = (  0, 255,   0);
RED   = (255,   0,   0);


TILE_NONE = False;



TITLE = "Maze Game";

FPS = 60;

def sign(x):
    return (x < 0) and -1 or (x > 0) and 1 or 0;

class Player(object):
    def __init__(self, x, y):
        self.x = x;
        self.y = y;

    def move(self, dx, dy, tiles):
        if (dx != 0):
            if (dy != 0):

            newX = self.x + sign(dx);
            if (not isSolidTile(tiles, newX, self.y)):
                self.x = newX;

        elif (dy != 0):
            if (dx != 0):

            newY = self.y + sign(dy);
            if (not isSolidTile(tiles, self.x, newY)):
                self.y = newY;

def generateTiles(width, height):
    tiles = [ ];
    for x in range(0, width):
        tiles.append([ ]);

        for y in range(0, height):
            tileType = TILE_NONE;

            if ((x == 0) or (y == 0) or (x == width - 1) or (y == height - 1) or (randint(0, 10) < 2)):
                tileType = TILE_SOLID;


    return tiles;

def isSolidTile(tiles, x, y):
    return ((x < 0) or (y < 0) or (x >= MAP_WIDTH) or (y >= MAP_HEIGHT) or (tiles[x][y] == TILE_SOLID));

def renderTiles(screen, tiles):
    for x in range(0, len(tiles)):
        for y in range(0, len(tiles[x])):
            if (isSolidTile(tiles, x, y)):
                pygame.draw.rect(screen, TILE_COLOUR, [x * TILE_SIZE, y * TILE_SIZE, TILE_SIZE, TILE_SIZE], 0);

def renderPlayer(screen, player):
    pygame.draw.rect(screen, PLAYER_COLOUR, [player.x * TILE_SIZE, player.y * TILE_SIZE, TILE_SIZE, TILE_SIZE], 0);

def playGame():
    screen = pygame.display.set_mode(SCREEN_SIZE);
    clock = pygame.time.Clock();

    playing = True;

    tiles = generateTiles(MAP_WIDTH, MAP_HEIGHT);
    player = Player(2, 2);

    while (playing):
        for event in pygame.event.get():
            if (event.type == pygame.QUIT):
                playing = False;

            if (event.type == pygame.KEYDOWN):
                if (event.key == pygame.K_LEFT):
                    player.move(-1, 0, tiles);
                if (event.key == pygame.K_RIGHT):
                    player.move(1, 0, tiles);
                if (event.key == pygame.K_UP):
                    player.move(0, -1, tiles);
                if (event.key == pygame.K_DOWN):
                    player.move(0, 1, tiles);


        renderTiles(screen, tiles);
        renderPlayer(screen, player);



if (__name__ == "__main__"):

The way it works is:

  • There is a 2 dimensional array of booleans - true for tile being there; false if there isn't
  • When rendering, iterate through these and if there's a tile, draw it at that location * TILE_SIZE (in a real game you may want to account for camera moving and only thinking about what is actually on screen)
  • Player's position is (x, y), which is the location of the top left corner in tile space. The size of the player is assumed to be 1x1. Just like with tiles, when rendering need to scale by TILE_SIZE
  • When the player attempts to move, +- 1 in the direction they want to move, if there isn't a tile there then it's safe to move, else do nothing

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0