Moonrays
A creature is hunting you. Find a way to use moonlight and mirrors to track it and kill it before it catches you.
(This is a very short game.)
Awards
Scores
Ratings (show detail)
Overall: 3.0
Fun: 2.6
Production: 2.7
Innovation: 3.8
Respondents: 17
Files
File | Uploader | Date |
---|---|---|
Moonrays-fixedcontrols.zip
Moonrays (fixed controls) |
Tee | 2013/09/22 03:36 |
Moonrays-ss.png
Moonrays screenshot |
Tee | 2013/09/07 22:19 |
Moonrays-prototype.zip
— final
Moonrays: final version. |
Tee | 2013/09/07 22:19 |
Diary Entries
A few notes on Moonrays
You know that I didn't have much time to work on the game when its title is completely generic. :)
This time early in the week I thought of an interesting idea that I wanted to try out. By now you may be tired of me saying that I had little time to work on my Pyweek game, but I do wish I had more time to expand on it. The result was a very short game very focused on what I wanted to try, with no other features. So in a sense, my game was made to prototype this specific idea. A tiny part of the game is to figure out what to do, which I think is fairly straightforward, but if you want to avoid the spoiler of knowing what you have to do you should play the game before reading this.
Here's a description of the idea and the game. The context was originally meant to be a horror game, though I didn't do much in that respect due to time. There's a creature hunting you who's invisible to your eyes (actually, in this prototype it is not fully invisible because I thought it would make it too hard to run away from it). However, a beam of moonlight doesn't pass through the creature. So the goal of the game is to use mirrors to create moonlight beams in order to track down its position. Once you've guessed a position, you can try shooting at it (shooting is limited).
I think I like the result. The beams turned out to be an interesting tool for a "being hunted" type of game: if you have some notion of where the creature is, a good beam construction creates safety. The prototype as it is is a bit shallow and short, but I can imagine that one could expand this idea to something more interesting.
As always, any feedback is appreciated. Congratulations to everyone who finished this Pyweek!
This time early in the week I thought of an interesting idea that I wanted to try out. By now you may be tired of me saying that I had little time to work on my Pyweek game, but I do wish I had more time to expand on it. The result was a very short game very focused on what I wanted to try, with no other features. So in a sense, my game was made to prototype this specific idea. A tiny part of the game is to figure out what to do, which I think is fairly straightforward, but if you want to avoid the spoiler of knowing what you have to do you should play the game before reading this.
Here's a description of the idea and the game. The context was originally meant to be a horror game, though I didn't do much in that respect due to time. There's a creature hunting you who's invisible to your eyes (actually, in this prototype it is not fully invisible because I thought it would make it too hard to run away from it). However, a beam of moonlight doesn't pass through the creature. So the goal of the game is to use mirrors to create moonlight beams in order to track down its position. Once you've guessed a position, you can try shooting at it (shooting is limited).
I think I like the result. The beams turned out to be an interesting tool for a "being hunted" type of game: if you have some notion of where the creature is, a good beam construction creates safety. The prototype as it is is a bit shallow and short, but I can imagine that one could expand this idea to something more interesting.
As always, any feedback is appreciated. Congratulations to everyone who finished this Pyweek!
Moonrays: Fixed controls
Thanks for the feedback, everyone.
It seems that most people had trouble with the controls. I apologize for that. I completely forgot to fix them as I was rushing to put the (small amount of) gameplay in. I've just spent now a few minutes fixing the controls and adding a restart button (I wish I had done that before) and I've uploaded a new version. If anyone who had issues with controls wants to try it again, feel free to play it.
And, yes, I think this is one of my shortest Pyweek games, if not the shortest one. As always, the only reason I didn't expand on it was time. But I think this idea could be quite interesting if expanded on.
Congratulations to the winners! See you all next Pyweek!
It seems that most people had trouble with the controls. I apologize for that. I completely forgot to fix them as I was rushing to put the (small amount of) gameplay in. I've just spent now a few minutes fixing the controls and adding a restart button (I wish I had done that before) and I've uploaded a new version. If anyone who had issues with controls wants to try it again, feel free to play it.
And, yes, I think this is one of my shortest Pyweek games, if not the shortest one. As always, the only reason I didn't expand on it was time. But I think this idea could be quite interesting if expanded on.
Congratulations to the winners! See you all next Pyweek!