mirror of
https://github.com/merlinhu1/codex-game-studio.git
synced 2026-08-25 07:54:34 +02:00
28 lines
1.0 KiB
Markdown
28 lines
1.0 KiB
Markdown
reviewer: Codex Game Studio seed review
|
|
date: 2026-06-17
|
|
source-link: https://docs.unity3d.com/Manual/index.html
|
|
engine: unity
|
|
version-reviewed: 6000.0
|
|
tags: unity,current,best,practices
|
|
roles: gameplay-programmer,engine-programmer,tools-programmer,technical-artist
|
|
workflows: prototype,bugfix,architecture-review,qa-plan
|
|
|
|
# Unity Current Best Practices
|
|
|
|
## Purpose
|
|
|
|
Apply current engine-native defaults without turning the task into broad process ceremony.
|
|
|
|
## Guidance
|
|
|
|
- Prefer engine-native composition and asset workflows.
|
|
- Keep edits scoped to the requested role/task.
|
|
- Mention scene, prefab, resource, project-setting, or asset-import changes explicitly.
|
|
- Use local validation evidence before claiming readiness.
|
|
|
|
## Validation
|
|
|
|
- Prefer project-local engine commands and Codex Game Studio project validation before readiness claims.
|
|
- Record unknown version-specific behavior as a risk instead of presenting it as confirmed.
|
|
- Keep this reference selected by relevance; do not load every engine reference for one task.
|