> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/player/player-zh/yi-dong-ying-yong/controls.md).
# 控制
如何使用触控进行移动、互动、聊天和使用摄像头。
Decentraland 移动应用用屏幕触控操作替代了键盘和鼠标。你在桌面端能做的一切，在移动端也都可以实现，只是采用了专为单手触控设计的不同布局。
Decentraland 移动应用的游戏内 HUD，每个触控控件都有标注。
## 移动
* **屏幕摇杆** （屏幕左侧）— 拖动即可向任意方向行走和奔跑。摇杆推得越远，移动速度越快。
* **摄像机拖动** （屏幕右侧任意位置）— 拖动即可环顾四周。这会旋转你的视角，但不会移动你的头像。
## 交互
* **交互按钮** （右下角）— 点击即可与你瞄准的对象进行交互。这相当于桌面端的指针点击。
* **轻点物体** — 世界中的许多东西都可以直接轻点。如果创作者已设置某个实体对轻点作出反应，你触发它的方式与在桌面端点击相同。
## 聊天
* **聊天图标** （左侧）— 点击打开聊天。可用它与附近的人交谈，或通过私信与好友聊天。
## 个人资料、搜索和表情动作
* **个人资料** （右上角）— 打开你的个人资料，管理你的头像，并访问账户设置。
* **搜索** （左侧）— 查找场景、世界、活动和其他玩家。
* **表情动作** （左侧）— 触发表情动作，在其他玩家面前表达自己。
## 摄像机
* **摄像机控制** （右上角）— 在第一人称和第三人称视角之间切换，并访问与摄像机相关的选项。
## 提示
* 你可以与附近的任何人聊天，即使他们使用的是桌面端或网页端。所有人共享同一个世界。
* 长按摇杆可让角色持续行走，而无需用拇指一直按住屏幕（取决于应用版本）。
* 如果某个场景的 UI 感觉过于拥挤，可能是创作者还没有为移动端更新它——请稍等片刻，看看是否有替代视图，或者通过应用内支持菜单进行反馈。
## 相关
* [移动端入门](/player/player-zh/yi-dong-ying-yong/getting-started.md)
* [故障排除](/player/player-zh/yi-dong-ying-yong/troubleshooting.md)
* [快捷方式与聊天命令](/player/player-zh/shi-jie-nei/shortcuts-and-chat-commands.md) （桌面端参考）
---
# 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.decentraland.org/player/player-zh/yi-dong-ying-yong/controls.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.
