What problem does it solve?
This Skill helps design and implement a unified time-of-day and weather layer for games, so clocks, skies, storms, seasons, and gameplay effects stay consistent instead of drifting, popping, or desynchronizing.
Core Features & Use Cases
- Clock Architecture: Defines a monotonic game clock, day phases, calendars, seasonal cycles, and server-versus-diegetic time models.
- Weather Systems: Covers weather as authored data, pre-rolled schedules, override stacks, and simulation-driven alternatives like volumetric clouds and dynamic storms.
- Gameplay Consumers: Shows how AI, combat, survival temperature, spawn windows, and event schedulers read time and weather without polling raw state.
- Rendering Integration: Explains how to keep lighting, sky, fog, precipitation, wetness, and global parameter buses coherent across transitions.
- Use Case: If your game has rain that never stops, a sun that jitters after long sessions, or quests that break across midnight, this Skill provides the architecture to fix it.
Quick Start
Ask for a system design for your game’s day-night, weather, and scheduler pipeline, including clock representation, weather state transitions, gameplay consumers, and rendering integration.
