HD + Game

Designer's Process

Targets :
- Modify the role of GD
- Improve the working process between GD and the others
- Instruct GD how to proceed
 Content
I. Chart of GD's Process in HD+ team
1. Pre-Alpha flow chart.
2. Alpha flow chart.
3. Beta flow chart.
4. Gold-Candidate flow chart.
II. Guide
1. Write a document
2. Check build
I. Chart of GD's Process
in HD+ team
 Periods of a project

Pre-Alpha Alpha Beta Gold Candidate Gold Release

1 2 3 4 5
1.Pre-Alpha Flow chart
Time to research your game
before the project is started

Producer
Producer HQ/Creation team
- Exchange info
- Confirm game features
Assign projects - Make plan

Lead GD

Assign projects
- Check out svn
- Share data
Game - Share build win32 Developer
Designers Supervisor

- Play full game and check out all Assign tasks

game's features
- Research game's type
- Review game Developers
- Research new platform, device's
info ...

- Build a task list by your own to

follow up what you've done and
report to Lead GD/Prod
 2.Alpha Flow chart
Time to make the game runnable
and be implemented your design

Localization
- Request to translate

Producer
Producer HQ/Creation team
- Confirm GD Documents
- Get and give feedback on designs
Assign projects - Update project's status
- Update project's
status regularly Lead GD
- Get and give Developer
feedback on designs - Follow up Supervisor
- Request to get projects' status
support - Support - Cooperate with the right dev
from the other studio - Share data ( graphic, text ) Separate tasks
Game - Share build win32
Designers
Developers
Specialzed
Lead QA Prepare graphic data tasks :
- Check if the design is rational, Alignment
Artist TnB
according to checklists/rules
Leaderboard
- Make GD documents (1) Achievement
- Present your design and review ...
game to other members of your
project ( QA, Dev, Prod ) (2)
- Prepare graphic data
- Prepare texts used in game

(1) The documents relating to gameplay/UI/ game's behavior

(2) Make a presentation to explain and introduce all game's features as you designed
Mini flowcharts Please keep these points in mind

Work with flash file

●

Game - Share flash file (*)

Developers
Designers

Check out all data from svn Input action scripts

Align UI

Add graphic data for a new

stage, new objects with
“instance name”

(*) GD must use the newest updated file which is well runnable from dev
Mini flowcharts Please keep these points in mind

Work with text file

●
Get translation
Localization
Send translation request

Producer

Get translation Send translation request

- Share text file (*)

Game - Request new text
Developers
Designers

Add new texts Implement into

game
Update/revise texts

(*) GD must use the newest updated file which is well runnable from dev
Important points Please keep these points in mind

Make sure that everyone in your team has your all design documents, it's
●

necessary for :
Prod : to follow up project's status
Dev : to update game design
QA : to check if the design of game has been updated
HOW? Send your newest documents to mail group, ex : WP8-MC4-Project@gameloft.com

Make sure that your design has been implemented completely

HOW? Check one by one with specialized developers. Always remember that there is only
GD having the right to change document and texts used in game

High co-operation with the others

●
 3.Beta Flow chart
Time to check and update your game

Localization
- Request to translate

Producer
Producer HQ/Creation team
- Get/give feedback on designs
- Update project's status

- Update project's
status regularly Lead GD
- Request to get Developer
support - Follow up Supervisor
from the other studio projects' status
- Support - Cooperate with the right dev
- Share data ( graphic, text ) Separate tasks
Game - Share build win32
Designers
Developers
Specialzed
Lead QA Update/make new graphic data tasks :
Alignment
Artist TnB
Check and confirm Leaderboard
- Play game on win32 + device to Achievement
bugs
check your design and game's quality ...
regularly
- Update design if any
- Check bugbase and fix bugs
Mini flowcharts Please keep these points in mind

Check game's quality

●

Producer

- Report your review

- Update design
Update graphic data - Share build
Artist Game
Lead GD Developers
Designers

Play to check game's quality

once every 2 weeks
Mini flowcharts Please keep these points in mind

Check bugbase
●

QA
- Update bugbase
- Send test report via email

Bugbase/test report

Producer Artist
Game Developers
Lead GD
Designers

Daily report Assign

Check bugbage everyday
Check gameplay bugs
Assign
Fix graphic bugs
4.Gold candidate Your game is almost done

Game Designers

Final maintenance
5.Gold release

Good job ya Congratulation!

Yay
II. GUIDE
 1.Write a document
●
Who reads your document?
HQ, producer, clients, developers, artists, QA => they are busy people
●
What is your document for?
To express your ideas and modify game's features
●
What do you need to do for your document?
- Make it clean and clear
- Give full detail
- More figures than texts
- Highlight content
- Scientific layout
●
Quick language check
To avoid language issues such as grammar issues, misspelling, etc, you should double check your document
before sending.
●
Name your document
[GameTitle]_[Type of doc]_[version], ex: MC4_TnB_v0.0.1
●
Save your document
\\sai-data01\Sai Mega\HD+ Mobiles\GD documents\[GAME NAME]
2.Check build
●
What do you need to check in a porting-game?

check

1.Alignment 90% alike master(iPhone)

2.Color 90% alike master(iPhone)

3.Control Play game and see if it's easy to touch/slide, if buttons fit your fingers

4.FPS Is the framerate smooth?

5.Sound Is it too loud or noisy?

6.Behavior Is it inconvenient for user?