One of the goals of Python Math is to have a project that's at least to some degree centered around design. It's debatable how well we're going to pull that off (it's a very quick project, and we're working on a small team), but I wanted to take just a paragraph or two to talk about what something like that would theoretically mean.
You could do drive by commits of assets or levels
We'd accomplish something like this by having really clear documentation of what the goals are for each level /asset and by putting that document into an easily accessible place. We're hoping to simulate this sometime either this upcoming week or next week by getting assets from some external people who aren't connected with the project.
Actual design could be contributed to by committee
This is where everything starts getting hugely hugely complicated. What we need for this is a clear, pre-decided "ethos" for the game. Something we can use to tell if something is 'fun' or not, and what 'fun' means anyway. Design docs will help, but there's something even more evasive that I want to capture, and I don't really know what that is yet.
Basically, we're trying to find a way to get around the semi-law that the more cooks you add, the worse everything goes in the kitchen. Having a small team adds unity to a project - it's something people have gotten around with code, but we don't have good mechanisms for doing anything similar with design yet.
Any suggestions?
No comments:
Post a Comment