Gaming Day Offset System

Align financial reporting to gaming days with per-location offsets.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/A-Hazzard/Casino-Manangement-System --skill gaming-day-offset-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Gaming Day Offset System
Source: https://github.com/A-Hazzard/Casino-Manangement-System/tree/main/.claude/skills/gaming-day-offset-system
Command: npx skills add https://github.com/A-Hazzard/Casino-Manangement-System --skill gaming-day-offset-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures all CMS financial metrics and reports align to gaming days instead of calendar days, preventing misreporting due to early-morning hours and supporting per-location offsets.

Core Features & Use Cases

  • Gaming day offset per location to align all metrics
  • Default 8 AM start with configurable offset per location
  • Applies gaming-day ranges to dashboards, location/machine reports, and aggregated financial data across all time periods
  • Supports custom date ranges using date-only inputs (YYYY-MM-DD) that respect gaming-day windows
  • Per-location range computation with global aggregation when querying across multiple locations

Quick Start

Configure each location's gameDayOffset and query dashboard totals using timePeriod plus optional startDate and endDate to retrieve gaming-day aligned metrics.

Frequently Asked Questions about Gaming Day Offset System

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align financial reporting with gaming days instead of calendar days?

To align financial reporting with gaming days, apply a default 8 AM offset to location and machine reports. This prevents miscalculation due to time-of-day boundaries and ensures metrics reflect a true gaming day across multiple sites.

Can I configure a custom gaming-day offset for each location?

Yes, you can configure a custom gaming-day offset per location. It enforces a default 8 AM start, supports 0 as a valid offset, and applies the gaming-day ranges to queries via backend utilities and frontend helpers.

How do custom date ranges work with gaming-day aligned reporting?

Custom date ranges use date-only inputs in YYYY-MM-DD format that respect gaming-day windows. The system computes per-location ranges and aggregates them globally when querying financial data across multiple locations.

Why does early-morning financial data appear on the wrong reporting day?

Early-morning financial data appears on the wrong day because calendar-day boundaries split gaming sessions. Applying a gaming-day offset re-aligns these hours to the correct operational day, preventing misreporting across dashboards.

Are collection reports affected by the gaming-day offset calculation?

No, collection reports are excluded from gaming-day calculations. The offset specifically applies to dashboards, location and machine reports, and aggregated financial data to maintain collection reporting accuracy.

What is the best way to align dashboard metrics across multiple timezones?

The best way to align dashboard metrics across multiple timezones is applying per-location gaming-day offsets. This supports global aggregation when querying across multiple locations, ensuring all sites align to their respective gaming days.