Joe’s Work
Friday May 22
Work
Saturday May 23
Level Description Due – Write out what you plan on making for the level. This doesn’t need to be the final outcome. Remember as we go through the rest of the semester and next, the game and the level will change.
Tuesday May 26
List of Sounds – While you’re working on the flowchart you’ll most likely come across what sounds you’ll need.
Thursday May 28
Level Flowchart Due – All great levels need to flow correctly.
Friday May 29
Work
Saturday May 30
Level Blockout – Use the code for the game to block out a level. Can be given to team on Tuesday.
Tuesday June 2
Level Blockout Due – No way around it.
Sound Samples – Seeing no evil isn’t your job. Hearing it is. Not all sounds are necessary but the more the better.
Thursday June 4
Music Feel – It would be good to have background music. If nothing else we need a basic idea of the music feel.
Friday June 5
Work
Saturday June 6
Kick Interfaces Ass – Join the team to present the game.
_____________________________________________________________________________________
Shelby’s Work
Friday May 22
Work
Saturday May 23
Work
Tuesday May 26
Lists - They’re everywhere!!! We need a lot of them. Final ones. Character Lists, Dino Lists, Enemy List. Who can we ride? What can they do?
Thursday May 28
Thumbnails – One thumbnail should take an average of two minutes. We need a lot of them for ideas. They’re also good for portfolio stuff.
Friday May 29
Work
Saturday May 30
Thumbnail Refinement – Refine the thumbnails. Keep in mind we’re not expecting all the artwork complete right now. As much as humanly possible. In fact, make one more than humanly possible. That should do it.
Tuesday June 2
Final Art – Take the most important pieces and make them final.
Thursday June 4
Work
Friday June 5
Work
Saturday June 6
Kick Interfaces Ass – Join the team to present the game.
_____________________________________________________________________________________
Malina’s Work
Friday May 22
Work
Saturday May 23
Work
Tuesday May 26
List – What? Where am I? Well things in the environment will help me figure that out. It’s your job to list them out. (Need to work closely with Joe)
Thursday May 28
Thumbnails (UI) – Thumbnails aren’t much. BASIC sketches. Lots of different ideas. Scrape off that top layer of paint. (Work closely with Tom)
Friday May 29
Thumbnails (Assets) - Again thumbnails are short and sweet. Let’s see those different ideas. Not every asset needs to be thumbnailed. This process will help you figure out what style works best.
Saturday May 30
Work
Tuesday June 2
Final Art (UI) –The user needs something pretty to look at. Otherwise they get confused and angry. Like a bear.
Thursday June 4
Thumbnail Refinement (Assets) – Take the thumbnail ideas and make them better (and bigger).
Friday June 5
Work
Saturday June 6
Kick Interfaces Ass – Join the team to present the game.
__________________________________________________________________________________
Justin’s Work
Friday May 22
Work
Saturday May 23
Code Rework - Figure out how to tackle the code. Our code is very antisocial. It doesn’t like other code.
Tuesday May 26
Work
Thursday May 28
Working Code - New code worked out being built from the start with classes. This will avoid conflict later.
Friday May 29
Work
Saturday May 30
Work
Tuesday June 2
3 Dinos and an Alien – The alien should be able to use three different dinosaurs to do his bidding.
Thursday June 4
Programming Flowchart – I don’t think it should be done until our code is. Working backwards! That’s how the pros do it.
Friday June 5
Prepare for Presentation – This isn’t the only day you’ll do this. We’ll all help too.
Saturday June 6
Kick Interfaces Ass – Join the team to present the game.
* there may not seem like a lot on this schedule but if you know what’s going on there’s a ton.
_________________________________________________________________
Tom’s Work
Friday May 22
Work
Saturday May 23
Code Rework - Figure out how to tackle the code. Our code is very antisocial. It doesn’t like other code.
Tuesday May 26
Flowchart – If the user can’t get to our game they won’t play it. Flowcharts make sense. Hail flowchart.
Thursday May 28
Working Code - New code worked out being built from the start with classes. This will avoid conflict later.
Friday May 29
Work
Saturday May 30
UI Test – Make sure the UI works. Test with people. REAL people.
Tuesday June 2
3 Dinos and an Alien – The alien should be able to use three different dinosaurs to do his bidding.
Thursday June 4
Programming Flowchart – I don’t think it should be done until our code is. Working backwards! That’s how the pros do it.
Friday June 5
Documentation – Stay up until the wee hours of the morning getting everyone’s work together and printing it out into a 300 page document that looks awesome.
Saturday June 6
Kick Interfaces Ass – Join the team to present the game.
Final Note:
I do believe that we can get this done. I don't know about you but this class is top priority. Nobody wants to suck at Interfaces. Nobody wants to wait three or four more semesters to retake this two semester class. We want to graduate and soon. I'm very excited for what this team can accomplish. GO TEAM SUPERFLUOUS!!!!!!!!!!!!!!
I actually think that this schedule is very reasonable. I will absolutely have have a list and reference sheets to you all by Tuesday! (As Kim wanted reference sheets yesterday, so.)
ReplyDeleteI think this scedule is fair and clear. I fully expect everyone to show up each class whith everything presented for each date. I do realize that life can get in the way sometimes and can push a deadline back. If the work isn't completed by the begining of class each date, then the end of the day, before midnight, is the latest it should take. We really need to haul some ass to get this thing going.
ReplyDeleteI agree completely. This schedule will be just fine.
ReplyDeleteThank you. I'm going back to work.
ReplyDeleteMalina - If you have any ideas, just throw them up on the blog. I've got a couple of things I'm going to post in a few.
ReplyDelete