1. Developing Tools for Game Development:
How make tools that support your team.
Daniel Saulnier

2. Who Am I? 6 years at Sheridan
Computer Systems Technician – Software Engineering
Bachelor of Game Design
1 and 1/2 years as a Freelancer in the Game Industry
2 years as an instructor at Hatch Canada
Who Am I?

3. A game development tool is a software that assists or facilitates the making of video games. Some tasks handled by tools include the conversion of assets (such as 3D models, textures, etc.) into formats required by the game, level editing and script compilation.
What Are Tools?

4. Why are Tools Helpful? They Save Time They Save Energy They Save Money
They Make Tasks Easier

5. Example Tool
It is Simple
It succeeded and failed at many the same tasks

6. Don’t reinvent the wheel

7. Don’t reinvent the wheel
Use a tool that does something close to what you need your tool to do.
It is build off of an existing tool then starting from scratch.
If you do need do make the tool from scratch, try and copy the next best thing.

8. Involve your “users”

9. Involve your “users”
The “users” of your tool will be the designers, artists or other programmers
Consider what they want and need and work with them to make a tool they can use and understand.
Many of your “users” won’t be tech-literate and won’t won’t always be direct with feedback.

10. Plan ahead

11. Plan ahead
Know what your tool needs to do ahead of time. And plan how it will support your designs and project.
Tools are directly impacted by the designs they are built to enable.
If you don’t know what you are designing for your tool won’t be successful.

12. Test your workflows early

13. Test your workflows early
Tools should be tested as early as possible. To ensure they work for the tasks you need them to perform.
If the tool is impeding your workflow then you should, change your tool not your workflow. Humans make projects not tools

14. Be prepared to adapt

15. Be prepared to adapt
The unfortunate fact of the matter is that workflows and designs will change over the course of a project.
The tools your design and build should be flexible enough to change to meet these changes
A “bad fix” to a problem is still a fix.

16. Support your tools

17. Support your tools
Make sure you get constant feedback from the people using your tools
As the developer of a tool it is important to make sure your tool is prevent others from working.
Fixing broken tools should take priority over any other task.

18. Plan Ahead
Be prepared the change the tool to the needs of the project
Make sure you are in constant communication with the people using the tool
A broken tool is more of hindrance then no tool
Takeaways

19. Ultimately, creating tools is like working on any other project
Ultimately, creating tools is like working on any other project. If you manage it well it will be successful. If not it will fail to achieve what it was built to do. “Which is to make work easier for everyone else.”