Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/VasquezRivero92/HabboCafe/llms.txt

Use this file to discover all available pages before exploring further.

A Dado is an independent tournament environment — a self-contained group where a set of Habbo Hotel players compete against each other on their own leaderboard. Every Dado runs in complete isolation: its scores, roster, configuration, and staff have no effect on any other Dado running simultaneously on the platform. Think of a Dado as a private tournament room that the Global Admin creates and hands off to a dedicated administrator.

​
What a Dado contains

Each Dado document in Firestore stores everything needed to run a tournament independently:
FieldTypeDescription
idstringAuto-generated Firestore document ID
namestringHuman-readable display name shown in the navbar (e.g. “Dado VIP”)
codestring?Optional short code for the Dado
adminIdstring?UID of the dado_admin user assigned to manage this Dado
adminEmailstring?Email of the assigned Dado Admin (stored for display)
adminNamestring?Habbo username of the assigned Dado Admin (shown in the Staff tab)
createdAtstringISO 8601 timestamp of when the Dado was created
startDatestring?Tournament start date in YYYY-MM-DD format
endDatestring?Tournament end date in YYYY-MM-DD format
rulesstring[]?Ordered list of rule strings shown in the Reglas info tab
schedulestring[]?Ordered list of schedule strings shown in the Fecha y horarios tab
totalPrizestring?Prize pool description displayed on the tournament info panel (e.g. “3000 USDT”)
qualifyingCountnumber?Number of top-ranked players who qualify for the final round (default: 12)

​
The Dado lifecycle

1

Global Admin creates the Dado

From the Global Panel tab, the Global Admin enters a name and clicks Generar Dado. A new Firestore document is created in the dados collection. The Dado starts with no admin, no players, and no tournament configuration.
2

A Dado Admin is assigned

Still in the Global Panel, the Global Admin selects any registered user from the assignment dropdown next to the Dado and submits. The platform writes adminId, adminEmail, and adminName onto the Dado document and promotes that user’s role to dado_admin in Firestore — all in a single atomic batch write.
3

Players are added to the roster

The Dado Admin (or an Intermediario) opens the leaderboard tab, clicks Crear Usuario, and enters the player’s Habbo nickname. The new user document is created with dadoId set to this Dado’s ID and role set to jugador. The player immediately appears on the leaderboard.
4

Tournament is configured and runs

The Dado Admin sets the startDate, endDate, totalPrize, qualifyingCount, rules, and schedule from the Dado Panel tab. Intermediarios load points throughout the tournament period and the leaderboard updates in real time.
5

Tournament is reset for the next edition

When the current tournament ends, the Dado Admin triggers Crear Nuevo Torneo (Reiniciar). All player scores are zeroed, dates are updated, and rank counters are reset to 1 — the roster stays intact and a fresh tournament begins immediately.

​
How players belong to a Dado

Every player (jugador) is linked to a specific Dado through the dadoId field on their HabboUser profile document in Firestore. When the platform queries a Dado’s leaderboard, it runs a Firestore query scoped to all users documents where dadoId == <dado.id>. A player without a dadoId — or one that does not match any active Dado — will see a warning prompting them to ask an administrator to register them. Intermediarios and Dado Admins share this same dadoId binding, which ensures that all point operations and role changes they perform are automatically scoped to the correct Dado. 
// Firestore query used to fetch a Dado's player list
const qUsers = query(
  collection(db, 'users'),
  where('dadoId', '==', targetDadoId)
);
The Global Admin has no dadoId restriction and can switch between all existing Dados using the Ver Dado dropdown in the top navbar. Selecting a different Dado immediately reloads the leaderboard, staff list, and admin panel for that environment — no page refresh required.

​
Multiple Dados running simultaneously

HADOS is designed to run any number of Dados in parallel. Each Dado maintains its own isolated Firestore listener, so score updates in one Dado never affect another. This makes it straightforward to operate, for example, a Dado VIP, a Dado Principiantes, and a Dado Mensual at the same time — each with its own administrator, ruleset, and prize pool.

Build docs developers (and LLMs) love

Get started for freeTalk to us