惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Security Latest
Security Latest
量子位
博客园 - 三生石上(FineUI控件)
小众软件
小众软件
S
SegmentFault 最新的问题
The GitHub Blog
The GitHub Blog
AWS News Blog
AWS News Blog
T
Threat Research - Cisco Blogs
博客园 - Franky
Vercel News
Vercel News
H
Help Net Security
Martin Fowler
Martin Fowler
Security Archives - TechRepublic
Security Archives - TechRepublic
L
LINUX DO - 热门话题
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
L
Lohrmann on Cybersecurity
Cyberwarzone
Cyberwarzone
W
WeLiveSecurity
V2EX - 技术
V2EX - 技术
C
CERT Recently Published Vulnerability Notes
S
Secure Thoughts
C
Cyber Attacks, Cyber Crime and Cyber Security
B
Blog RSS Feed
H
Hacker News: Front Page
P
Proofpoint News Feed
博客园 - 聂微东
N
News and Events Feed by Topic
C
Cybersecurity and Infrastructure Security Agency CISA
D
Docker
博客园_首页
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
人人都是产品经理
人人都是产品经理
The Hacker News
The Hacker News
S
Security @ Cisco Blogs
博客园 - 【当耐特】
F
Fortinet All Blogs
The Register - Security
The Register - Security
A
About on SuperTechFans
D
Darknet – Hacking Tools, Hacker News & Cyber Security
S
Schneier on Security
NISL@THU
NISL@THU
Attack and Defense Labs
Attack and Defense Labs
Help Net Security
Help Net Security
Cisco Talos Blog
Cisco Talos Blog
月光博客
月光博客
IT之家
IT之家
有赞技术团队
有赞技术团队
Know Your Adversary
Know Your Adversary
Hugging Face - Blog
Hugging Face - Blog

Deno

Deno 2.8 | Deno Claw Patrol: an open-source security firewall for agents | Deno Fresh 2.3: Zero JS by default, View Transitions, and Temporal support | Deno Deno 2.7: Temporal API, Windows ARM, and npm overrides | Deno Build a dinosaur runner game with Deno, pt. 6 | Deno Deno Deploy is Generally Available | Deno Introducing Deno Sandbox | Deno Build a dinosaur runner game with Deno, pt. 4 | Deno Build a dinosaur runner game with Deno, pt. 3 | Deno Build a dinosaur runner game with Deno, pt. 2 | Deno React / Next.js Denial-of-Service Vulnerability: Deno Deploy users protected | Deno Deno 2.6: dx is the new npx | Deno Build a dinosaur runner game with Deno, pt. 1 | Deno React Server Functions / Next.js Vulnerability: Deno Deploy users protected | Deno My highlights from the new Deno Deploy | Deno Deno's Other Open Source Projects | Deno How Deno protects against npm exploits | Deno Help Us Raise $200k to Free JavaScript from Oracle | Deno Deno 2.5: Permissions in the config file | Deno Fresh 2.0 Graduates to Beta, Adds Vite Support | Deno Deno 2.4: deno bundle is back | Deno JavaScript™ Trademark Update | Deno What's coming to JavaScript | Deno A brief history of JavaScript | Deno Reports of Deno's Demise Have Been Greatly Exaggerated | Deno An Update on Fresh | Deno How Plaid migrated 100 services to a new database platform 5x faster with Deno | Deno Deno 2.3: Improved deno compile, local npm packages, and more | Deno Add JSR packages with pnpm and Yarn | Deno Zero-config Debugging with Deno and OpenTelemetry | Deno Exploring Art with TypeScript, Jupyter, Polars, and Observable Plot | Deno Deno v Oracle Update 3: Fighting the JavaScript Trademark | Deno Build a custom RAG AI agent in TypeScript and Jupyter | Deno How to get deep traces in your Node.js backend with OTel and Deno | Deno toranoana.deno #20 登録受付中(2025年3月14日) | Deno Node just added TypeScript support. What does that mean for Deno? | Deno The Dino 🦕, the Llama 🦙, and the Whale 🐋 | Deno Publish a lint rule, get a prize | Deno Deno 2.2: OpenTelemetry, Lint Plugins, node:sqlite | Deno If you're not using npm specifiers, you're doing it wrong | Deno How Deno's documentation is evolving | Deno Oracle justified its JavaScript trademark with Node.js—now it wants that ignored | Deno Introducing the JSR open governance board | Deno Intro to Wasm in Deno | Deno Announcing OpenAI on JSR | Deno Deno in 2024 | Deno Goodbye WinterCG, welcome WinterTC | Deno Build a SolidJS app with Deno | Deno Run your Next.js SSR app on Deno Deploy | Deno Solve Advent of Code 2024 with Deno and Win Prizes! | Deno Deno v. Oracle: Canceling the JavaScript Trademark | Deno Deno 2.1: Wasm Imports and other enhancements | Deno Build a Typesafe API with tRPC and Deno | Deno Self-contained Executable Programs with Deno Compile | Deno Build a Database App with Drizzle ORM and Deno | Deno Introducing your new JavaScript package manager: Deno | Deno Announcing Growthbook on JSR | Deno Build an Astro site with Deno | Deno How to convert CommonJS to ESM | Deno Announcing Deno 2 | Deno The Final Touches: What’s New In v2.0.0-rc.10 | Deno Announcing Stable V8 Bindings for Rust | Deno Deno 2.0 Release Candidate | Deno Secure, efficient private npm registries with Cloudsmith and Deno | Deno Painting the Plane as We Fly It: Designing JSR | Deno Introducing Web Cache API support on Deno Deploy | Deno Deno 1.46: The Last 1.x Release | Deno Protect your cloud spend with new Deno Deploy spend limits | Deno What we got wrong about HTTP imports | Deno Benchmarking AWS Lambda Cold Starts Across JavaScript Runtimes | Deno Announcing Supabase on JSR | Deno Deno 1.45: Workspace and Monorepo Support | Deno Introducing KV Backup for Deno Subhosting | Deno A Gentle Intro to TypeScript | Deno Announcing Hono on JSR | Deno How We Made the Deno Language Server Ten Times Faster | Deno How the Guardian uses Deno to audit accessibility and performance across their 2.7 million articles | Deno Introducing More Flexible Domain Association for Deno Subhosting | Deno The stabilization process of the Standard Library has begun | Deno Deno 1.44: Private npm registries, improved Node.js compat, and performance boosts | Deno How we built a secure, performant, multi-tenant cloud platform to run untrusted code | Deno The Deno Standard Library is now available on JSR | Deno How to document your JavaScript package | Deno Your Low Code Solution Needs an Escape Hatch | Deno Deno 1.43: Improved Language Server performance | Deno How Slack used Deno to save months of engineering effort in launching their new platform | Deno JSR Is Not Another Package Manager | Deno Announcing the Hookdeck SDK on JSR | Deno Announcing the Neon Serverless Driver on JSR | Deno An intro to TSConfig for JavaScript Developers | Deno How we built JSR | Deno How Netlify used Deno Subhosting to build a successful edge functions product | Deno Introducing Simpler Project Creation in Deno Deploy | Deno Deno 1.42: Better dependency management with JSR | Deno Introducing deployctl, the command line interface for Deno Deploy | Deno Introducing JSR - the JavaScript Registry | Deno How to add Monaco to a Next.js app and securely run untrusted user code | Deno Survey Results and Roadmap | Deno Deno 1.41: smaller deno compile binaries | Deno Webhooks suck, but here are alternatives | Deno
Build a dinosaur runner game with Deno, pt. 5 | Deno
Jo Franchett · 2026-02-09 · via Deno

This series of blog posts will guide you through building a simple browser-based dinosaur runner game using Deno.

  1. Setup a basic project
  2. Game loop, canvas, and controls
  3. Obstacles and collision detection
  4. Databases and global leaderboards
  5. Player profiles and customization
  6. Observability, metrics, and alerting

Player Profiles & Customization

In Stage 4, we wired Oak, PostgreSQL, and a leaderboard route so every run could be recorded. The UI was still anonymous though: everyone shared the same dino, the same desert background, and you had to hard refresh the page each time you wanted to switch difficulty. In Stage 5, we’ll keep that leaderboard code, but layer on player identity and customization so the experience matches what ships in the game-tutorial-stage-4 repository.

What you’ll build

By the end of this stage you will have:

  • Added player-name and customization modals to public/index.html.
  • Styled those surfaces with reusable modal utilities in public/css/styles.css.
  • Extended public/js/game.js with a settings lifecycle: prompt for a name, load cached preferences, sync with the server, and apply themes/difficulty multipliers instantly.
  • Created players, player_settings, and high_scores tables plus the /api/customization endpoints that persist those choices in PostgreSQL.
  • Verified the global leaderboard page now reflects the player’s chosen name, color, and score in real time.

1. Upgrade the UI with identity & customization controls

Start by extending the markup in public/index.html. We add three things near the game canvas:

  1. A “Customize Game” button so players can open the modal mid-run.
  2. A player-name modal that appears the first time someone loads the page.
  3. A customization modal that exposes color, theme, and difficulty controls.

public/index.html

<section class="container canvas-container">
  <canvas id="gameCanvas" width="800" height="220"></canvas>
  <div class="game-ui">
    <div class="score">Score: <span id="score">0</span></div>
    <div class="high-score">High Score: <span id="highScore">0</span></div>
    <div class="btn btn-primary" id="gameStatus">Click to Start!</div>
  </div>
  <button onclick="openCustomization()" class="btn btn-primary btn-block">
    Customize Game
  </button>
</section>


<div class="modal" id="playerModal">
  <div class="modal-content">
    <h3>🎮 Welcome to Dino Runner!</h3>
    <p>Enter your name to save scores and compete on the global leaderboard:</p>
    <input
      type="text"
      id="playerNameInput"
      placeholder="Your name"
      maxlength="20"
    />
    <div class="modal-buttons">
      <button onclick="savePlayerName()" class="btn btn-primary">
        Save &amp; Play
      </button>
      <button onclick='closeModal("playerModal")' class="btn btn-secondary">
        Play Anonymous
      </button>
    </div>
  </div>
</div>


<div class="modal" id="customizationModal">
  <div class="modal-content">
    <h3>🎨 Customize Your Game</h3>
    <div class="customization-options">
      <div class="option-group">
        <label for="dinoColorPicker">Dino Color:</label>
        <input type="color" id="dinoColorPicker" value="#4CAF50" />
      </div>
      <div class="option-group">
        <label for="backgroundTheme">Background Theme:</label>
        <select id="backgroundTheme">
          <option value="desert">🏜️ Desert</option>
          <option value="forest">🌲 Forest</option>
          <option value="night">🌙 Night</option>
          <option value="rainbow">🌈 Rainbow</option>
          <option value="space">🚀 Space</option>
        </select>
      </div>
      <div class="option-group">
        <label for="difficultyPreference">Difficulty:</label>
        <select id="difficultyPreference">
          <option value="easy">😊 Easy</option>
          <option value="normal">😐 Normal</option>
          <option value="hard">😈 Hard</option>
        </select>
      </div>
    </div>
    <div class="modal-buttons">
      <button onclick="saveCustomization()" class="btn btn-primary">
        Save Changes
      </button>
      <button
        onclick='closeModal("customizationModal")'
        class="btn btn-secondary"
      >
        Cancel
      </button>
    </div>
  </div>
</div>

The modal triggers call helper functions we’ll add in game.js so there’s no framework dependency—plain DOM APIs keep things deploy-friendly.

2. Style the modal surfaces

Layer in the modal utility classes inside public/css/styles.css. They reuse the existing btn palette from earlier stages, so everything feels cohesive.

public/css/styles.css

.modal {
  display: none;
  position: fixed;
  top: 0;
  left: 0;
  width: 100%;
  height: 100%;
  background: rgba(0, 0, 0, 0.5);
  z-index: 1000;
  animation: fadeIn 0.3s ease;
}

.modal.show {
  display: flex;
  justify-content: center;
  align-items: center;
}

.modal-content {
  background: white;
  border: 2px solid var(--secondary);
  padding: 2rem;
  max-width: 500px;
  width: 90%;
  box-shadow: 4px 8px 0px 0px var(--tertiary);
  animation: slideIn 0.3s ease;
}

.customization-options {
  margin-bottom: 1.5rem;
}

.option-group label {
  display: block;
  margin-bottom: 0.5rem;
  font-weight: 500;
}

.option-group select,
.option-group input[type="color"] {
  width: 100%;
  padding: 0.75rem;
  border: 1px solid var(--secondary);
}

Feel free to tweak the palette! The logic we’ll add next pulls the chosen colors right into the canvas background and dino sprite.


3. Teach game.js to orchestrate settings

With the UI in place we can extend the DinoGame class inside public/js/game.js, the key additions are:

  • tracked playerName, settings, and theme definitions.
  • lifecycle methods (showPlayerNamePrompt, loadPlayerSettings, applyCustomizations, savePlayerSettings).
  • global helpers (openModal, closeModal, saveCustomization, etc.) so the HTML buttons can talk to the class without bundlers.

Constructor upgrades

public/js/game.js

class DinoGame {
  constructor() {
    this.canvas = document.getElementById("gameCanvas");
    this.ctx = this.canvas.getContext("2d");
    this.scoreElement = document.getElementById("score");
    this.statusElement = document.getElementById("gameStatus");
    this.highScoreElement = document.getElementById("highScore");

    this.playerName = localStorage.getItem("playerName") || null;
    this.settings = {
      dinoColor: "#4CAF50",
      backgroundTheme: "desert",
      soundEnabled: true,
      difficultyPreference: "normal",
    };

    this.themes = {
      desert: { sky: "#87CEEB", ground: "#DEB887" },
      forest: { sky: "#98FB98", ground: "#228B22" },
      night: { sky: "#191970", ground: "#2F4F4F" },
      rainbow: { sky: "#FF69B4", ground: "#FFD700" },
      space: { sky: "#000000", ground: "#696969" },
    };

    this.init();
  }

Now you can customize the game's colors

Prompt for a player name

showPlayerNamePrompt() looks for saved state; if none is found it opens the modal and focuses the input.

public/js/game.js

showPlayerNamePrompt() {
  if (!this.playerName || this.playerName === "" || this.playerName === "null") {
    setTimeout(() => {
      const modal = document.getElementById("playerModal");
      if (modal) {
        window.openModal("playerModal");
        const input = document.getElementById("playerNameInput");
        if (input) {
          input.focus();
          input.addEventListener("keypress", this.handlePlayerNameEnter);
        }
      }
    }, 1000);
  }
}

The name prompt

Load, apply, and save settings

Once a player name exists we look up settings on the server, fall back to localStorage, and immediately apply the palette + difficulty multipliers.

public/js/game.js

async loadPlayerSettings() {
  try {
    if (this.playerName) {
      const response = await fetch(`/api/customization/${this.playerName}`);
      if (response.ok) {
        const data = await response.json();
        this.settings = data.settings;
        this.applyCustomizations();
      }
    } else {
      const savedSettings = localStorage.getItem("gameSettings");
      if (savedSettings) {
        this.settings = { ...this.settings, ...JSON.parse(savedSettings) };
        this.applyCustomizations();
      }
    }
  } catch (error) {
    console.log("Using default settings:", error);
  }
}

applyCustomizations() {
  const theme = this.themes[this.settings.backgroundTheme] || this.themes.desert;
  this.canvas.style.background = `linear-gradient(to bottom, ${theme.sky} 0%, ${theme.sky} 75%, ${theme.ground} 75%, ${theme.ground} 100%)`;

  const multipliers = { easy: 0.8, normal: 1.0, hard: 1.3 };
  this.initialGameSpeed = 3 * (multipliers[this.settings.difficultyPreference] || 1.0);
  this.gameSpeed = this.initialGameSpeed;

  console.log(`🎨 Applied theme: ${this.settings.backgroundTheme}, difficulty: ${this.settings.difficultyPreference}`);
}

async savePlayerSettings() {
  if (this.playerName) {
    await fetch("/api/customization", {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({ playerName: this.playerName, ...this.settings }),
    });
  } else {
    localStorage.setItem("gameSettings", JSON.stringify(this.settings));
  }
}

Global helpers for the modals

Instead of wiring everything through class instances, game.js exposes a few functions on window. They open/close modals, persist names, and populate the customization controls.

public/js/game.js

window.openModal = function (modalId) {
  const modal = document.getElementById(modalId);
  if (modal) {
    modal.classList.add("show");
    modal.style.display = "flex";
  }
};

window.saveCustomization = function () {
  const colorPicker = document.getElementById("dinoColorPicker");
  const themeSelect = document.getElementById("backgroundTheme");
  const difficultySelect = document.getElementById("difficultyPreference");

  if (window.dinoGame) {
    window.dinoGame.settings = {
      ...window.dinoGame.settings,
      dinoColor: colorPicker?.value || window.dinoGame.settings.dinoColor,
      backgroundTheme: themeSelect?.value ||
        window.dinoGame.settings.backgroundTheme,
      difficultyPreference: difficultySelect?.value ||
        window.dinoGame.settings.difficultyPreference,
    };

    window.dinoGame.applyCustomizations();
    window.dinoGame.savePlayerSettings();
  }

  window.closeModal("customizationModal");
};

Hook everything up inside window.addEventListener("load", ...) so the health check runs, the DinoGame instance is created, and your modals are ready the moment the DOM finishes loading.


4. Persist player choices in PostgreSQL

Stage 4 already introduced a database connection pool, migrations runner, and a high_scores table. To store customization data we add players and player_settings tables to src/database/schema.sql:

CREATE TABLE IF NOT EXISTS players (
  id SERIAL PRIMARY KEY,
  username VARCHAR(50) UNIQUE NOT NULL,
  email VARCHAR(100) UNIQUE,
  avatar_url TEXT,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE TABLE IF NOT EXISTS player_settings (
  id SERIAL PRIMARY KEY,
  player_id INTEGER REFERENCES players(id) ON DELETE CASCADE,
  dino_color VARCHAR(7) DEFAULT '#4CAF50',
  background_theme VARCHAR(20) DEFAULT 'desert',
  sound_enabled BOOLEAN DEFAULT true,
  difficulty_preference VARCHAR(20) DEFAULT 'normal',
  updated_at TIMESTAMP DEFAULT NOW(),
  UNIQUE(player_id)
);

high_scores still stores anonymous runs (player_name), but if someone has a registered player_id we can connect their customization + leaderboard data in one query.


5. Expose /api/customization routes

All API logic lives in src/routes/customization.routes.ts. We reuse the ctx.state.db pool set by middleware, so every handler can grab a client from the pool, execute queries, and release connections.

src/routes/customization.routes.ts

import { Router } from "@oak/oak";

const router = new Router();

router.get("/api/customization/:playerName", async (ctx) => {
  const pool = ctx.state.db;
  const playerName = ctx.params.playerName;
  let settings = {
    dinoColor: "#4CAF50",
    backgroundTheme: "desert",
    soundEnabled: true,
    difficultyPreference: "normal",
  };

  const client = await pool.connect();
  try {
    const playerResult = await client.query(
      `SELECT id FROM players WHERE username = $1`,
      [playerName],
    );

    if (playerResult.rows.length > 0) {
      const playerId = Number(playerResult.rows[0].id);
      const settingsResult = await client.query(
        `SELECT dino_color, background_theme, sound_enabled, difficulty_preference
         FROM player_settings WHERE player_id = $1`,
        [playerId],
      );

      if (settingsResult.rows.length > 0) {
        const row = settingsResult.rows[0];
        settings = {
          dinoColor: row.dino_color,
          backgroundTheme: row.background_theme,
          soundEnabled: row.sound_enabled,
          difficultyPreference: row.difficulty_preference,
        };
      }
    }
  } finally {
    client.release();
  }

  ctx.response.body = { success: true, playerName, settings };
});

router.post("/api/customization", async (ctx) => {
  const pool = ctx.state.db;
  const body = await ctx.request.body.json();
  const {
    playerName,
    dinoColor,
    backgroundTheme,
    soundEnabled,
    difficultyPreference,
  } = body;

  const client = await pool.connect();
  try {
    const playerResult = await client.query(
      `INSERT INTO players (username) VALUES ($1)
       ON CONFLICT (username) DO UPDATE SET updated_at = NOW()
       RETURNING id`,
      [playerName],
    );

    const playerId = Number(playerResult.rows[0].id);

    await client.query(
      `INSERT INTO player_settings (player_id, dino_color, background_theme, sound_enabled, difficulty_preference)
       VALUES ($1, $2, $3, $4, $5)
       ON CONFLICT (player_id) DO UPDATE SET
         dino_color = $2,
         background_theme = $3,
         sound_enabled = $4,
         difficulty_preference = $5,
         updated_at = NOW()`,
      [
        playerId,
        dinoColor,
        backgroundTheme,
        soundEnabled,
        difficultyPreference,
      ],
    );
  } finally {
    client.release();
  }

  ctx.response.body = {
    success: true,
    message: "Customization settings saved successfully",
  };
});

export { router as customizationRoutes };

There’s also a simple /api/customization/options handler that returns available themes, colors, and difficulty presets for future UI work.

Screenshot of the customization modal


6. Serve everything with Oak

The rest of the backend is Oak boilerplate. src/middleware/database.ts attaches the pool to every request. src/main.ts initializes the schema, registers middleware, and mounts the routers before falling back to the static file server:

src/main.ts

import { Application } from "@oak/oak/application";
import { apiRouter } from "./routes/api.routes.ts";
import { leaderboardRoutes } from "./routes/leaderboard.routes.ts";
import { customizationRoutes } from "./routes/customization.routes.ts";
import { databaseMiddleware } from "./middleware/database.ts";
import { initializeDatabase } from "./database/migrations.ts";

await initializeDatabase();

const app = new Application();
app.use(databaseMiddleware);

app.use(async (context, next) => {
  try {
    if (context.request.url.pathname === "/leaderboard") {
      await context.send({
        root: `${Deno.cwd()}/public`,
        path: "leaderboard.html",
      });
      return;
    }

    await context.send({ root: `${Deno.cwd()}/public`, index: "index.html" });
  } catch {
    await next();
  }
});

app.use(apiRouter.routes());
app.use(leaderboardRoutes.routes());
app.use(customizationRoutes.routes());

app.listen({ port: PORT });

With those pieces in place the leaderboard API, customization API, and static assets all share a single Deploy project (or run locally via deno task dev).


7. Exploring your databases with Deno Deploy

You can view and edit your PostgreSQL databases directly from the Deno Deploy dashboard. This is especially useful for inspecting the players, player_settings, and high_scores tables as you test your game. To access the database:

  1. Go to your Deno Deploy project dashboard and log in.
  2. Click on the “Apps” tab and select your game project.
  3. Navigate to the “Databases” section in the sidebar. Here you can see a list of your databases, a production database, a preview database and a database you can use for local testing.
  4. Click the Explore button on the database you want to explore (e.g., the production database).
  5. From here you can search and edit your tables to inspect player data, scores, and settings.

Screenshot of the Deno Deploy database explorer

8. Validate the full loop

At this point you should have a fully functional game with player identities, customizable themes, and persistent preferences. To validate everything is wired up correctly:

  • Run deno task dev (or deno run --allow-net --allow-read --allow-env --env-file src/main.ts) inside game-tutorial-stage-4.
  • Open localhost and enter a name when prompted.
  • Customize the color/theme/difficulty, then start a run. When you crash the game, the POST /api/scores handler records the attempt, while POST /api/customization persists your palette.
  • Visit /leaderboard (served via public/leaderboard.html) and watch public/js/leaderboard.js call /api/leaderboard?limit=50 every 30 seconds.
  • Reload the main page—your dino should immediately apply the stored palette and speed multiplier fetched from /api/customization/:playerName.

Screenshot of the now global leaderboard

You can explore the full reference implementation and Deploy link here: https://game-tutorial-stage-4.thisisjofrank.deno.net/

Stage 5 accomplishments

  • ✅ Player-name prompt and customization modal wired directly into the game UI.
  • ✅ Responsive modal styles that reuse the existing Stage 2–4 design system.
  • game.js settings lifecycle: fetch, apply, persist, and rehydrate themes plus difficulty multipliers.
  • ✅ PostgreSQL schema + Oak routes that store both scores and preferences.
  • ✅ Leaderboard page that reflects personalized player identities in real time.

What’s next?

Stage 6 will concentrate on observability—metrics, logging, and alerting—so you can understand how players behave at scale. We’ll wire up structured logs, shipping analytics events, and dashboards that track leaderboard health and customization adoption. For now, enjoy the custom player experience you just delivered! 🦕✨

What else are you building with Deno? Let us know on Twitter, Bluesky, or Discord.