> 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/shroom-zoom.md).

# Shroom Zoom

Platforming with trigger-activated bounce raycasts, player impulses, and collectible sprites that follow or orbit their owner.

![Shroom Zoom preview](https://45449780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoPnXBby9S6MrsW83Y9qZ%2Fuploads%2Fgit-blob-df150ee3c17dd5d82f9985e8215af6cb57b11e79%2FshroomZoom-preview.webp?alt=media)

A platforming and time-trial game with double-jumping, gliding, collectibles, and exploration.

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

## Project information

**Maintained by:** Community · CanessaDCL

[View upstream source](https://github.com/CanessaDCL/dcl-shroomzoom)

**License:** Not identified in this catalog. Consult the upstream repository and maintainer for applicable terms before reuse.

{% 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
* Physics impulses for bouncy mushrooms

## 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.

### Combine a nearby trigger with a precise contact check

BounceTrigger callbacks enable raycasting while the player is inside a trigger and remove that system on exit. The raycast and bounce logic check downward hits against the configured mushroom entity and apply a player impulse near its surface.

**Project context:** Read it alongside BounceZoom or BounceRegular for the scene's trigger dimensions and impulse settings.

**Source references:**

* [BounceTrigger callbacks](https://github.com/CanessaDCL/dcl-shroomzoom/blob/042968e3c13b5d1093d2922d5713570ad4cb0284/src/bounce/class.bounce.ts#L75-L101)
* [The raycast and bounce logic](https://github.com/CanessaDCL/dcl-shroomzoom/blob/042968e3c13b5d1093d2922d5713570ad4cb0284/src/bounce/class.bounce.ts#L103-L164)

### Turn collected items into an animated entourage

Follower target helpers calculate offsets around the player and positions around an orbit. followSpritesSystem interpolates each sprite toward its target, switching to orbiting when the collection is complete and rotating sprites toward their owner.

**Project context:** The scene's collection sets, follower entities, and per-player orbit timestamps supply the state for this visual behavior.

**Source references:**

* [Follower target helpers](https://github.com/CanessaDCL/dcl-shroomzoom/blob/042968e3c13b5d1093d2922d5713570ad4cb0284/src/spriteFollowers.ts#L400-L437)
* [followSpritesSystem](https://github.com/CanessaDCL/dcl-shroomzoom/blob/042968e3c13b5d1093d2922d5713570ad4cb0284/src/spriteFollowers.ts#L678-L706)


---

# 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/shroom-zoom.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.
