QCS Progress Report #5345235
by abc · 12/22/2005 (7:35 pm) · 1 comments
I haven't updated on QCS recently. But it's all going well. I've been filling out editing functionality....now you can create new Things, rename them, delete them, edit some(not all yet) of their properties...and today and yesterday was spent reblocking the code so that it actually uses seperate files now. One of the things about Python is that it doesn't really force you to use lots of seperate files until you want to, but making the change generally means a lot of minor breaking and fixing of things. So there's some inertia against doing it, but I finally set to it because editing a huge source file is aesthetically unfun and if I want other people to actually contemplate developing, I'll have to keep such things sane.
While I'm at it, spirit of the holidays and such, I'll point everyone to a pre-pre-not-very-official-unfinished-release download:
people.ucsc.edu/~jhofmann/qcs.rar
It's just the Python source, so you have to have all dependencies(Python, PIL, Pygame) to run it. Start it from qcs.py, or possibly(if your install is set up right) run.bat. It's set up so that you only see the test gameplay: Arrow keys move, 'a' key brings up the attack cursor(space selects your target), 'q' quits. To see the other stuff I've done, you can uncomment the two commented things at the end of qcs.py. Like I said, pre-pre-not-very-official. It still doesn't look like much of anything because it's not yet to the point where any substantial content pipeline can exist - I haven't even put in load and saves for the editor bits that are done. It'll get there.
You can also see the mission statement, which I think I've made too complex, and the readme file that has nothing to read.
While I'm at it, spirit of the holidays and such, I'll point everyone to a pre-pre-not-very-official-unfinished-release download:
people.ucsc.edu/~jhofmann/qcs.rar
It's just the Python source, so you have to have all dependencies(Python, PIL, Pygame) to run it. Start it from qcs.py, or possibly(if your install is set up right) run.bat. It's set up so that you only see the test gameplay: Arrow keys move, 'a' key brings up the attack cursor(space selects your target), 'q' quits. To see the other stuff I've done, you can uncomment the two commented things at the end of qcs.py. Like I said, pre-pre-not-very-official. It still doesn't look like much of anything because it's not yet to the point where any substantial content pipeline can exist - I haven't even put in load and saves for the editor bits that are done. It'll get there.
You can also see the mission statement, which I think I've made too complex, and the readme file that has nothing to read.
About the author

Torque Owner Jason Swearingen