#pyweek

[kolegaliterat]

Dżemowanie

#Felieton: Dżemowanie #notatkiliterata #próby

Myślę, że przyszedł czas, abym podzielił się moimi gamejamowimi historiami. Ku mojemu zdumieniu, zebrało ich się całkiem sporo. Od dwóch lat aktywnie biorę udział w różnego rodzaju zabawach związanych z szybkim tworzeniem gier. Z perspektywy czasu widzę, że dużo mnie to nauczyło. Coraz rzadziej wymyślam skomplikowane projekty, których w ogóle nie jestem w stanie ukończyć. Nie to, że mam listę…

View On WordPress

[tortuefleur]

I finished up my submission to PyWeek, I think it’s alright. I would love to be able to do a lot more graphical work on it but I lost a day so that just didn’t happen. I will probably pick it up and do more with it in the future because I like the concept. But for now the final version is up here!

[grizzly-gamedev]

Behold, the amazing tiles replacement.

Also, behold the reason why this screenshot is named “oops”. This should be sideways, not like this. But on the plus side : it’s displaying the background behind the map ! (it’s something @_@)

Yay. I’m so laaaate for Pyweek

[grizzly-gamedev]

So far, not much.

It’s day 3 of Pyweek20 and I have :

a partial idea of the end UI

a partial idea of what the game is going to feel like

a map on paper

an almost map.py to deal with the map in game

a highscores display that displays nothing :D

You can now lose the game and retry. To lose, just press the DO NOT PRESS button. I mean, it’s not like it’s written in red and caps. Must be fun to press it.

[grizzly-gamedev]

It’s Pyweek 20 !

Dammit, I’m not gonna have much time to work on Dragon Defense for now, but I entered this contest to try and get more experience with Python and Pygame.

This week’s theme is “Data, data, data”, and I decided to make a topdown 2D game where you play a little robot who needs to find more data to save his fellow human crew members aboard the ship he is in. It will feature a little highscore list, and a race against the clock, plus, possibly terrible art.

For now, there’s only a menu, though. And it doesn’t do anything yet. Soon it will do more !

(repository is here : https://github.com/Freyj/Pyweek20/)

[paperstarships]

Pyweek 19 - Favorite Bits: Lightswitch & Sentient Storage

The entries have been a blast to play through (although I still have a good amount of the games to play this week). Here are some of my favorite bits so far from a couple of the games this Pyweek  - Lightswitch and Sentient Storage. 

Lightswitch

I ended up playing this game for much longer than I was expecting to. There’s a wonderful humor to this game and it’s hard to tell how much of that was planned by the game’s creators.

The goal is to find a pattern of words/letters by typing them into the dark room. If you find the pattern and submit five words in a row that satisfy the necessary condition, the contents of the room are revealed (I’ve been having a good time trying to find correlations between each room’s contents and the implied word patterns). Each word or combination of letters you throw into the void will generate a drawing in either red or green, letting you know whether or not the word you gave fit the correct pattern. 

Overall a fun game. You can download and play Lightswitch, as well as check out the team’s documentation and diary entries, on their Pyweek entry page: https://pyweek.org/e/lightswitch/

Sentient Storage

This game went all out on the graphics and sound production for only having a week.

I found myself stuck several times trying to figure out the inventory/object-based puzzles. This is a game that had me wishing for a walkthrough, and starting over several times from the beginning trying to find pieces I may have missed.

You can download and play Sentient Storage on their Pyweek entry page: https://www.pyweek.org/e/np8g/

[adigitalmagician]

DBCM Update

Since Pyweek is over, this project is getting renamed to DBCM, so update your watched tags accordingly.

Today's effort was setting the framework for animating battle scenes. Since, ya know, it's a little boring without it. This meant setting up the battle frame from the menu screen, and start puzzling how to animate over time. The solution is of course setting a bunch of variables in the model that are "future" or something similar and setting the animation equation to move from current state to future state over time. Then of course when the animation is done and the animation is over, the model needs to commit the change to the actual values. No big deal, right?

So, the second issue is how to handle time. To date, I've been using Pygame's Clock module to handle it, but it's hooked directly to the model and it's the only pygame call in the model at the moment. So, the plan now is to cut that out and make that a new controller that I can manipulate in its own time. Of course, a second controller means either hooking in each one separately, or making a mediator for the controllers to listen to that handles subscription to the main mediator.

A quick branch and hour of puzzling later, and that's what's happening behind the scenes now. The game itself doesn't look any different. Yet.

[adigitalmagician]

Pyweek Miniupdate

I've definitely lost this. I wasted too much time figuring out the MVC thing, but I learned a bunch, and I'm going to continue working on this project. For now, it's goign to be menu based, and eventually have a fun little overworld map so exploration can happen. But it won't be done in eight hours.