# Gameplay Overview

**Gameplay Overview**

*Muish Oddity: Mutant Monkfish* is a systems-first survival sim between two dying worlds. You’re not a hero. You’re an operator—extracting, building, trading, reacting in an ecosystem that remembers what you do to it.

***

**Dual-World Traversal**

Two biomes. Both hostile. Both exploitable.

Below: biotech ruins and oxygen debt. The trench is ancient, unstable, and power-starved.

Above: glitching factions and energy greed. The city is dense, volatile, and watching.

Each world bleeds into the other. What you unlock in the deep destabilizes the surface—and vice versa.

***

**Energy as Currency**

Nothing moves without power. Travel, tech, breathing—it all costs energy.

Energy is scarce. Player-owned. Priced in $MUISH.

Manage it and you expand. Mismanage it and you're renting someone else’s future.

***

**Ownership Is Infrastructure**

Land isn’t cosmetic. It’s where systems live—and decay.

Drop a reactor in the trench. Build a hub in the city. If players need what you’ve built, they pay.

Ownership isn’t status. It’s leverage. And responsibility.

***

**Crafting and Construction**

What matters is player-made.

Suits, vehicles, mods—built from blueprints you scavenge, decode, or steal.

Crafting is escalation. Every item is a system extension—or disruption.

***

**Systemic AI & Multiplayer Tension**

The world adjusts. AI factions track your moves, your footprint, your mistakes.

Multiplayer is opt-in. Until someone wants your land, your gear, or your grid.

Then it’s on.

***

**Blockchain Backbone**

Every asset is real. Minted. Owned. Tradable.

Land, gear, blueprints, relics—anchored on-chain.

$MUISH powers the economy. Smart contracts run the rules.

This isn’t a skin. It’s the skeleton.

***

**What You Do Matters**

*Muish Oddity* doesn’t reward winning. It rewards survival inside a system that mutates around you.

Every tool placed, every structure powered, every anomaly triggered—etches your presence into a world that won’t forget.


---

# 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://whitepaper.muish.com/gameplay-overview.md?ask=<question>
```

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.
