>>156
This seems way excessive. No one has time for that shit. We should just do it in Python, since it's extremely easy and probably has the best chance of us actually getting something playable.
Alternatively, we all know what the classic
/prog/ troll is, so why not put our money where our mouth is?
Also, is
>>88 the gameplay mechanic we are talking about here? Seems like quite a bit of leg work to actually get something playable. Why don't we do a JRPG, like a stripped down version of FF1? Seems by far the easiest. A character sprite that can wander around a simple static dungeon/overworld, with a simple tileset, and tiles simply have passable/impassable state. Random battles in the style of FF1; turn-based, party-style, no effects other than moving health bars. That's it.
This to me is the quickest way to get a playable game, and from there you can enhance it however you like. I am sure I can write a simple tile-based map editor with wxPython in a few hours, and we can let whoever wants to make content go crazy; meanwhile we can add basic elemental spells (no effects needed, just an alternative form of damage), items and chests, scripted events, etc. These things are not difficult; the main thing in a JRPG is always content.
Also, what do you guys think of revision control? I feel like it's cheating if we break anonymity, which would be required to maintain any kind of shared revision control system; I don't think we should use anything other than pastebin and rapidshare. I think all code patches and such should just go on pastebin and be linked and discussed here, and whoever feels like it can rapidshare a tarball every now and then.
I think this project is a good experiment. Thoughts?