What do you plan on doing that you haven't done before?
PyWeek seems like a good opportunity for experimentation. I'm planning on trying to make use of PyODE for some physics and collision detection. I've use some other physics libraries a little before (Bullet with C++), but I thought this might be a nice opportunity to see what PyODE has to offer.
I also thought a lot about how to create simple, flexible, scriptable, dynamic worlds. If I implement my idea the right way I should be able to very quickly and easily add new unique interactive gameplay elements on a whim. If I wish to change how an object in the world behaves it may even need only one word to be changed.
For example, in XML this might be:
<object id="check" type="variable"> <property id="property" value="value" /> </object> <object id="object" type="object"> <action id="action"> <if condition="check.property == value"> <trigger object="object" action="action"> <argument name="name" value="argument" /> </trigger> <event actor="actor" target="target" event="event"> <argument name="name" value="argument" /> </event> </if> </action> </object>
I'm still not entirely sure how I want this. This is actually getting more complicated than I thought it would be (the implementation might be difficult), so there may still be room for improvement or simplification. Maybe if I didn't try to use XML?
Anyhow, what do you plan on trying to do that you haven't attempted to do before?
(log in to comment)
Comments
class (Object123(GameObject):
-
def trigger(self, name, args):
- return getattr(self, name)(args)
def move(self, args): #is a trigger...
- etc...
That would probably be faster to set up and use, but if you want to try something new, then go the xml approach, otherwise, I would suggest not *much* new, as you still need to be able to finish, and ODE can be a beast as it is - I would suggest you worry about that, and try xml next time...
As for us, we are not trying anything new, just trying to get what we tried last time to work, mainly networking :) LOL
@ArmchairArmada: We had a scriptable world last PyWeek, all credit to Martin and Adam but I think our scripting system was awesome. RB[0] is right, write it in Python, it'll be cleaner faster and more dynamic than anything you could write in a year, let alone a week. Python is after all a scripting language. :-)
Anyway you can check out what we did (generator-based coroutines incrementally advanced from a state-based script management system) by looking at Robot Underground from April.
I hope to write music for our team this PyWeek, which we've never done before. I'm not too set on it though, mostly I want to produce a great game.
Please disregard what I wrote. A few minutes after I made that post I realized that I was really over-engineering things. Implementation would have been time consuming and difficult and in the end I would not have had as flexible or powerful of a system as simple Python code could accomplish. I think I might stick with a more traditional use of classes instead.
My only previous Python-based game ( http://www.pygame.org/project/860/ ), as well as all of the games I have completed in Java, are arcade-style games.
I plan to change that this time around.
simono on 2008/09/03 15:40:
Never Write a Framework (tm) come's to mind :)
But the idea is intriguing...