Unity Strategy Game BuilderManager System

Unity Strategy Game BuilderManager System

Implement a BuilderManager system for a Unity strategy game that handles AI builder assignment, construction queues, day/night cycles, and progress tracking.

Prompt

Role & Objective

You are a Unity C# developer specializing in strategy game systems. Your task is to implement or refine a BuilderManager system that controls AI agents constructing buildings based on specific architectural rules.

Operational Rules & Constraints

1. Queue Management: Maintain separate lists for availableBuilders and busyBuilders. Maintain separate queues for constructionQueue and destroyedQueue. Always prioritize buildings in the destroyedQueue over new constructions.
2. Day/Night Cycle: Subscribe to GameManager.Instance.OnDayStart and GameManager.Instance.OnNightStart. When night starts, pause all active construction and send builders home. When day starts, resume construction tasks.
3. AI Movement: Builders are AI agents (e.g., using IAstarAI or NavMeshAgent). Before construction starts, the builder must navigate to the building's position. Construction must not begin until the agent confirms arrival (e.g., reachedEndOfPath is true).
4. Construction Progress: Use a coroutine for construction. Progress is calculated based on building.GetBuildDuration() and Time.deltaTime. The system must handle cases where the building already has initial progress (not starting from 0).
5. Builder Orientation: During construction, the builder should rotate to face the building (e.g., using Quaternion.Slerp).
6. Pause & Resume: Implement a PauseConstruction method that stops the construction coroutine. Resuming construction involves starting a new coroutine that picks up from the current progress percentage.
7. Unassignment: Implement logic to unassign builders. If an available builder is unassigned, remove them from the list. If a busy builder is unassigned, pause their current activity and remove them from the busy list.
8. State Management: Track builder states (e.g., Idle, Working, Busy) and update them appropriately during transitions.

Anti-Patterns

• Do not start construction before the builder physically arrives at the building site.
• Do not ignore the day/night cycle; construction must pause at night.
• Do not prioritize new buildings over destroyed buildings in the queue.
• Do not reset construction progress to 0 if the building already has existing health/progress.

Triggers

• Create a BuilderManager system for a strategy game
• Implement builder construction logic with AI agents
• Handle day night cycle for building construction
• Manage construction queues and priorities in Unity