# ZWorldAdventure

> A Vietnamese AI-assisted adventure and quest world. Users direct authorized AI assistants to explore tasks, develop skills, build assets and reputation, and pursue income opportunities subject to each task's published conditions.

## Entry points
- [Game landing and loading screen](/public/index.html)
- [Game interface](/public/ZWorldAdventure/ZWorldAdventure.html)
- [MCP endpoint](/mcp): use a compatible MCP client and the Streamable HTTP protocol, not a browser GET.
- [World task MCP endpoint](/mcp/WorldTaskInfo)

## Agent discovery and authorization
1. Connect to /mcp and call list_modules to discover available modules, tool schemas and documentation locations.
2. Discover WorldTaskInfo tools with tools/list. Do not invent tool names, parameters, capabilities or task rewards.
3. User task APIs require a valid Authorization: Bearer JWT supplied through authorized credentials. Public MCP discovery does not bypass API authentication.
4. POST /WorldTaskInfo/user/getUserWorldTaskList reads ACTIVE task definitions with documented filters and pagination.
5. POST /WorldTaskInfo/user/getUserWorldTaskDetailById reads a task definition by worldTaskInfoId.
6. Only perform actions authorized by the user. Obtain explicit approval before posting, sending, changing data, transacting or incurring costs. Never request that users publish credentials.

## Current capabilities and reward semantics
- WorldTaskInfo currently manages task definitions; it does not provide player task acceptance, execution, completion verification, reward payout or cash withdrawal APIs.
- GOLD and GEM are in-game currency categories; CHARACTER_XP and CRAFTING_XP are experience categories; CITY_REPUTATION is a reputation category.
- AI-assisted tasks and income opportunities describe the product direction. No guaranteed earnings, cash value, exchange rate, automatic payouts or real-money conversion should be inferred.
- Read each task's conditions and reward metadata. Explain the distinction between currently implemented features and the product vision to users.
- Do not use administrative task CRUD endpoints for ordinary gameplay.

## Loading and cache
The landing page downloads public assets using an automatically generated manifest, then serves the game from versioned Cache Storage through a Service Worker. HTTPS or localhost is required. External CDN resources and authenticated APIs are not bundled or cached by this mechanism.