# Gameplay Aspects ![](https://2559250486-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtlWzdWKtqQ6kQH3SGze%2Fuploads%2FH0tEcbmX2ClAB3K1yttx%2Fgameplay_aspect_banner.png?alt=media\&token=47c3e328-0072-45a7-9db6-831a1729291a) Soulbond is a **third-person perspective** game where the player’s character avatar can be seen in the centre of the screen. Combat mechanics involve combinations of **action** and loadout **strategies**. Character **power growth** revolves around collection of **items** and improving **skills**. There are **NO character levels** in Soulbond. **Phase 1** of the game will feature **session-based dungeons** focused on **Musou (hack & slash)** action, while **Phase 2** will feature an **open free-roaming world** with more types of **social interactions** and **in-game activities**. **Cooperative play** is encouraged in the game, especially in combat and other tasks. Player **characters** will possess a variety of **traits**, **skills**, **classes**, while **monsters** will have different classes and elements, each with varying **degrees of power**. Tougher monsters are designated as **Bosses**, and pose a significant challenge to players. Elements feature prominently in the game, and the **five major elements** have their own unique **nations**, **skills**, **items** and **wearables**. Each element has its own **advantages** and **disadvantages** and provides an added layer of **depth** to gameplay. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://soulbond.gitbook.io/soulbond/the-game/gameplay-aspects.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.