RTSimple... thoughts (aside from: sorry for the hard install, testserver finally up)
This time, I made an unconventional game - from the development side. I wanted to have an RTS in the browser no matter what - it sort of worked.
You can see the result here: http://nekapuzer.at/games/ .. Or better yet, download the final submission
If you want run the RTSimple-server you don't need a webserver, but the python-django module (comes with its own testserver) and a mysql-server. I didnt include a howto for windows users, but you can download if from the django-site (see below) and install via "python setup.py" .
I used lot's of tools, that didnt make it into the README. So here there are:
Handy library for DOM-access and other JS needs
A objectmodel + web-helpers following the DRY principle
shiny web 2.0 magic, coming from my hometown vienna
There are a few things I'll code today, that are missing in the final submissions:
- Units defending themselves automagically when attacked
- Unit moving to attack-target if it is not yet in range (as of now you have to first move the unit in attack-range, then attack works)
And when that is done, I have to balance the units and create more, interesting maps.
In general, the tech-side worked better then before... using django, also first-time, was a relieve. I know my way around JS and its quirks, so now horror there either.
Yeah.. about that. It sort of didn't make it into the final submission lol. Maybe you think it's "twisted" enough to have an RTS with browser-tech. However the full story goes like this: This is a fast paced game with a duration of maximum 5-10min. To make it even more stressfull I planned on rotating (twist!!) a patch of 5-10 tiles in the middle of the map, where usually something of interest is. The buildings, units , etc. on that rotating-tiles would of course move with it... though, that didn't really make it into the submission. (log in to comment) Thanks for tip about py2.5 and sqlite - but I wanted mysql at least, should have gone for postgres though, that would have made life easier. Django version: it must be 0.96. In the readme and install_help file I state this very clearly. I tested it with 0.95 and the new svn version and there were a lot of incompatible changes, so no-go unless you use 0.96
Comments
malcolmt on 2007/09/09 14:24:
When I saw you were using Django, I thought you might have chosen 2.5 as your minimum Python version. Then you could have used sqlite as the database backend, since it comes standard with Python 2.5 and would require no setup.
Also, which version of Django did you develop against? Given the large number of changes (some of which are backwards incompatible) between Django 0.96 and the subversion trunk, the version might be important.