-
Notifications
You must be signed in to change notification settings - Fork 38
Folder Structure and Naming Conventions
Drew Burden edited this page Apr 26, 2014
·
9 revisions
As of Wed, 19th Feb
- Assets/
- Assets/scenes/ - all scenes go in here
- Assets/scenes/test/ - test scenes
- Assets/fonts/ - fonts folder. If it's a single font just throw it in here
- Assets/scripts/ - most scripts go in here
- Assets/scripts/network/ - networked scripts
- Assets/art/ - all art goes here
- Assets/art/carts/ - all things needed to build a cart go in here. 1 folder per cart
- Assets/art/characters/ - all things needed to build characters go in here. 1 folder per character
- Assets/art/courses/ - all things needed to make the courses go in here
- Assets/art/environment/ - All environmental models like trees and rocks go in here
- Assets/art/terrain/ - all things needed to make a terrain go in here
- Assets/art/materials/ - these need to be moved to whatever they go with...
- Assets/art/ui/ - all UI stuff goes in here
- Assets/resources/ - prefabs only in here
- ProjectSettings/ - settings
If your file is called "test" and your name is "name" then you should name your file "test_name". This applies only to assets that are WIP and/or temporary.
Files should be named to indicate their purpose with the most generic aspects first (so that when lexically sorted, similarly purposed items will appear together) and use "lower camel case" for the non-name portion of files names: eg musicTitle01_jasondesante.wav