> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/tutorials-and-examples/published-games/sky-chaser.md).

# Sky Chaser

Multiplayer package-catching rounds with persistent leaderboards, pooled projectiles, and pickup placement seeded from round state.

![Sky Chaser preview](https://45449780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoPnXBby9S6MrsW83Y9qZ%2Fuploads%2Fgit-blob-4a25b9a6b7b82b8eab689d0280ef01bbb5d8683e%2FskyChaser-preview.webp?alt=media)

A multiplayer game where players compete to catch escaping packages in each round. The scene includes weekly and all-time leaderboards.

* [Play on Decentraland](https://decentraland.org/jump?realm=skychaser.dcl.eth)

## Project information

**Maintained by:** Community · stom66

[View upstream source](https://github.com/stom66/dcl-sky-chaser)

**License:** [CC BY-NC-ND 4.0](https://github.com/stom66/dcl-sky-chaser/blob/main/LICENSE.md). Check upstream terms before reuse; code and assets may have different terms.

{% hint style="warning" %}
**Community-maintained code — review before use**

This community project is maintained outside the Decentraland Foundation and DAO GitHub organizations. Its source code and live deployment may change independently.

Inclusion in this catalog does not imply a security audit or guarantee of safety. Review code, dependencies, and installation scripts before running or reusing it.

[Report a catalog concern](https://github.com/decentraland/docs/issues/new). For suspected vulnerabilities, follow the upstream project's security policy. Do not include exploit details or credentials in public issues.
{% endhint %}

## Key features

* Multiplayer server
* Synced gameplay via synced Mulberry32 RNG
* Storage API for leaderboards
* Player locomotion tweaks and physics forces for booster/trampolines/explosions
* Particle systems (boost trails, explosions, pickups)

## Explore the code

These links point to a specific source snapshot so the explanations remain useful as upstream development continues. They are learning references, not a security assessment.

### Reuse projectile entities during play

`fireProjectile` and `getIdleProjectile` reuse inactive projectiles, create new ones when the pool is exhausted, and update only active projectiles.

**Project context:** Follow the project's `Projectile` class and event handlers for movement, collision responses, and round-end cleanup.

**Source references:**

* [`fireProjectile` and `getIdleProjectile`](https://github.com/stom66/dcl-sky-chaser/blob/e546854d2a2634ca5e28635c8b9be124a173f6dc/dcl/src/client/projectileManager.ts#L76-L124)

### Seed pickup placement from round state

`onGameStart` and `getRandomPosition` use the round start time to initialize the project's random generator, then sample pickup distances and heights.

**Project context:** Read the pickup configuration and component store alongside it: mobile limits and later pickup activity affect the sequence of random calls, so a shared seed alone does not guarantee identical layouts on every client.

**Source references:**

* [`onGameStart` and `getRandomPosition`](https://github.com/stom66/dcl-sky-chaser/blob/e546854d2a2634ca5e28635c8b9be124a173f6dc/dcl/src/client/spawners/pickupSpawner.ts#L115-L164)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decentraland.org/creator/tutorials-and-examples/published-games/sky-chaser.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
