{"id":98,"date":"2025-04-22T09:40:45","date_gmt":"2025-04-22T09:40:45","guid":{"rendered":"https:\/\/myuberconcept.com\/?p=98"},"modified":"2025-06-25T13:05:37","modified_gmt":"2025-06-25T06:05:37","slug":"how-to-manage-game-asset-in-a-game-design-document","status":"publish","type":"post","link":"https:\/\/myuberconcept.com\/index.php\/2025\/04\/22\/how-to-manage-game-asset-in-a-game-design-document\/","title":{"rendered":"How to Manage Game Asset in a Game Design Document"},"content":{"rendered":"

Function<\/strong><\/h2>\n

In game development, team members often come from different backgrounds and may use varying formats when creating and naming assets. Without a standardized naming convention, inconsistencies can cause confusion, slow down production, and create unnecessary bottlenecks during asset implementation.<\/p>\n

Problem<\/strong><\/h2>\n

Let\u2019s say two game artists are tasked with creating prop assets. One names a file \u201chouse\u201d in English, while the other names it \u201crumah\u201d in Indonesian. Without a shared naming system, it\u2019s unclear whether these refer to the same asset, different versions, or where each should be placed. Now scale that problem to a library of thousands of assets. Verifying each one manually would take hours or even days wasting valuable development time.<\/p>\n

Solution<\/strong><\/h2>\n

The key is to define and enforce a clear naming convention from the start. A good naming system allows any team member to understand an asset\u2019s type, function, and purpose at a glance without opening the file.<\/p>\n

For example, a UI asset named btn_nor_play_1<\/code> immediately communicates that it\u2019s a button (btn<\/code>), in its normal state (nor<\/code>), associated with the play action (play<\/code>), and it’s version 1. This level of clarity boosts productivity, minimizes miscommunication, and keeps pipelines running smoothly.<\/p>\n

See the image below for a visual example of how this standard can be applied.<\/p>\n

\"\"<\/p>\n

View full size<\/a><\/p>\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Function In game development, team members often come from different backgrounds and may use varying formats when creating and naming assets. Without a standardized naming convention, inconsistencies can cause confusion, slow down production, and create unnecessary bottlenecks during asset implementation. Problem Let\u2019s say two game artists are tasked with creating prop assets. One names a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[4,5],"class_list":["post-98","post","type-post","status-publish","format-standard","hentry","category-1","tag-gamedesign","tag-gamedesigndocument"],"_links":{"self":[{"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/posts\/98","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/comments?post=98"}],"version-history":[{"count":5,"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/posts\/98\/revisions"}],"predecessor-version":[{"id":953,"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/posts\/98\/revisions\/953"}],"wp:attachment":[{"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/media?parent=98"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/categories?post=98"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/myuberconcept.com\/index.php\/wp-json\/wp\/v2\/tags?post=98"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}