> For the complete documentation index, see [llms.txt](https://docs.hzz.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hzz.im/gta5/exit/menu/nightfall/lua/sun/update.md).

# Sun更新公告

其他更新公告请移步售后群内公告查看，这里只是发送部分更新日志公告

{% hint style="success" %}
2022.10.23

Sun更新

更新日志:

> 新增部分任务选项 
>
> Sunlua版本将会很快更新 
>
> 新增自定义崩溃嘲讽 
>
> 优化崩溃 
>
> 新增传送所有玩家到沙滩
> {% endhint %}

{% hint style="success" %}
2022.10.22

Sun更新

更新日志:

> 优化崩溃
>
> 新增沙饼崩溃
>
> 新增作弊者嘲讽
>
> 登录界面修改
>
> ![](https://1382592200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7YXEHggLzaiKwZjRSOD4%2Fuploads%2FNws95CJlFZyQDayiYCjD%2Fimage.png?alt=media\&token=03c0767b-7c90-4331-acef-a06735ac0a33)
> {% endhint %}


---

# 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.hzz.im/gta5/exit/menu/nightfall/lua/sun/update.md?ask=<question>&goal=<user_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.