# Map Editor

MG.Land was born in Web3 and serves all Web3 users. A truly open metaverse should give users more choices, richer interaction modes, and the pursuit of ultimate decentralization. Therefore, MG.Land will provide a set of SDK (developer tools) with a high degree of freedom, allowing community members, individual creators and developers to build personalized communities and functional upgrades. 

MG.Land is committed to developing an ever-evolving ecosystem, and the SDK provides users with the tools to build everything and an opportunity to innovate the future.

* Create all new characters → Existing NFT collections or brand new IP extensions 
* MG.Land character skins, digital clothing, equipment, etc. (including ownership and interoperability) 
* Game development → Rich game components are provided to easily complete customized game development 
* One-stop node service → Embedded contract development and powerful database calls Users can customize and select the general scene modules provided by MG.Land, and freely place and develop their own Land according to their own preferences. 
* MG.Land will open exclusive functions such as custom naming. MG.Land brings in open user-defined scenes, and the resources uploaded by users, including pictures, audios, videos, etc., are converted into usable scene content through the editor protocol. It is allowed to bring NFT assets that meet the land into the land for decoration.

<figure><img src="/files/kfPni6Cnjbpn58HxF5ox" alt=""><figcaption></figcaption></figure>


---

# 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.mg.land/space-tool/map-editor.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.