Rapid, Iterative Prototyping for IGDA 1-27-10
Post on 17-Nov-2014
2979 Views
Preview:
DESCRIPTION
Transcript
Rapid, Iterative Prototyping
What we’re gonna cover
• The prototyping phases– 1st iteration (~ 1 – 2 weeks)– 2nd iteration (~ 1 – 3 months)– Vertical slice
• Lessons learned from prototyping our upcoming game, Slam Bolt Scrappers
• And occasionallydinosaurs
Who Am I?• I'm Eitan!
• AudiOdyssey, Immune Attack
• Loves Ice Hockey
• Founded Fire Hose, new Boston Indie Studio
• Big Nerd
What does prototyping get you?• Can lead to a stronger design + mechanics
• Can save you time in the long run
• Lets you bail on bad ideas sooner
• You'll make more of the costly mistakes up front, when they are easier to fix
• You'll learn how to talk about your game
Starting out
Starting out
PLAYER INVENTORY
2 Programmers/Designers
1 Designer/Business
Small Office
$40,000
+2 Wireless Router of Internet, 50% bonus against Orcs
Starting out• Focus on our strengths, temporarily ignore
our weaknesses
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?
1st Week Demos
1st Round Prototypes• Anything to get it done fast
• Rough or stolen assets OK
• Use open source code
• Paper prototyping is also OK
• Don't forget to play test!
Analyze Testing Results
>
Take feedback with a grain of salt.
Is it viable as a full game?
Start fixing deficiencies
Hire artist
Begin looking for more $$$
Use Tools, Keeping Records
Start With:
Graduate To:
Deadlines are your friendTest every week, no matter what!
Mon
Work on Game
Tues
Work on Game
Wed
Read Comics
Thurs
Work on Game
Friday
TEST!TEST!TEST!
Always have a playable build
Incremental Improvements = Big Progress
Neil Armstrong: “One small step for man, one giant leap for mankind”
Find Creative Solutions
Make friends and ask for help + advice!
Do it now, get it right later
• Stealing is OK early on, but you want to start replacing stolen assets
• Code base can still be throw away
Experiment!
Try out different modes (single vs. multiplayer), big features (AI, physics, networking)
1st and 3rd Month Demos
2nd Round Prototypes• Start covering long term problems (team building, finding money)
• Start using project management tools
• Test constantly, always have playable build, make deadlines and stick to them!
• Focus on incremental improvements
• Make friends, ask for help, get advice
• Just get it done, but start replacing stolen assets
• Experiment with weird ideas!
Build the Vertical Slice
Switch to Real Controls
• No lazy keyboard controls(debugging shortcuts still OK)
(Finally) Start Real Code Base
• Keep overall architecture in mind; you should have a good idea of that by now
Make Tools
• Level Editor, Tools for Artists, Config Files
Identify + kill bad ideas
Start Polishing
Make it Sellable!
Most exciting part of the game, make some marketing materials if you actually have to sell it
Lessons from Vertical Slice• Start building real code base
• Make helpful tools for everyone on the team
• Identify and kill bad ideas quickly and ruthlessly
• Make it look as sexy as possible
• Create something sellable!
When To Stop Prototyping
When you've finished the vertical slice, and it is GOOD, it's time to make the full game!
Prototyping Pitfalls
• Be careful of ballooning scope
• Need to know when to stop prototyping
• Avoid ping pong-ing back and forth
• Still need design doc, asset list
What does prototyping get you?• Can lead to a stronger design + mechanics
• Can save you time in the long run
• Lets you bail on bad ideas sooner
• You'll make more of the costly mistakes up front, when they are easier to fix
• You'll learn how to talk about your game
Closing Thoughts
Please don't sue us Ryan North!
Questions?
eitan@firehosegames.com
www.firehosegames.com
www.slamboltscrappers.com
FB, Twitter: Fire Hose Games
top related