Internal — Dev Team

Cryptid Hotel

Dev Milestone 1 — Base Game Architecture

Version 1.0

Phase Dev M1 — Base Game

Engine Godot 4.6

Date Mar 13, 2026

Dev Milestone 1 — Base Game

Task List

Project Folder Structure

Game Architecture

Base Game Scene

Base Room Grid System

Camera System

Day/Night Cycle System

Move Reception Room Logic from Room.gd

Client Component

Room Component

Room Relation System

Damage System

Requirement System

Aura System

Client Moving System

Client Spawner System

0 / 16 completed

Day/Night Cycle System

Phase	Name	Description
1	Morning — Arrival	A set number of clients spawn at Floor 0 (Reception). Each are unique with their randomized requirements.
2	Day — Assignment	Player assigns clients into rooms (Besides the Reception Room).
3	Night — Resolution	Each client's requirements are evaluated to their current state. Satisfied → reward. Unsatisfied → player takes damage.

!The Day/Night Cycle System is the time keeper that will at specific times do certain actions such as spawning clients or calculating damage for the moment, more to come
!New Clients spawn in the Reception Room, starting from the right towards the left

Requirement & Aura System

Requirements

Likes / Dislikes

Each client has a set of Likes/Hates requirements. A requirement only matters if the client explicitly has it. A client with no opinion on a type is completely unaffected by that type's aura.

Auras

4 Orthogonal Neighbors

Clients and items can emit an aura of a given type. It spreads to the 4 directly adjacent rooms (Up, Down, Left, Right). Diagonals are not affected for now.

All Requirement & Aura Types

🌑 Darkness 👁 Fear 🔊 Noise ❄ Cold 🍖 Hunger 👥 Nearby Clients

✓Satisfaction rule: A client is satisfied only when all of their requirements are fulfilled. A single unmet requirement makes them unsatisfied.
iA Like means the condition must be present in the room. A Hate means it must be absent.
—Auras recalculate whenever a client or room is placed or moved. The Aura System feeds into the Requirement System at resolution time.

Room System

aura

Room ★

aura

Room

Floor 0 — Reception

Occupied room

Aura spread (4 neighbors)

Empty slot

Reception (Floor 0)

Script / System	Responsibility
`room.gd`	Core room node. Holds client references, item slots, room type, and tracks active conditions based on innate properties and received auras.
Room Relation System	Tracks orthogonal adjacency between all placed rooms. Primary source of truth for aura propagation and Nearby Clients checks.
`hotel_grid.gd`	Manages grid placement logic, room validity checks, and the overall hotel shape. Currently also handles reception setup — to be extracted later.
Reception Room	Floor 0 special room. Fixed, not player-modifiable. Spans 3 grid cells. Reception logic currently lives in `hotel_grid.gd` and will be moved to its own file.

Conventions & Guidelines

iAll code, files, and Godot scenes must follow the team conventions documented in the pages linked below. Refer to them before naming anything or structuring a new script.

Guidelines

Coding Conventions

../guidelines-and-normes/coding-conventions.html

Guidelines

File Naming Conventions

../guidelines-and-normes/file-naming-conventions.html

Guidelines

Godot Conventions

../guidelines-and-normes/godot-conventions.html