I'm currently a student, and as I always dreamed to build my 3d game with my own proper sets of rule, here I finally come !
I wandered a lot before making the final decision to make ny game using google's o3d, but I don't want to wait anymore :
I wrote the main core game fighting rules and items, I have 2 episodes, one first, short and easy, and another, longer but with a quite much bigger scenario.
The main gameplay aspects are: - infiltration/diversion (I'm a big fan of metal gear since I started playing MGS) - action tactic (I played a lot of counter strike, quake 3 and unreal tournament, and have a whole lot of ideas to bring a new aspect of winning without killing) - strategy/action time battle (I also have some simple idea on how final fantasy ATB system and RTS have aproximately the same concepts, and can be made into one single interface)
I also wish to work at google's one day, as a programmer in -maybe- a gaming division. I am not sure where I am now between studies and work, but I thought too much about gameplay concepts to wait any longer without writing about it.
One other thing: the economy recently showed gaming industry is now stronger than the movie industry. I really want to get hired to get a rewarding job that pleases me, and stop the school as I only like maths and programmation.
Of course, as the google code dictate, this is not only open, but you are free to propose any idea so I can read them : I don't want to make something better than all best games existed on consoles: I want a simple gameplay,
I also want to make a game that would either work on a nintendo ds and an android supported platform: a lot of computation can be saved when using a Resident Evil I/II/III style render: while the game assumes several FIXED cameras can display the environment as RAW pixel images, the 3d is only needed as a CGI static computation: this could lead to almost photo-realistic render, if, of course, this concept is kept and no dynamic render is needed from a graphical dedicated unit, as it would only trace characters, since a room for example doesn't necessarily have a lot of MOVING objects: lights would only make a surface more bright by defining polygonal matrix zones ON the RAW image, and then calculate progressive color change: the result compared to a full 3d engine would be quite the same TO THE EYE.
This game mode could be defined as a static graphic mode, while the other would be a full dynamic mode, compiled for non portable station like console or home computers
Feel free to ask questions !
Of course, I won't collaborate with people I don't know or don't have some 3d meterial conceptual mathematics knowledge, as I'm a learner myself: the game won't be "stand alone": it will as much mode able as it can be done.
But first thing first : don't ask a shit, if you don't know C (NOT C++, JUST PLAIN C99 standard: if, struct, typedef, bit wise operators and switch): I'm still learning JS myself, so don't come and say stuff like "you are doing shit": I know I'm making shit atm, I just want to learn making a 3d game.
These details are provided for information only. No information here is legal advice and should not be used as such.