<?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/%E8%BF%90%E8%A1%8C%E6%97%B6%E6%9E%B6%E6%9E%84/</link><description>Recent content in 运行时架构 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Mon, 19 May 2025 19:22:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E8%BF%90%E8%A1%8C%E6%97%B6%E6%9E%B6%E6%9E%84/index.xml" rel="self" type="application/rss+xml"/><item><title>游戏服务器玩法插件运行时架构设计</title><link>https://plumephp.com/game-server-gameplay-plugin-runtime-architecture/</link><pubDate>Mon, 19 May 2025 19:22:00 +0800</pubDate><guid>https://plumephp.com/game-server-gameplay-plugin-runtime-architecture/</guid><description>&lt;h2 id="背景"&gt;背景&lt;/h2&gt;
&lt;p&gt;长线运营的游戏会不断增加玩法：节日小游戏、联动活动、限时挑战、特殊战斗规则、排行榜变体。每次都改核心服务，发布风险越来越高；完全交给脚本，又容易失控。玩法插件运行时介于两者之间：它给玩法扩展预留生命周期、状态存储、事件订阅、资源预算和权限边界，让新玩法能接入公共能力，但不能随意破坏核心状态。&lt;/p&gt;</description></item></channel></rss>