Skip to content
TheChatArchiveThe Chat Archive
Geminigemini-2.0-flash-grounding· GoogleHugging Face LMArena Search Arena 24K

What are the best practices to follow when organizing assets for your Unity project?

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with gpt-4o-search-preview-high’s answer.
  1. User

    What are the best practices to follow when organizing assets for your Unity project?

  2. Gemini Assistant

    Here are the best practices to follow when organizing assets for your Unity project, based on the provided search results:

    I. General Principles:

    • Consistency: Stick to a defined style guide and project template to make files easier to locate and organize.[[1]]
    • Naming Conventions:
      • Be consistent with your naming conventions.[[1]][[2]]
      • Avoid spaces in file and folder names.[[1]][[3]][[4]] Use CamelCase as an alternative.[[1]]
      • Use PascalCase for custom file- and folder names.[[3]]
      • Keep the most specific descriptor on the left (e.g., DarkVampire, not VampireDark).[[3]]
      • For sequences, use numbers, starting with 0 (e.g., PathNode0, PathNode1).[[3]]
      • Avoid special characters such as *()?[[2]] "#$.
    • Folder Structure: Use a basic folder structure and build upon that as the project expands.[[4]]
    • Project Root: Store your content files within the Assets folder.[[1]] Avoid extra folders at the project's root level unless absolutely necessary.[[1]] You can add a root folder named after your game to keep your project files separate from third-party assets.[[5]] Adding an underscore to the start of your game's root folder places it at the top and helps to keep files separate from third-party asset files.[[5]]
    • Version Control: Use a version control system (e.g., Anchorpoint, Unity Version Control, Git) to back up current and previous versions.[[4]]
    • Documentation: Document your naming conventions and folder structure.[[1]]

    II. Folder Structure and Organization:

    • Separate Folders:
      • Separate internal assets from third-party ones (Asset Store assets, plugins).[[1]]
      • Create a separate folder for non-production scenes and experimentation.[[1]]
      • Divide work areas by team member using subfolders with usernames.[[1]]
      • Keep a clear separation between Art, Scripting, Prefabs, and Scenes, along with Audio and Asset Packs/Plugins.[[4]]
    • Asset Type Subfolders: Organize subfolders by asset type (e.g., Audio, Materials, Textures, Models, Scripts, Prefabs, Scenes).
    • Consistent Structure: Create the same folder structure for all projects.

    III. Specific Asset Types:

    • Materials: Organize and name the materials in your Scene.
    • Textures: Store your output Texture files together in your Unity project (e.g., in \Assets\textures).[[2]]

    IV. Working with Assets:

    • Prefabs: Prefab everything.[[3]] To modify an asset from the store, drag it into the hierarchy and create a prefab inside _Project.[[3]]
    • Asset Store Assets: Leave complex asset package files where they are imported by default to make updating easier.[[3]] When making modifications, copy the file(s) you want to modify to an appropriate subfolder in _Project, make changes only to that copy, and make the other parts reference the newly created, modified file.[[3]]
    • Scenes: Name objects in your Scene sensibly and uniquely.

    V. In-Scene Organization

    • Empty Game Objects as Folders: Use empty game objects as folders to group objects in the hierarchy.[[5]]

    By following these best practices, you can maintain a clean, organized, and efficient Unity project, making it easier to navigate, collaborate, and manage your assets effectively.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.