Function: each developer may have different experiences and standards when it comes to creating and naming assets. If there is no standardization, other team members may become confused due to the inconsistent formats. This can hinder the process of asset creation and implementation.

Example: let’s consider two game artists assigned to create prop assets. One artist uses English while the other uses Indonesian. One writes “house” while the other writes “rumah.” Without any clarification, it becomes unclear which version of the house asset it is or where the “house” asset should be placed. Now, imagine if there are thousands of assets and each one needs to be opened individually just to determine its purpose. It would consume an entire day’s worth of time.

Solution: lies in establishing a standardized naming convention right from the beginning. By following this convention, the type, function, and placement of an asset can be understood without needing to open the file. This facilitates greater efficiency for all parties involved. For instance, if a developer needs a button asset for their game UI, they can immediately recognize from the code “btn_nor_play_1” that it is the original version of the normal state button. There is no need to open the file to confirm if it is the asset they are looking for.

You can see an example of its usage in the image below: