> For the complete documentation index, see [llms.txt](https://ujhhgtgteams.gitbook.io/wekit-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ujhhgtgteams.gitbook.io/wekit-docs/liao-tian/stickers-sync.md).

# 贴纸包同步

> 从指定路径将所有图片注册为贴纸包。搭配 Telegram Xposed 模块 StickersSync 或自带此功能的第三方客户端使用

## 类别

聊天

## 类型

可开关 & 可点击

## 描述

从指定路径将所有图片注册为微信贴纸包, 便于与 Telegram 的贴纸包导出模块或自带此功能的第三方客户端同步使用, 也可直接使用已有的图片文件作为贴纸。

### 目录结构

```none
<模块数据>/stickers/
├── pack1/
│   ├── sticker1.png
│   ├── sticker2.png
│   └── .pack_icon.png (可选)
├── pack2/
│   ├── sticker1.png
│   └── sticker2.webp
└── ...
```

* 在 `<模块数据>/stickers/` 目录下创建贴纸包目录。
* 每个贴纸包为一个子目录, 目录名即为贴纸包名称。
* 将贴纸图片放入对应目录。贴纸支持 `png` `jpg` `jpeg` `gif` `webp` 后缀图片。`webp` 图片将会自动转换为支持的 `png` 格式。
* (可选) 在贴纸包目录中添加 `.pack_icon.png` 文件作为该包图标。该文件不存在时, 将自动使用贴纸包第一张贴纸作为图标。
* `.hashes.json` 文件自动生成, 无须手动创建, 包含微信内部使用的每张贴纸的哈希值, 大幅提高加载速度。

## 使用方法

在模块设置中启用, 并手动创建目录结构和添加贴纸

## 注意事项

当该功能出现异常, 可点击功能, 点击「清除贴纸哈希缓存」或「清除微信数据库贴纸包缓存」并重启微信以尝试修复


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ujhhgtgteams.gitbook.io/wekit-docs/liao-tian/stickers-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.