The Open Source Club meeting this week is on Python basics. It is not a game-oriented overview, but hey, it’s Python. The Open Source Club meets on Thursdays at 7 PM in Dreese Labs. I couldn’t find the room number. If you want to go, it’s best to contact them.
AH HA! Finally found a good word for this…”challenge.”
Finals week is next week which only means one thing! (Besides the agony that shall ensue) Spring Break is around the corner. If you ain’t doing anything social or just have a lot of time on your hands we suggest you try out our challenge, pretty much make a game. There are actually two challenges; here’s what they are:
One game, one “week”
As the title suggest, during the week of Spring Break, you make one game. This challenge is more focused on the playability (and re-playability) or the game. Of course technical and style points are always given, but focus more on FUN!
– You can be alone or with a small group (3-4 people max).
– Any API is allowed (Ogre3D, jMonkey, Pygames, XNA Game Studio, Flash, GameMaker, DarkBasic, plain out OpenGL or DX10 (or 9), etc., etc.). Pick whichever you’re comfortable or want to learn over the week.
– Keep the games “appropriate.” Remember these games represent the GCC and, more importantly, YOU. (At maximum ‘M’ rating, no ‘Ao’ ESRB ratings).
– Although we say this is a “week-long” challenge, you are free to start on this right after your exams if you want. I know how busy we all are and I doubt most of you will start this before your exams. That said I ain’t concerned if you guys start this early, just make sure it’s done, and it’s fun!
7 Games in 7 Days
Now this is where we separate the men from the girly-men! From Sunday till Saturday of the same week, you make one game everyday.
– Mostly the same as the “One game, one ‘week’.” Can be done individually or in a small group, any API is allowed, and keep appropriate.
– Concepts and gameplay ideas can be thought up and written before the official start but unlike the other contest: all code must be done in only one day.
– If you miss a couple of days, it doesn’t mean you are disqualified, it just means you won’t get the points for that day’s game.
This week we are holding 2 meetings to get a better idea for what days are better for all of you. Each meeting will be the same information so you will not need to attend both unless you wanted to. Snacks and drinks as usual. Dates/times listed below.
Wednesday 2-18-09, 6:45pm, Scott Lab [SO245]
Thursday 2-19-09, 7:00pm, Knowlton Hall [KN190]
Other: Recruit, Develop, Interact!
GCC had a presence in the second of the twice yearly python game programming competition. Myself, Alfred, James, and Jane formed a team and completed our game with 1 min to spare earlier this evening.
You can check out our entry on the pyweek website. You can download a version of our software there, or get a tar.gz here. I am pretty excited about our chances for an award, but since it is peer reviewed, who knows. We are though 1 in about 30 entrants, where those are split again by team awards vs. solo awards.
Next pyWeek is in March of 09. We should get another group or two going for that next year. Surprisingly enough, there is actually you can get done in python in a week. The pygame libraries combined with pymunk proved to be a powerful combination.
We’ll keep you all posted, and feel free to let us know how you like the game.
The PyWeek challenge:
- Invites entrants to write a game in one week from scratch either as an individual or in a team,
- Is intended to be challenging and fun,
- Will hopefully increase the public body of game tools, code and
This sounds like a very fun and fast paced project. We should make a team, or two, and get some brainstorming going. I think some simple 2d classics would be great to implement. Or even make a new one of our own.
Entries must be developed in Python during the challenge, and must incorporate some theme decided at the start of the challenge.
The arcade machine at ACCAD: