<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>发售准备 on PlumePHP</title><link>https://plumephp.com/tags/%E5%8F%91%E5%94%AE%E5%87%86%E5%A4%87/</link><description>Recent content in 发售准备 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Mon, 10 Oct 2022 20:36:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E5%8F%91%E5%94%AE%E5%87%86%E5%A4%87/index.xml" rel="self" type="application/rss+xml"/><item><title>Steam 首发客服与崩溃反馈入口：个人开发者如何把问题收集完整</title><link>https://plumephp.com/steam-support-contact-crash-reporting-2022/</link><pubDate>Mon, 10 Oct 2022 20:36:00 +0800</pubDate><guid>https://plumephp.com/steam-support-contact-crash-reporting-2022/</guid><description>个人游戏首发后支持入口要提前设计好，让玩家能提供版本、系统、日志和复现步骤，而不是只留下“打不开”。</description></item><item><title>Steam 发售前 QA 矩阵：个人开发者如何用有限设备做有效测试</title><link>https://plumephp.com/steam-qa-matrix-before-release-2021/</link><pubDate>Wed, 16 Jun 2021 08:55:00 +0800</pubDate><guid>https://plumephp.com/steam-qa-matrix-before-release-2021/</guid><description>个人开发者没有完整 QA 团队，也可以用风险优先的测试矩阵覆盖启动、存档、输入、性能和 Steam 安装版等关键问题。</description></item></channel></rss>