Skip to content
MaskedRetriever edited this page Oct 22, 2012 · 2 revisions

I did a snippet of a game a while back in Adventure Game Studio and I quite liked it, but I had a lot of frustrations with various things being stuck as this-is-how-it-goes with no way to change it, and when a hard drive failure wiped all my project files, I decided, you know what, it might not take me that much longer to implement something than it did to learn it.

Hence ScummPy.

Now I understand there's another project called PyScumm out there which has been orphaned for a while, and while I'm a believer in contribute-rather-than-make-new, I honestly couldn't make heads or tails of the code base, and the demo didn't run on my machine.

Hopefully I will fare slightly better.

As of now, I have tested the basics of the engine on a couple different platforms. The code is (mostly) organized and over time I hope to keep it as clean and pithy as possible. Another big goal is flexibility: I have a second demo game that I run on my home machine every now and then to see if major changes (different resolution, character size, animation lengths, etc) are "safe".

To Do: Actually make documentation on using the engine.

Clone this wiki locally