Script Naming Conventions ​

To ensure clarity and a consistent approach within our projects, we adhere to the following script naming conventions:

1. Specific Object Behaviors ​

Scripts defining behaviors for particular game objects or characters.

Examples:

• PlayerMovement.cs
• EnemyAttack.cs
• DoorInteraction.cs

2. Managers and Handlers ​

Scripts that manage and control various game systems or groups of objects. These scripts often centralize logic for easier management and debugging. Append with a Handler or Manager suffix.

Examples:

• AudioManager.cs
• GameStateHandler.cs
• InventoryManager.cs

3. Utilities and Helpers ​

Scripts that provide utility functions or services to other scripts, not necessarily tied to a specific game object. They may contain reusable logic that doesn't fit within a behavior or manager. Prefix with Utility or Helper.

Examples:

• MathUtility.cs
• StringHelper.cs
• CameraUtility.cs

4. Extensions ​

Extensions specific to specific classes, append with an Extensions suffix.

Examples:

• TransformExtensions.cs
• Vector3Extensions.cs
• GameObjectExtensions.cs