How do you document levels in game design?

1 Why document levels?

Documenting levels is important for several reasons. First, it helps you clarify your design goals, challenges, and solutions. Second, it helps you track your progress, identify issues, and make changes. Third, it helps you share your work with others, such as programmers, artists, sound designers, testers, and publishers. Fourth, it helps you create a portfolio of your level design skills and showcase your creativity.

2 What to document?

Documenting levels does not have to be a one-size-fits-all approach. Generally, it should include a high-level overview of the level's theme, genre, setting, mood, and story. Additionally, it should have a detailed breakdown of the level's structure, flow, logic, and mechanics. This can be supported by visual representation such as sketches, maps, diagrams, or screenshots. Furthermore, the level's assets should be described in detail including models, textures, sounds, and scripts. It is also important to list the level's requirements such as performance, accessibility, and compatibility. Lastly, the level's feedback should be summarized such as playtesting results, bug reports, and user reviews.

3 How to document levels?

When it comes to documenting levels, there are many tools and methods available. Commonly used options include word processors like Google Docs or Microsoft Word, spreadsheets such as Google Sheets or Microsoft Excel, presentation software like Google Slides or Microsoft PowerPoint, drawing software like Adobe Photoshop or Sketch, level editors like Unity or Unreal Engine, and version control systems such as Git or SVN. These tools can help you write text documents, create tables and charts, make slideshows and videos, create sketches and diagrams, build and test levels, and manage and share files.

4 When to document levels?

Documenting levels is an ongoing process that should begin at the early stages of development and continue until the final release. The amount and type of documentation can depend on the project's scope, scale, and stage. For instance, during the pre-production phase, you may want to document your level's concept, vision, and scope. When in production, you may need to document the design, development, and testing. Lastly, for post-production, you may need to document your level's polish, optimization, and launch.

5 Where to document levels?

Documenting levels can be done in a variety of places and formats, depending on your preferences and needs. For example, you can store local files, such as documents, spreadsheets, and images, on your computer or external drive. Alternatively, you can use online platforms like Google Drive or Dropbox for storing and accessing files on the cloud. Wikis like Confluence or MediaWiki allow you to create and edit web pages with rich content and links. Blogs such as WordPress or Medium are great for publishing and sharing your level design process and insights. And portfolios such as ArtStation or Behance are perfect for showcasing and promoting your level design work and skills.

6 Who to document levels for?

Documenting levels can be a useful tool for a variety of purposes and audiences, depending on your goals and context. For instance, you can document levels for yourself to better organize your thoughts and refine your ideas. Additionally, you can document levels for your team to collaborate effectively and coordinate your level design work. Furthermore, documenting levels for clients can help you pitch, demonstrate, and deliver your level design services. Finally, documenting levels for players can help you inform, instruct, and entertain them with your level design.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?