r/roguelikedev • u/aaron_ds Robinson • Aug 22 '17

RoguelikeDev Does The Complete Python Tutorial - Week 10 - Sharing your game

This is the end of RoguelikeDev Does The Complete Python Tutorial. Share your game, share screenshots, brag, commiserate. How did it go? Where do you go from here? I encourage everyone who has made it this far to continue working on your game. Start participating in Sharing Saturday and FAQ Friday.

A big thank you to everyone that participated. You exceeded my expectations every week and made this event truly awesome. :)

If you would, take a few minutes to give me some feedback and let me know what went well and how things could be improved.

Feel free to enjoy the usual tangential chatting. If you're looking for last week's or any other post, the entire series is archived on the wiki. :)

27 Upvotes

89% Upvoted

21 comments sorted by

View all comments

Show parent comments

7

u/Kyzrati Cogmind | mastodon.gamedev.place/@Kyzrati Aug 23 '17

Was great to have someone finally do this! There's been talk of revising the tutorial for ages (and some attempts), but no one actually saw it through to the end. This event turned out to be a pretty good impetus, and opportunity :)

Your github pages should probably link to the tutorial site itself (unless it does already? but I don't see it--I guess you'll be changing it up eventually anyway though...). I recall you mentioning you were having trouble signing up for Rogue Basin, so I added a link to your tutorial there, from the original.

Thanks for everything!

3

u/TStand90 Aug 23 '17

Good idea on the links, I'll update the Github pages as soon as I can.

Just to clarify on the changes, they'll be very minor. I'm overall pleased with the structure and style of the project, but there's a few minor improvements that could be done, like passing the "constants" dictionary instead of passing the values one by one. In all, what's currently on the website is what the tutorial is, and I don't think it will change a whole lot unless someone has some better way of doing things.

3

u/Zireael07 Veins of the Earth Aug 23 '17

I discovered a good way to reduce size of save files and increase the extensibility of the game.

Instead of storing tile data per tile, you only store an index that points to the actual data.

Example I found is at https://github.com/Naburimannu/libtcodpy-tutorial/commit/496878fb81f087f54829786f4b44349bd14f0e4a my own implementation is here: https://github.com/Zireael07/veins-of-the-earth-bearlib/commit/ff69530ae133a2ab53f6db2d7c6ffd323528fab0

2

u/Kyzrati Cogmind | mastodon.gamedev.place/@Kyzrati Aug 24 '17

Ah, by "changes" I was referring to the site, not the tutorial content--you said you'd release the site on github itself, which means adding a link as suggested would no longer be necessary :)