September 2008 challenge: “The length of a piece of string”
People and Planes - Second detour
Posted by Tee on 2008/09/12 21:10
Anyone who has been following my posts know that I haven't been doing very well with my entry, so this morning I had a new idea that uses some of what I've already implemented and I scrapped the rest. This is the second time I'm changing ideas, and I don't think I've ever changed ideas so late in Pyweek. Anyway, this new idea isn't too complex to implement, though unfortunately it's not simple enough to have that "beauty of simplicity", and hopefully I'll deliver something in time. I've already coded some of it this afternoon and will continue until I finish.
This is probably one of my worst performances in Pyweek, but I think I can at least submit something that's probably not too fun, but it's slightly innovative in the sense that it's probably not a type of game you play very often. I haven't given up yet.
This is probably one of my worst performances in Pyweek, but I think I can at least submit something that's probably not too fun, but it's slightly innovative in the sense that it's probably not a type of game you play very often. I haven't given up yet.
So long, A love story - back to code
Posted by riq on 2008/09/12 21:02
Ok, I'm back.
I will try to finish the game today. I've the idea. I found a nice music, and I already have the graphics.
TODO:
levels
menu
sound effects
I will try to finish the game today. I've the idea. I found a nice music, and I already have the graphics.
TODO:
Shot The Hook - Almost Done!!
Posted by zhen on 2008/09/12 20:31
Well, it's almost done. All the gameplay is in the game, and only need little polish.
ArmchairArmada PyWeek 7 - I may quit, but first let's see what I have.
Posted by ArmchairArmada on 2008/09/12 19:58
I'm not really in the mood to continue, so I think I might just quit. I probably could make the game before the deadline, but I think I might rather relax a little instead. I really thought this was going to be the PyWeek that I actually end up making something, but I guess I'll have to try again next time. Here are the teacups, mugs, and teabags that I made yesterday:
_Cecilia Music Game_ - Here we are
Posted by JuanjoConti on 2008/09/12 18:23
We'll I have spent less than 5 hours in my game and I think I'll finish it. Of ours it'll be a very light implementation...
Dominoes String - Dominoes String v0.1 release
Posted by milker on 2008/09/12 17:43
You can download in my entry's files list.Thank you for your download.
Can Play !!!
Fishing Frenzy! - Hacking Day 4 Progress
Posted by htormey on 2008/09/12 17:40
A major milestone was crossed yesterday, with the addition of collision detection and animation to handle fish being caught the game is now semi playable. Soon we will upload a snapshot and ask for feedback.
New Features:
-Added new sounds for The SS Busan.
-SS Busan 3d tire graphics added
-SS Busan, now ejects tires which float then drop to the bottom of the sea
-The hook can collide with the ejected tires on the bottom of the sea.
-Collision detection system added. The hook can now collide with fish/tires
-New fish animation, when fish get caught they get pulled into the boat.
-Improved random fish spawning.
-A number of minor performance tweaks.
Tower Climber - Calling it Quits - What I've learned here, and what will happen to my game
Posted by Akake on 2008/09/12 16:50
It's looking like my game isn't going to make the deadline.
I've decided, in a calm mindset, after being talked down from major drama-ism, to just let this one go.
I'll be making Friba the Freebnot, but after the compo is over, and after I've gotten a couple other, simpler platformers under my belt.
I'm just gonna kick back, ride it out, play the entries, and be more prepared next time. :)
So this is pretty much it. It's been a bit of a roller-coaster for me, but I've learned some things about game making.
1.Keep simplicity in mind, or it will escape you:
----My movement scripting was vastly more complex than it needed to be. I had this problem because I didn't spend time figuring things out before the compo, and moreover because I didn't keep the timeless mantra "Keep It Simple, Stupid" in my heart, mind, and other cheesy parts of me.
2.Never code when you're upset:
----Anyone who read this or has been on #pyweek the past couple days can probably figure out how I found this out. It you're getting frustrated, take a break, go get something to eat, take a nap, play with your dog, or anything else that helps you calm down. You won't find solutions to any but the most obvious errors while you're angry.
3.Always look for help on IRC, but try your best to keep a level head:
----*Raises hand guiltily* I had this issue. I blew off #pyweek until yesterday, and even then, go to people for help with bugs as I found them, which was not a time when I was particularly calm. The people on #pyweek are very kindly patient, but this is not something to take advantage of.
4.It pays to make friends:
----One thing I found out is that if you make friends with your competitors, they're more liekly to want to help you. C'mon, who isn't more likely to help a friend? ;)
5.Remember:It's a game about games. It's not for keeps!:
----This is a problem I had, and I want to share it because I feel that I should at least say it if just to keep it in my mind. There's no firing squad if you quit, but the people who wanted to play your game may be bummed out if you aren't going to finish it later and post it on Pygame.org. There are no angry mobs if your game isn't fun or doesn't work. There's no million dollar prize if you win. It's a game.
Sometimes I need to be reminded of stuff like that :P
I'm shelving Friba the Freebnot. I'm going to make it once I've gone back and learned a thing or two about basic platformers. By then, I'll probably be able to do something with the concept, even something really simple.
Besides, she looks too cool to not use. I surprised myself with my Inkscape skills. Heh, all those games I did assets for but never coded payed off! XD
It's been fun overall, though. I really look forward to the next Pyweek, and I'll be more prepared for it! ^_^
*Takes a deep breath, and smiles*
This time around, though, like, I imagine, alot of peoples' first game making compo, I'm gonna take what I learned, what I can use, and all that, and just relax, play the entries, and try to do better next time.
I've decided, in a calm mindset, after being talked down from major drama-ism, to just let this one go.
I'll be making Friba the Freebnot, but after the compo is over, and after I've gotten a couple other, simpler platformers under my belt.
I'm just gonna kick back, ride it out, play the entries, and be more prepared next time. :)
So this is pretty much it. It's been a bit of a roller-coaster for me, but I've learned some things about game making.
1.Keep simplicity in mind, or it will escape you:
----My movement scripting was vastly more complex than it needed to be. I had this problem because I didn't spend time figuring things out before the compo, and moreover because I didn't keep the timeless mantra "Keep It Simple, Stupid" in my heart, mind, and other cheesy parts of me.
2.Never code when you're upset:
----Anyone who read this or has been on #pyweek the past couple days can probably figure out how I found this out. It you're getting frustrated, take a break, go get something to eat, take a nap, play with your dog, or anything else that helps you calm down. You won't find solutions to any but the most obvious errors while you're angry.
3.Always look for help on IRC, but try your best to keep a level head:
----*Raises hand guiltily* I had this issue. I blew off #pyweek until yesterday, and even then, go to people for help with bugs as I found them, which was not a time when I was particularly calm. The people on #pyweek are very kindly patient, but this is not something to take advantage of.
4.It pays to make friends:
----One thing I found out is that if you make friends with your competitors, they're more liekly to want to help you. C'mon, who isn't more likely to help a friend? ;)
5.Remember:It's a game about games. It's not for keeps!:
----This is a problem I had, and I want to share it because I feel that I should at least say it if just to keep it in my mind. There's no firing squad if you quit, but the people who wanted to play your game may be bummed out if you aren't going to finish it later and post it on Pygame.org. There are no angry mobs if your game isn't fun or doesn't work. There's no million dollar prize if you win. It's a game.
Sometimes I need to be reminded of stuff like that :P
I'm shelving Friba the Freebnot. I'm going to make it once I've gone back and learned a thing or two about basic platformers. By then, I'll probably be able to do something with the concept, even something really simple.
Besides, she looks too cool to not use. I surprised myself with my Inkscape skills. Heh, all those games I did assets for but never coded payed off! XD
It's been fun overall, though. I really look forward to the next Pyweek, and I'll be more prepared for it! ^_^
*Takes a deep breath, and smiles*
This time around, though, like, I imagine, alot of peoples' first game making compo, I'm gonna take what I learned, what I can use, and all that, and just relax, play the entries, and try to do better next time.
Rayzan - King of the Strings - New screenshot
Posted by graner on 2008/09/12 16:45
I just uploaded a new screenshot of our game. There are still some stuff to do and we'd like to add many more levels. Good stuff is worth waiting for!
Kiko The Circus Hero - doubleweek proposal !!!
Posted by claxo on 2008/09/12 16:42
What if:
. at deadline for pyweek each entry can opt between 'pyweek candidate' and 'lateweek' candidate
. Judging for pyweek goes as normal, but voting is limited to 'pyweek candidates' (pyweek award)
. 2nd deadline one week later than 1st deadline, voting over 'lateweek candidates' (lateweek award)
. optionally 'pyweek candidates' are allowed to entry for the a 'doubleweek award' , for upgraded games that want to present
The questions are:
. Can Richard take the extra work ?
. Is there enough people interested ?
For this to happen, I think an early as possible anounce is needed, so I ask people interested to do a +1 vote in the thread, and I suggest that details can be worked after the 1st deadline.
@Richard: first, sorry for the too sudden proposal. second: If you cant, you cant, I understand you dont have any obligation. third: if not happens now, probably it will not happen forever ( piggy awards ?).
respectfully,
claxo
. at deadline for pyweek each entry can opt between 'pyweek candidate' and 'lateweek' candidate
. Judging for pyweek goes as normal, but voting is limited to 'pyweek candidates' (pyweek award)
. 2nd deadline one week later than 1st deadline, voting over 'lateweek candidates' (lateweek award)
. optionally 'pyweek candidates' are allowed to entry for the a 'doubleweek award' , for upgraded games that want to present
The questions are:
. Can Richard take the extra work ?
. Is there enough people interested ?
For this to happen, I think an early as possible anounce is needed, so I ask people interested to do a +1 vote in the thread, and I suggest that details can be worked after the 1st deadline.
@Richard: first, sorry for the too sudden proposal. second: If you cant, you cant, I understand you dont have any obligation. third: if not happens now, probably it will not happen forever ( piggy awards ?).
respectfully,
claxo