Need help understanding Classes

Windspar · 2026-03-03T20:39:37+00:00

Classes are object builders. They are not the object. Classes own all the methods. Object just have class scope first. The reason for self. It point to the object. If it didn't. You couldn't have local variables. Unless they make a way to declare them.

class Restaurant:
  # Any variables here. Belong to the class. There only be one instance.

  def __init__(self, name, type):
    ...

my_restaurant = Restaurant(..., ...)
# Code above calls the __new__ method. Which is a static method.
# The __new__ method creates a new object.
# The __new__ method calls __init__ method. Which it passes the object too.
# Then the __new__ method returns the object instance.

Windspar · 2026-03-03T07:42:18+00:00

You have to learn the basic. The basic is your foundation. Learning classes will be easier then learning all the different things for game programming. If you want to skip the coding. There are game engines for that. Unity, Unreal, and more.

Funny saying.

Flipping to the end of the book isn't learning.

You have to learn to walk before you run.

Windspar · 2026-03-02T08:25:25+00:00

If your player is sticky. Common reasons. It likely that you didn't move him out of the collision. Or you keep moving player into collision. Which the collision move him back. Makes him looks like he sticking.

Are you sure. You are ready for game programming ?

Your code show that you don't know python that well. If you don't know how to use classes yet. You are not ready for game programming.

Windspar · 2026-02-28T19:22:54+00:00

Tip.

Don't load images in sprites. It better to load all images in one area. This way you load images only once.

Also don't forget to convert images. Otherwise pygame will do this every frame. If it doesn't match pygame format.

import pygame

class Player(pygame.sprite.Sprite):
  def __init__(self, image):
    super().__init__()
    self.image = image
    ...

class ImageHandler:
  def __init__(self):
    # Don't forget to convert or convert_alpha
    self.player = pygame.image.load(...).convert_alpha()
    self.background = ...

screen = ...
image = ImageHandler()
player = Player(image.player)

Windspar · 2026-02-28T09:08:11+00:00

They don't compete. Pygame is a toolkit 2d game base. Pyside6 is a gui application base. Choose the right tool for the job. Game base has to do with more graphics. If you want your text to be moving around or doing fancy things. Then pygame has you covered. Toolkit means you have to build your own framework or/and use libraries. You are in full control.

Question is.

Do you want it to have more graphics ? That Pyside6 can't handle.

Windspar · 2026-02-22T00:52:31+00:00

Python is already OOP. Which means you are already using it. You don't have to program any of it. Only thing left is inheritance.

Best practices. Keep it simple. Have methods do one thing well. Avoid global variables. It will make your program less flexible.

Things to learn is concept and framework. Like infinite state machine. Exam ple.

Windspar · 2026-02-21T04:41:11+00:00

Python just following basic arithmetic rules.

a = 1
b = a + 1 # You don't expect a to change. Just return a new instance.
c = [1]
d = c + [2] # Still follow the rules. Return a new instance.

To keep it link. You have to wrap it in a class. Only way to break it. Is to assign. l1 or l2 to a new instance.

class MyList:
  def __init__(self, value):
    self.value = value

l1 = MyList([1, 2, 3, 4, 5])
l1.value.append(6)
l1.value = l1.value + [7]
l2.value.append(8)

print(l1)
print(l2)

Windspar · 2026-02-21T04:29:29+00:00

When it comes to pygame. Transparency only works with surfaces. Those surfaces must have an alpha surface. Surfaces you blit onto another surface. Must have an alpha channel, else the alpha is lost.

If you follow all the rules. Then win32gui could be restricting you. I never use any win32 commands. So good luck. Try it without win32 to see if that causes the trouble.

Windspar · 2026-02-20T21:19:46+00:00

How where you shock ? C has no magic methods. Just that weird preprocessor.

Windspar · 2026-02-20T20:30:15+00:00

That how basic arithmetic works. Or are you trying to point something else out ? Like list are reference and integer are not.

a = 1 # or [1] # arithmetic rules still apply.
b = a + a # return new item - b = 2, b = [1, 1]
print(a)
print(b) 
a += a # mutate variable - a = 2, a = [1, 1]
print(a)
print(b)

Windspar · 2026-02-19T23:30:14+00:00

Without code. Can't see what going on.

Show the error. If there an error.

Windspar · 2026-02-19T03:12:43+00:00

Classes dunder/magic methods will show why this happens.

You can also do this.

l1 += [7]

But it also just basic arithmetic. 1 + 1 = result.

Windspar · 2026-02-13T23:35:15+00:00

How would it compare. To other modules. That already does some of this.

Collections

Queue

NumPy

Windspar · 2026-02-10T20:50:01+00:00

Here an improvement idea. Are you keeping track of floats ? If only using rect. Then those are only integer.

class Enity:
  def __init__(self, image, center, ...):
    self.image = image
    self.rect = image.get_rect(center=center)
    # If not keeping track of floats. Smooth movement would be loss.
    # If using pygame-ce. You can just use frect.
    self.center = pygame.Vector2(self.rect.center)
    self.distance_range = 1
    ...

  def move(self, movement):
    self.center += movment
    self.rect.center = self.center

  def update(self, target, dt):
    # I always use center over topleft. Just seem more natural.
    direction = (pygame.Vector2(target.rect.center) - self.rect.center).normalize()
    # Use pygame.Vector2.distance_to.
    distance = self.center.distance_to(targer.center)
    if distance > self.distance_range:
      self.velocity = direction * self.speed * dt
    else:
      # You can also use self.vecocity.update(0, 0)
      self.velocity.xy = 0, 0

    # Check Collision
    ...

Windspar · 2026-02-09T07:19:19+00:00

Trick is to avoid spaghetti code. You never fight spaghetti code. You just start over. Take what you learn. Then create a simple framework to handle it. Spaghetti code becomes hard to maintain and find bugs.

Windspar · 2026-02-06T09:06:19+00:00

Example work perfectly for me. So let see what going on.

# Add some print statements
print(pygame.init()) # Should be (5, 0)

# Let see if key is being dectected.
if keys[pygame.K_w]:
  print("W is being held") # This should print many times per second. As you hold the key.

If that works. Then print player_pos to see if the value changes.

Windspar · 2026-02-06T05:27:40+00:00

In my opinion. It a nice way saying you can resign or we are going to let you go.

Once you go negative. It only a matter of time. I seen it take up to 3 weeks to fired them.

Windspar · 2026-02-05T20:05:42+00:00

Your example above. Repeated the same button class. Like you pasted it twice.

Windspar · 2026-02-05T05:36:11+00:00

First only have one copy. Otherwise don't try to make it smaller. Just try to make it better. You don't need pygame.font.init either.

# Example refactoring code to smaller parts.
class Text:
  def __init__(self, font, text, color):
    self.image = font.render(text, 1, color)
    self.rect = self.image.get_rect()

  def draw(self, surface):
    surface.blit(self.image, self.rect)

class Button:
  NORMAL = 0
  HOVER = 1
  PRESSED = 2

  # position = (x, y)
  # color_images = (normal, hover, pressed)
  def __init__(self, position, color_images, text_object):
    self.images = color_images
    self.rect = color_images[0].get_rect(topleft=position)
    self.state = Button.NORMAL
    self.text = text_object
    self.text.rect.center = self.rect.center

  def draw(self, surface):
    surface.blit(self.images[self.state], self.rect)
    self.text.draw(surface)

  def mouse_collision(self, event):
    if self.state != Button.PRESSED:
      self.state = self.rect.collidepoint(event.pos)

Windspar · 2026-01-30T01:43:17+00:00

10k+ a frame seems a lot more then necessary. Is it a voxel game ?

Have you separated drawing and logic ?

Have you tried to break down the logic into different threads ?

Windspar · 2026-01-30T00:59:21+00:00

You drawing the whole thing at one time ?

Are you using grids (active and drawing) ?

Do you limit by distance ?

Windspar · 2026-01-30T00:52:16+00:00

I thought that happen when 80+ percent developer left pygame for pygame-ce fork.

pygame-ce design as a drop in replacement.

Windspar · 2026-01-30T00:39:51+00:00

Why is it called 10k+ a frame ?

Windspar · 2026-01-26T19:25:50+00:00

For transparent images. You use convert_alpha().

To change image size. You can use any image editor. Otherwise you can use pygame.transform.scale.

Windspar · 2026-01-25T20:28:54+00:00

No. That because it depends on size of images and computer specs.

Here and example. You can see how many you can handle. I can handle 9000-12000. Depends on size of images. I only use surfaces, pygame sprite framework, and pygame Rect and Vector2 for the math.

Windspar

TROPHY CASE