Template:Grand Crafting Puzzle Project round 3

=Puzzle Codename: =

Gameplay
{{ifdef|{{{storyboard1|}}}|2=

Step One
frame }} {{ifdef|{{{storyboard2|}}}|2=

Step Two
frame }} {{ifdef|{{{storyboard3|}}}|2=

Step Three
frame }} {{ifdef|{{{storyboard4|}}}|2=

Step Four
frame }} {{ifdef|{{{storyboard5|}}}|2=

Step Five
frame }} {{ifdef|{{{storyboard6|}}}|2=

Step Six
frame }} {{ifdef|{{{storyboard7|}}}|2=

Step Seven
frame }} {{ifdef|{{{storyboard8|}}}|2=

Step Eight
frame }} {{ifdef|{{{storyboard9|}}}|2=

Step Nine
frame }} {{ifdef|{{{storyboard10|}}}|2=

Step Ten
frame }}

Crafting type
Furnishing

Images
{{Usage|1=This template is to be used for submissions in the Grand Crafting Puzzle Project. To use this template, follow the directions below.

First, copy the following template code onto your proposal page:

 {{ Grand Crafting Puzzle Project round 3

 | codename =   | username =   | extra contact = 

 | game concept = 

 | objective = 

 | gameplay = 

 | scoring = 

 | variability = 

 | end criteria = 

 | difficulty scaling = 

 | known problems = 

 | notes = 

 | images = 

 | discussion = 

 }} 

Then, fill in the information specific to your puzzle proposal.

The optional parameters quickstart, quickstarttext, and storyboard do not need to be included. They can be added in at any point and are filled in as follows:

 | quickstart = Name of quickstart image  | quickstarttext = Caption for that image  | storyboard1 = Enter an image name for your storyboard image in the form of Image:Filename  | text1 = Enter text to accompany the image. The template can accommodate up to ten images and text, simply replace 1 with 2, 3, and so on.

The specifics shown in the table below were used to fill in the sample proposal, found at GCPP:Proposal-Shark.

To create additional sections, simply add an appropriate heading. To modify things within the template (such as the order of sections), you will need to substitute the template into your project page by changing the first line to:

 {{subst: Grand Crafting Puzzle Project

then saving the page. This will not change how the page appears, but will make the underlying code more malleable (and for some more confusing).

}}