Date post: | 27-Jan-2015 |
Category: |
Self Improvement |
Upload: | firehosegames |
View: | 118 times |
Download: | 1 times |
Rapid, Iterative Prototypingor, How to Rip off Dinosaur Comics
What we’re gonna cover
• The path to our first game• Show off some interim builds • Lessons learned • 4 ways to Prototype!
• And occasionallydinosaurs
Who Are We?Eitan Sharat
2007
Eitan
2008
2009
Starting out
Starting out• Focus on our strengths, know (and work on)
our weaknesses
Our First Game
Scope
Scope it right!
NOToo Big
Perfect Size(Awesome Game, btw)
Start PrototypingFour Days, Three Prototypes
Test on the fifth day, and listen to testers
Mon
Brainstorm Ideas
Tues
Prototype ideas 1 and 2
Wed
Prototype ideas 2 and 3
Thurs
Prototype idea 3,
polish all
Friday
Test all Day
Just get it done
Art assets?
Code base?
Ask Questions/Get Help
1st Week Demos
Lessons from 1st week• Do anything to get the early games done fast
• Use programmer art or steal assets
• Use open source code if doing tech prototype
• Paper prototyping is ok!
• Don't forget to play test!
Find Creative Solutions
Small Team Management
Deadlines are your friendTest every week, no matter what!
Mon
Brain Storm
Tues
Prototype 1st idea
Wed
Prototype 2nd idea
Thurs
Prototype 3rd idea
Friday
Test!Analyze
Mon
Revise Design
Tues
Prototype Revision
Wed
Prototype Revision
Thurs
Prototype Revision
Friday
TEST!
Analyze Testing Results
>
Take feedback w/grain of salt
Is it viable?
What Changed?
• Keyboard or Xbox controllers
• 1 player or 2 player
• Build with beams, wires, pipes
• Better graphics and animations (some stolen)
• Basic enemy AI and building physics
• Music (stolen) + lots of sound effects
• Multiple levels + level editor (idea from prototype 3)
• Achievements (to impress Dave)
1st Month Demo
Lessons from 2nd Prototype• Test constantly and interpret feedback
• Simple project management, good communication
• Make friends, ask for help, get advice
• Make deadlines + stick to them!
Ways to Prototype
• #1 – The Paper Prototype• #2 – The Web Prototype• #3 – The (Stolen) Tech Prototype• #4 – The Wizard of Oz Prototype
• We'll cover Pros + Cons, Weapons, and Tricks
#1 – The Paper Prototype
• Pros/Cons+ Requires no programming experience
+ Quick to make and iterate on
+ Can be modified on the fly during testing
- Hard to test with multiple users at once (need one prototype per testing session)
- Easy to unintentionally bias testers
- Tends to get unrealistically high praise
#1 – The Paper Prototype
• Weapons
#1 – The Paper Prototype
• Tricks– Shut up during testing! Don't influence!– Use big font + images, roughly 2-3x what
they would be on the screen– The “computer” should be mechanical.
Have a second group member conduct testing.
– Make sure the paper version can be implemented on a computer
#2 – The Web Prototype
• Pros/Cons+ Can be quick and have high fidelity look + feel
+ Can be tested with many users, even remotely
+ Easy to throw out after testing
- Users will focus on layout, not just gameplay
- Limits creativity in design (big problem!)
- Requires someone to know html or other web programming
#2 – The Web Prototype
• WeaponsHTML, CSS, PHP, Javascript, FBML, Flex,
Dreamweaver, Surveymonkey for remote testing
#2 – The Web Prototype
• Tricks– Be aware of reliance on widgets! They
limit design creativity, and will cause your interface to look shitty
– Test like crazy since it is so easy– Use art sketches (.jpgs, .pngs) for
interface elements wherever possible. Even a sketched button is better than a widget button
#3 – The (Stolen) Tech Prototype
• Pros/Cons+ Modding, not coding from scratch
+ Can be VERY high fidelity, highest of all the types of prototypes mentioned here
+ It's hardcore – if you can do this, making the game will be cake
- Easy to get attached to code
- Requires VERY strong coders
#3 – The (Stolen) Tech Prototype
• Weapons– Open Source (Pygame, Box2D, etc.),
existing games with source you can grab, previous projects (ex GAMBIT games?)
#3 – The (Stolen) Tech Prototype
• Tricks– Only attempt if you are really, really
confident in your programming ability.– MUST throw away code at the end– Don't write what you can copy– Do NOT mess with underlying engine
(physics, camera, rendering, etc.)
#4 – The Wizard of Oz Prototype
• Pros/Cons+ Requires little programming knowledge, if
any
+ Can simulate complicated game AI/functionality
= Like a high tech paper prototype
- Testing is slow and requires at least 2 people (probably 3) per session
- May not be possible for every game
#4 – The Wizard of Oz Prototype
• Weapons– Tape recorder/player, instant messenger,
remote/shared control programs
#4 – The Wizard of Oz Prototype
• Tricks– Can be hybridized with other prototyping
methods– Hide the “Wizard” from the tester– Be ready for tech to break– Wizard must be mechanical, and act like a
computer.
Incremental Improvements = Big Progress
Neil Armstrong: “One small step for man, one giant leap for mankind”
Identify + kill bad ideas
Do it now, get it right later
And have fun in the process!
Questions?
www.firehosegames.com