Special folder names under the Unity assets directory

Original: Http://wiki.unity3d.com/index.php/Special_Folder_Names_in_your_Assets_Folder

1. Hide Folders
Folders with a. Start will be ignored by unity. Resources in this folder will not be imported and the script will not be compiled. Also does not appear in Project view.
2.Standard Assets
The script in this folder is first compiled.
The scripts in this folder will be exported to Assembly-csharp-firstpass, Assembly-unityscript-firstpass or Assembly-boo-firstpass projects, depending on the language. Refer to http://docs.unity3d.com/Documentation/Manual/ScriptCompileOrderFolders.html. The script in this folder is compiled first than any other script. Put the script in this folder, you can use C # script to access JavaScript scripts or other language scripts.
3.Pro Standard Assets
Same as standard assets, except that the files in it are for the pro version of Unity.
4.Editor
The folder named in Editor allows the script in it to access the API of Unity Editor. If a class or method in the Unityeditor namespace is used in the script, it must be placed in a folder named editor. Scripts in the Editor folder are not included in the build.
You can have multiple editor folders in your project.
Note: If you are in a normal folder, the Editor folder can be at any level of the directory. If you are in a special folder, the Editor folder must be a direct subdirectory of the special folder.
5.Plugins
The plugins folder is used to put native plugins. They are automatically included in the build. Note This folder can only be a direct subdirectory of the assets folder.
Under the Windows platform, the native plugin is a DLL file; under Mac OS x is the bundle file; under Linux, the. so file.
Like standard assets, the scripts here are compiled earlier, allowing them to be accessed outside the script.
5.1.plugins/x86
If you create a game for a 32bit or 64bit platform, the native plugin file under this folder is automatically included in the game build. If this folder does not exist, unity will look for native pluglins under the Plugins folder.
5.2.plugins/x86_64
If you create a game for a 32bit or 64bit platform, the native plugin file under this folder is automatically included in the game build. If this folder does not exist, unity will look for native pluglins under the Plugins folder.


If you are creating a universal build, it is recommended that you use both folders at the same time. Then put the 32bit and 64bit native plugins into the appropriate folder.
5.3.plugins/android
Put the Java.jar file in this folder. The plugins. So file used in the Java language is also included. Reference http://docs.unity3d.com/Documentation/Manual/PluginsForAndroid.html
5.4.plugins/ios
A limited, simple-to-automatically add (as symbolic Links) any. A,. M.,. mm,. c, or. cpp files into the generated Xcode Project. Seehttp://docs.unity3d.com/documentation/manual/pluginsforios.html
If you need more control how to automatically add files to the Xcode project, you should make use of the POSTPROCESSBUILDP Layer feature. Doing so does don't require you to place such files in the Plugins/ios folder. Seehttp://docs.unity3d.com/documentation/manual/buildplayerpipeline.html


6.Resources
The resources folder allows you to access the resource through the file path and name in the script. However, it is recommended to use direct references to access resources.
The resources placed in this folder are always included in the build, even if it is not used. Because unity cannot tell if the script has access to its resources.
You can have multiple resources folders in your project, so it is not recommended to place a resource with the same name in multiple folders.
Once the build game is in place, all resources in the resource folder are packaged into the archive of the game's storage resources. In this way, the resources folder does not exist in the build of the game. Even though the script still uses the path of the resource in the project. Reference http://docs.unity3d.com/Documentation/Manual/LoadingResourcesatRuntime.html
Note: When a resource is accessed as a script variable, these resources are loaded into memory after the script is instantiated. If the resource is too large, you may not want it to be loaded like this. Then you can put these large resources into the resource folder and load them through resources.load. When these resources are no longer used, you can release the memory by destroy the object and then calling Resources.unloadunusedassets.
7.Editor Default Resources
This is the folder used for the editor script.
8.Gizmos
The Gizmos folder holds the map and icon resources used by the Gizmos.drawicon method. The map resource placed in the Gizmos folder can be used directly by name and can be drawn on the screen by editor as a gizmo.
9.WebPlayerTemplates
The default Web page used to replace the Web build. None of the scripts in this folder will be compiled. This folder must be a direct subdirectory of the assets folder.
10.StreamingAssets
The files here are copied to the build folder and are not modified (the mobile and web versions are different, they are embedded in the final build file). Their paths may vary by platform, but they can be accessed through Application.streamingassetspath.
Refer to Http://docs.unity3d.com/Documentation/Manual/StreamingAssets.html and http://docs.unity3d.com/Documentation/ Scriptreference/application-streamingassetspath.html.


Reference: Http://wiki.unity3d.com/index.php/Special_Folder_Names_in_your_Assets_Folder

(go) Special folder name in Unity assets directory