> For the complete documentation index, see [llms.txt](https://docs.sandbox.game/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sandbox.game/en/creator/game-maker/creative-guides/experience-guide/action-adventure.md). # Action / Adventure {% embed url="" %} Action / Adventure games involve navigation and active participation to complete objectives and achieve an overall goal. The Sandbox Game Maker has many new tools, including the [**Game Rules**](/en/creator/game-maker/docs/game-rules.md) system, to combine with the [**Objectives**](/en/creator/game-maker/docs/objectives.md) system for quests (formerly called "Rules") and new or enhanced object logic ([**behaviours**](/en/creator/game-maker/docs/behaviours.md) and [**components**](/en/creator/game-maker/docs/components.md)) to design a spectacular world to explore. ### Variations of Action
Beat 'em Up:
Players engage in hand-to-hand combat against waves of enemies.
Hack and Slash:
Intense combat with a focus on defeating numerous foes.
Platformer (includes Parkour):
Players navigate levels, overcoming obstacles and enemies.
### Variations of Adventure
Point-and-Click:
Emphasis on exploration and puzzle-solving through mouse interaction.
Survival Horror:
Combines elements of horror and survival, often with limited resources.
Metroidvania:
Non-linear exploration, interconnected levels, and character upgrades.
### Variations **of Fighting**
Traditional Fighting:
One-on-one combat with a focus on combos and special moves.
Beat 'em Up (Fighting Adventure):
Fighting within a broader narrative and exploration context.
Versus Fighting:
Multiplayer-focused competitive combat.
--- # 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.sandbox.game/en/creator/game-maker/creative-guides/experience-guide/action-adventure.md?ask=&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.