March 2019 challenge: “6”
Posted by mauve on 2019/04/01 21:18
Some people have reported getting a plain brown screen in What The Frog?!
I couldn't reproduce the problem, because it is driver related and it works fine with my drivers.
Many thanks to rdb who spent an hour working through the problem with me. Ultimately we think it is this one-line fix - but to make it easier I've re-packed the release and uploaded it to GitHub (which includes another commit that may or may not do nothing).
Apologies, and good frogging!
DEEP-6 - Notes for reviewers
Posted by schilcote on 2019/04/01 06:04
So, uh, a few notes:
There's no save system, so, uh, don't close the game if you don't want to start over.
Game requires Python 3.7.
So, I managed to completely break combat by accident; I made a last-second change 'cos everyone was way too fragile, and instead made combat completely stake-less. Too late to fix it now.
Really do read the readme, the game is a little bit obscure as it is.
6-Crates - True Final Diary Entry
Posted by Phantasma on 2019/03/31 23:16
I've done all I can with this final upload. I believe I covered almost everything. If not well...
Whatever happens, I'll take what I can get from feed back and work on it for the next challenge. It's been fun.
Posted by asrp on 2019/03/31 21:11
Here's a diary entry for commenting and reporting anything.
The game uses Python 2.7
𝐻𝑒𝑥𝑖𝑚𝑎 - Uploaded fixed build
Posted by rdb on 2019/03/31 20:15
I have uploaded a fixed build. This is particularly of relevance for macOS users, for which the build was broken for a variety of reasons.
I am given to understand that it is OK to put in bugfixes and distribution-related changes on the final sunday, as long as the gameplay is unmodified. I've not made any change that changed the behaviour or visuals of the game itself under normal conditions (other than an insignificant change to allow you to get a star on level 1-3), but in the interest of full disclosure, here is the full list of changes:
- Fix crashes and game-breaking graphical glitch on macOS
- Saving would crash when extracted to read-only directory
- Fixed the UI locking the game in an unusable state when double-tapping escape
- Updated README with additional documentation and missed acknowledgements
- It was impossible to get the star on level 1-3 due to the move requirement being wrong
- Removed unused .ogg files
- Set a window title so that you can find the game in your task bar
- Add an error message if you try to run the game in Python 2
- Shader fix for an obscure driver error on some Linux systems
If you feel that it is unfair to judge the fixed build, feel free to grab the 1.0.0 download instead (or check out v1.0.0 on GitHub), but you may run into the above bugs.
TextSmith - Finishing Line Hosting Shenanigans
Posted by ntoll on 2019/03/31 13:30
There's not a lot there at the moment, but we'll be building out the six literary worlds over the coming days... and you're welcome to contribute too. We've written some
simple documentation to get you started, although we totally concede that the TextSmith "engine" still needs plenty of refinement.
After some rather subtle problems with Heroku, Gandi based A records and websockets (connections were getting dropped after 55 seconds), I've migrated to a small EC2 instance running on AWS, so please treat it with care. If you get errors please ping me via Twitter (@ntoll). The side-effect is we don't automagically get HTTPS connections, so (sadly) your password will be transmitted in the clear. Please just use a throw away password for connecting to the game for testing purposes.
This has been my favourite PyWeek (my third so far). I'm definitely going to continue with the TextSmith code, it needs refactoring and there are a bunch of gremlins I want to fix. It'll probably be a complete re-write with copious amounts of code-reuse from this original version, but without this first draft, I wouldn't be in a position to understand and see where improvements can be made.
Finally, all the other entries I've submitted in previous PyWeeks have built upon some sort of existing library (e.g. the amazing PyGameZero). This entry was
completely written from scratch. The only third party modules are
Quart (used for very basic web-facing stuff like static templates and the websockets) and the
Python Markdown module (for rendering user generated content).
My favourite part of PyWeek comes next, exploring, playing, enjoying and commenting on all the other entries. This is a source of joyful silliness.
As always, thanks to Dan Pope for making all this happen.
Posted by zwerver on 2019/03/31 10:25
The jam has ended and boy was it fun and cool. We laughed and cried. We danced and sat still for long stretches of time. We drank and forgot to drink. But it's all been worth it. This is the best pyweek yet! *jumps in the air in freezeframe*
6-Crates - Uploaded The game + screenshot
Posted by Phantasma on 2019/03/31 04:58
Soo after 4 hours of strenuous research on how to package and submit the game. I think I MAY HAVE figured it out. Let me know if I'm missing anything with the submission and I'll try to get it done ASAP.
Also how can you tell if you released your source code? Does someone look at your Github repo to verify it or something?
Posted by gcewing on 2019/03/31 02:57
A bit of a rush job again this time. The idea I chose was probably a bit too ambitious -- it took me until Thursday to come up with a suitable data structure and algorithm, and some fairly fundamental bugs were plagueing it until the last moment, so I didn't get a chance to implement most of the things I had in mind. On the plus side, I gained a few insights into how hexaflexagons work, hopefully not at the expense of too much of my sanity!
Some future directions I could go with this:
- Putting images on the faces
- Rotating the view to look at the flexagon from different perspectives
- Animated flexing
- A way to "peek under the flaps" to see what the next flex will turn up
- Printing out a pattern for making a physical version of your creation
- Build a flexagon-manufacturing CNC machine (okay, maybe not)
Posted by rdb on 2019/03/31 02:17
Phew, the game got finished in time! I'll make a better diary entry tomorrow, but I've created this one in the meantime so that people have a place to report game-breaking bugs or ask questions about how to run the game.
You can run it from source (please read the README.md) or download the binary builds from
the entry page, or grab the latest source from
GitHub.
Hope you all enjoy the game!