-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Ok, so some meta
A lot of not-PyGame python gamedev just isn't well known. Let's fix that.
This is meant to be kind of a mix of Rust's are we whatever yet (those guys need a webring) and ActivityPub Rocks.
This site is meant to introduce people (developers and developer-adjacent) to the world of making games in Python. That it works, that you can be successful with it, and why you should.
Project descriptions should focus on what differentiates it from the other options and why people should care about this one.
The site should strive to be neutral in tone, not favoring anyone other than Python. Don't worry about the specifics of the implementation unless it leaks or its a significant selling-point. (eg, the fact that Arcade is based on Pyglet and PPB on PySDL2 is completely hidden from the user.)
So we can't list every game-related library ever. What are we including?
- Must be a "game engine", not just a utility or helper library
- Must be active. That can be hard to rigorously define, but let's just rough it out as "the developers have done stuff in the last 3 or 6 months ish" as a start
- Must be written in Python or focused on Python
- Making games must be a significant part of its use
Maybe in the future, we'll have ecosystem pages that get into the major libraries for each engine.
Still trying to figure this out, since some of them (Pyglet, Harfang) can straddle the line, but the questions I'm asking so far:
- Is an event loop provided by default?
- Is rendering code provided by default?
- Is game structure provided?
If yes, you might be a framework. If no, you might be a hardware library