让游戏生成可迭代进化,通过机制规划实现创意渐进提升
CreativeGame:Toward Mechanic-Aware Creative Game Generation

- 用机制规划代替随意生成,先设计再写代码
- 多版本积累经验,4轮迭代中出现新机制创新
- 适合研究游戏演化过程的开发者与教育者
大语言模型能生成合理的游戏代码,但实现持续创造性改进仍具挑战。单次生成常导致运行时行为脆弱、版本间经验难以积累,且创意评估过于主观,无法作为可靠优化信号。此外,游戏机制通常仅作为事后描述,而非可规划、追踪、保留和评估的显式对象。本文提出CreativeGame,一个面向迭代式HTML5游戏生成的多智能体系统,通过四项核心设计解决上述问题:基于程序化信号的代理奖励,而非纯语言模型判断;跨版本的经验累积机制;将运行时验证融入修复与奖励环节;以及在生成前通过检索机制知识生成显式机制计划的引导式规划循环。系统包含71条历史线、88个已保存节点和774项全局机制档案,由6,181行Python代码实现,并配备可视化分析工具。真实4代演化案例表明,后期版本可涌现出可追溯的机制创新。其核心贡献不仅是生成可玩游戏,更提供了一套可观测、可解释的机制演变追踪管道。
原文摘要 · Abstract (English)
Large language models can generate plausible game code, but turning this capability into \emph{iterative creative improvement} remains difficult. In practice, single-shot generation often produces brittle runtime behavior, weak accumulation of experience across versions, and creativity scores that are too subjective to serve as reliable optimization signals. A further limitation is that mechanics are frequently treated only as post-hoc descriptions, rather than as explicit objects that can be planned, tracked, preserved, and evaluated during generation. This report presents \textbf{CreativeGame}, a multi-agent system for iterative HTML5 game generation that addresses these issues through four coupled ideas: a proxy reward centered on programmatic signals rather than pure LLM judgment; lineage-scoped memory for cross-version experience accumulation; runtime validation integrated into both repair and reward; and a mechanic-guided planning loop in which retrieved mechanic knowledge is converted into an explicit mechanic plan before code generation begins. The goal is not merely to produce a playable artifact in one step, but to support interpretable version-to-version evolution. The current system contains 71 stored lineages, 88 saved nodes, and a 774-entry global mechanic archive, implemented in 6{,}181 lines of Python together with inspection and visualization tooling. The system is therefore substantial enough to support architectural analysis, reward inspection, and real lineage-level case studies rather than only prompt-level demos. A real 4-generation lineage shows that mechanic-level innovation can emerge in later versions and can be inspected directly through version-to-version records. The central contribution is therefore not only game generation, but a concrete pipeline for observing progressive evolution through explicit mechanic change.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。