← 返回 shouyou.me
首页 / 联系方式

📮 联系方式

更新于 2026 年 11 月 5 日 · 独立开发者维护,请按下面的分类提交

shouyou.me 是一个人维护的业余项目,没有客服团队,也没有公开的邮箱地址。所有反馈统一走 GitHub Issues 公开处理:这样问题、复现步骤和修复进度都留得住,后来的玩家遇到同样的情况也能直接查到,比一封封私人邮件更有用。

GitHub → github.com/xiaomo945 找到对应仓库后点 Issues → New issue。报 bug、攻略纠错、功能建议、隐私请求都走这里。

按你要说的事选一类

你要反馈去哪标题建议
游戏卡住、白屏、数值异常对应游戏仓库的 Issues[Bug] 游戏名 + 一句话现象
攻略里的数字和实际对不上star-rift-miner 仓库 Issues[Guide] 攻略页 + 具体数值
想加新游戏 / 新功能 / 新语言任意仓库 Issues[Suggestion] 你的想法
隐私、Cookie 或数据删除请求任意仓库 Issues,标题写 [Privacy][Privacy] 请求类型
版权或内容使用授权任意仓库 Issues,标题写 [Copyright][Copyright] 使用范围

报 bug 时最好带上这些信息

游戏是纯前端运行,我看不到你的屏幕,也拿不到你的存档。信息越具体,能定位得越快:

  1. 哪款游戏、哪个页面,以及完整的网址。
  2. 浏览器和版本、操作系统、设备(例如 Chrome 131 / Windows 11,或 Safari / iPhone 15)。
  3. 复现步骤:点哪里、做了什么、期望发生什么、实际发生什么。
  4. 浏览器控制台的报错(F12 → Console),有截图最省事。
  5. 如果是存档相关:说明是否清理过网站数据、是否用过无痕窗口,不要粘贴完整的 localStorage 内容。
💡 攻略数值纠错特别欢迎。攻略里的公式直接取自源码,游戏调参后可能出现对不上的情况。指出「哪一页、哪个数字、你在游戏里看到多少」,我会核对后同步修订。

关于回复时间

这是业余维护的项目,不是全职服务,因此不承诺固定响应时间。通常几天内会看一次 Issues;如果长时间没动静,可以在原 issue 下追加一条,不用另开新的。涉及隐私或数据删除的请求会优先处理。

关于公开邮箱

目前不设公开联系邮箱,主要是为了避免收件箱被自动化垃圾邮件淹没,导致真正的反馈被埋掉。公开 issue 也意味着处理过程可查证。如果确实需要私下沟通(例如涉及个人信息的隐私请求),先在 issue 里说明,我们再约定一个临时方式——请勿在公开 issue 中张贴任何个人身份信息或完整存档内容。

其他入口

Home / Contact

📮 Contact

Updated 5 November 2026 · Independently maintained; please file feedback under the right category

shouyou.me is a one-person side project. There is no support team and no public email address. All feedback goes through public GitHub Issues: the report, reproduction steps and fix history stay visible, so the next player hitting the same problem can find the answer instead of waiting on a private reply.

GitHub → github.com/xiaomo945 Open the relevant repository, then Issues → New issue. Bugs, guide corrections, feature ideas and privacy requests all go here.

Pick the right category

What you wantWhereSuggested title
Freeze, blank screen, wrong numbers in-gameIssues in that game's repository[Bug] game name + short symptom
A guide number disagrees with the gamestar-rift-miner repository Issues[Guide] page + specific number
New game, feature or language ideaIssues in any repository[Suggestion] your idea
Privacy, cookie or data-deletion requestIssues in any repository, tagged [Privacy][Privacy] request type
Copyright or content licensingIssues in any repository, tagged [Copyright][Copyright] intended use

What to include in a bug report

The games run entirely in your browser, so I cannot see your screen or read your save. The more specific the report, the faster it can be tracked down:

  1. Which game and which page, plus the full URL.
  2. Browser and version, OS, device (e.g. Chrome 131 / Windows 11, or Safari / iPhone 15).
  3. Reproduction steps: what you clicked, what you expected, what actually happened.
  4. Console errors (F12 → Console); a screenshot is ideal.
  5. For save issues: whether you cleared site data or used incognito, and please do not paste your full localStorage contents.
💡 Corrections to guide numbers are especially welcome. The formulas come straight from the source, so a rebalance can leave a page out of date. Tell me which page, which number and what you observed in-game, and I will verify and revise it.

Response time

This is a spare-time project, not a staffed service, so no fixed response time is promised. Issues are usually checked every few days; if nothing happens, add a comment to the same issue rather than opening a duplicate. Privacy and data-deletion requests are prioritised.

Why there is no public email

There is deliberately no published contact address: automated spam would bury genuine reports. A public issue also keeps the handling verifiable. If a private channel is genuinely needed (for example a privacy matter involving personal information), say so in the issue first and we will arrange a temporary channel — please never post personal identifiers or complete save data in a public issue.

Other pages