# 《电梯大战 2026 / ELEVATOR WAR 2026》— GPT6 生成提示词(完整版)...

作成日: 2026年9月10日

使用モデル GPT-6 Pro by Chat01

質問

《电梯大战 2026 / ELEVATOR WAR 2026》— GPT6 生成提示词(完整版)

使用说明:本文件是给 GPT6 的完整生成规格
由于内容量大(约 4000+ 行代码),不要要求一次性输出
先把「§0 任务说明」+「§1~§9」整份粘贴给 GPT6,然后按「§10 分段输出计划」逐段索要代码。
每段生成后把上一段代码回贴给它作为上下文,保证接口一致。


§0 任务说明(直接粘给 GPT6 的开场白)

text
你是一名资深独立游戏开发者,精通 HTML5 Canvas 2D 游戏架构与 Roguelike 数值设计。 请为我实现一款完整可玩的俯视角 Roguelike 游戏《电梯大战 2026》。 硬性技术约束: 1. 交付物是【单个 .html 文件】,双击即可在 Chrome/Edge/Safari 运行,零外部依赖、零 CDN、零构建工具。 2. 全部美术用代码绘制(Canvas 图元 / 程序化生成 / Emoji 字形),不引用任何图片或音频文件。 音效用 WebAudio API 程序化合成(方波/噪声包络)。 3. 目标 60 FPS,同屏 80 个实体不掉帧。使用固定时间步长(1/60s)+ 插值渲染。 4. 全部游戏内容【数据驱动】:武器表、敌人表、楼层表、强化表、词缀表必须是文件顶部的 常量 JSON 数组,改数值不用改逻辑。 5. 代码分模块、带中文注释、每个模块之间用 // ==== 模块名 ==== 分隔。 6. 存档用 localStorage(键名 EW2026_SAVE),含版本号字段以便迁移。 7. UI 全中文。支持键鼠 + 手柄(Gamepad API) + 触屏虚拟摇杆三种输入。 我会分段向你索要代码。每一段你只输出该段代码,不要省略、不要写 "// 其余同理"、 不要写占位函数。每段结尾告诉我该段导出了哪些全局符号。

§1 游戏总览

内容
名称电梯大战 2026(ELEVATOR WAR 2026)
类型俯视角 · 动作 Roguelike · 清关制
视角正俯视 45°(Top-down),单屏房间制,无镜头卷动或轻微跟随
参考手感《元气骑士》的操作 + 《以撒》的房间节奏 + 《武士零》的武器耐久紧张感
单局时长主线通关 3~5 小时;单层 40~90 秒
核心循环电梯门开 → 清空本层敌人 → 拾取/替换武器 → 电梯战 → 上一层
主线长度A 栋 100 层(上行)+ B 栋 100 层(下行)+ 1 个最终 BOSS = 201 关
通关后解锁「无尽挑战 · 深渊塔」

1.1 剧情设定(一句话)

2026 年,跨国集团「昇平大厦」双子塔内部的 AI 楼宇管理系统「OTIS-9」失控,
把整栋楼变成了一座垂直绞肉机。你是被困在 B1 停车场的一名普通打工人,
手里只有一把从消防柜里抠出来的砍刀。你要做的事只有一件:** 上去,然后下来,然后把它关掉。**


§2 核心机制

2.1 玩家基础

text
初始 HP 100(可通过强化提升到 600+) 移动速度 每秒 180 px 翻滚 Dash 消耗 1 格耐力,位移 140px,无敌帧 0.25s,冷却 0.55s 耐力 Stamina 3 格,每 1.2s 回复 1 格 拾取半径 28 px(按 E / 手柄 X 拾取) 基础暴击率 5%,暴击倍率 2.0x

2.2 武器槽位系统(核心规则

text
槽位 1 ── 【砍刀】固定槽,永远不可丢弃、永远不会损坏(唯一无耐久武器) 槽位 2 ── 自由槽 A 槽位 3 ── 自由槽 B 槽位 4 ── 自由槽 C
  • 玩家最多同时携带 1 把砍刀 + 3 把其他武器
  • 切换:数字键 1/2/3/4,或滚轮,或手柄 LB/RB。切换有 0.2s 硬直。
  • 槽位满时拾取新武器 → 弹出「替换哪一格?」小轮盘(时间减速到 0.15x,最多 4 秒)。
  • 丢弃武器:按 G。被丢弃的武器留在地上,可以再捡回来(同层内不消失)。

2.3 耐久 / 弹药系统(核心规则

武器类型消耗资源消耗规则
近战耐久 Durability命中普通敌 −1;命中重甲敌 −2;被格挡/命中金属环境 −3
枪械弹药 Ammo每发 −1,弹匣打空需装填(装填时间见武器表)
投掷堆叠数 Stack每次投出 −1,部分可回收
装置充能 Charge每次部署 −1

耐久损坏三阶段(近战/装置)

text
耐久 100%~26% 正常 耐久 25%~ 1% 武器出现裂纹(红色描边闪烁)+ 伤害 −20% + 攻速 −10% 耐久 0 【断裂】:武器碎裂消失,触发一次范围 60px / 伤害 40 的碎片爆炸(补偿性设计)

弹药规则

  • 弹药按口径共享:9mm / .357 / 12G / 5.56 / 7.62 / .50 / 能量电池 / 燃料 / 特种
  • 敌人掉落的弹药只补给玩家当前携带武器对应口径(避免掉落浪费)
  • 枪械打空后不会消失,变为「空枪」:可当作耐久 8 的钝器(伤害 12),或按 G 投掷造成 60 伤害后消失

2.4 砍刀升级树(让初始武器全程不废)

砍刀是唯一贯穿 201 层的武器,必须能成长。在电梯厅可用「刀匠工位」花费**螺丝钉(通用货币)**升级:

层级名称需求伤害新增特性
Lv1砍刀初始18挥击 100° 弧
Lv2淬火砍刀40螺丝30攻速 +12%
Lv3锯齿砍刀90螺丝48命中附加 3 层流血(每层 4/s,持续 3s)
Lv4加长砍刀180螺丝78攻击范围 55→82px,弧 100°→140°
Lv5电磁砍刀340螺丝128第三段挥击释放前冲电弧(射程 220px)
Lv6断层者600螺丝210处决 25% 以下血量的非 BOSS 敌人;击杀回 1 点耐力
Lv7OTIS 骨刀通关最终BOSS后解锁340无视 50% 护甲;击杀积攒「怒气」,满怒后下一击范围 x3

设计意图:砍刀伤害曲线略低于同期最强掉落武器(约 75%),但零维护成本
玩家的策略是"平时用砍刀苟,遇到精英/BOSS 掏出宝贝武器",这正是耐久系统想要的张力。

2.5 电梯机制(本作最大特色,必须实现

清空一层后,电梯门开启,进入电梯不是过场动画,而是一段独立小关:

① 电梯战(Elevator Fight)

  • 场地极小(240×160 px 密闭轿厢),持续 8~14 秒(随层数增长)
  • 敌人从天花板检修口 / 门缝 / 通风管三个方向持续涌入
  • 空间狭窄 → 枪械施展困难,近战与投掷收益极高(刻意反向考验砍刀)
  • 电梯战期间玩家受到的伤害 ×0.8(补偿无法拉扯)

② 电梯面板(到站前 3 秒可交互)

按钮效果
▲ +1正常上一层
▲ +3跳 3 层:立即获得 +80 螺丝钉,但跳过的层不掉落武器,且下一层敌人 +30%
⚠ 急停停在层间夹层,进入「维修井道」隐藏小关(高风险高回报,必出 1 件 T4+ 武器)
♻ 检修消耗 60 螺丝,全武器耐久/弹药回满(每 10 层限用 1 次)

③ 坠梯事件(随机 6% 概率触发,第 30 层后开放)

  • 钢缆被切断,电梯自由落体 5 秒,玩家在失重状态下战斗(重力反向、位移飘移)
  • 成功存活 → 直接下坠 5 层但获得「幸存者」增益(本层起 10 层内伤害 +25%)
  • 失败 → 掉落到随机低 3 层,损失一把随机武器

2.6 数值成长曲线

楼层序号 F(1~200,最终 BOSS 视为 F=201)为自变量:

js
// 敌人 enemyHP(F) = round(20 * Math.pow(1.028, F) * zoneMul) // F=1→21, F=50→81, F=100→320, F=200→5060 enemyDamage(F) = round(4 * Math.pow(1.0175, F)) // F=1→4, F=100→23, F=200→129 enemyCount(F) = clamp(round(4 + F * 0.09), 4, 26) // F=1→4, F=100→13, F=200→22 enemySpeed(F) = 70 + Math.min(F * 0.55, 90) // px/s,上限 160 // 玩家期望战力(用于校验,不直接写死) expectedDPS(F) = 45 * Math.pow(1.027, F) // 掉落 screwDrop(F) = round(3 * Math.pow(1.021, F)) weaponTierRoll(F): T1..T5 权重随 F 线性迁移(见 §5.3

TTK 设计不变量(实现后必须实测校验)

目标期望击杀时间
普通杂兵0.4 ~ 0.7 s
精英怪3 ~ 6 s
区域 BOSS60 ~ 120 s
最终 BOSS(三阶段合计)180 ~ 300 s

§3 五十种武器完整数据表

字段说明:伤害 为单次命中基础值(未计暴击/强化);资源 为耐久/弹药/堆叠/充能。
稀有度 T1白 / T2绿 / T3蓝 / T4紫 / T5橙。

3.1 近战武器(20 种,消耗耐久)

#名称稀有度伤害攻速(s)耐久特性
01砍刀初始180.38永不损坏,可升级(见 §2.4)
02办公椅腿T1110.3045遍地都是,掉落率最高;击退低
03钢管T1140.2890攻速快、击退高、耐久长的万金油
04碎玻璃片T1160.2512命中附加流血 6/s × 4s;极脆
05棒球棍T1220.4270完美时机可击回敌方投射物
06拖把(湿)T180.3460在地面留下水渍,配合电系武器可导电
07消防斧T2340.5560对门/箱体/护盾破坏 ×3
08灭火器T2260.6035右键喷雾(减速 50%,2.5s);耐久归零时原地爆炸 200 伤害
09电动螺丝刀T29×3连击0.45120穿甲:无视 60% 护甲
10裁纸铡刀T2400.5025暴击率 +30%,暴击倍率 2.5x
11高尔夫球杆T2280.4650挥击弧 180°,扫群
12消防水带T2120.20水压 100持续冲击,强力击退,可把敌人推下楼梯井秒杀
13链锯T315 / 0.1s持续燃料 80持续伤害;噪音吸引全层敌人仇恨(双刃剑)
14武士刀T3550.4040对 30% 以下血量非 BOSS 敌人处决
15电击警棍T3200.35电池 30麻痹 2s;对水渍中的敌人伤害 ×2.5 并连锁
16大锤T3800.8530慢;蓄力 1.2s 可砸穿地板直接掉到下一层(跳关)
17液压破拆钳T3650.6228完全无视护甲;对机械敌 ×1.8
18电磁斩刀T4950.44能量 45挥击轨迹残留 1.5s 电弧地带
19钨合金长刀T41100.4855范围 95px / 弧 150°;重量使移速 −8%
20单分子刃T52500.3015无视一切护甲与格挡;耐久极低,是"一次性斩杀 BOSS 阶段"的道具
21电梯钢缆鞭T5700.55需充能射程 200px 鞭击,可拉拽敌人到身前;击杀充能,充能满可再挥

注:上表 21 行含初始砍刀,实际"可捡武器"= 20 种近战(#02~#21)。

3.2 枪械(18 种,消耗弹药)

#名称稀有度伤害口径弹匣/备弹射速特性
22钉枪T110特种·钉20 / 800.15s把轻型敌钉在原地 1.5s
23手枪 9mmT1209mm12 / 960.22s全能入门枪
24微冲T2149mm30 / 1500.07s高散布,近距压制
25左轮 .357T248.3576 / 420.45s穿透 2 个敌人
26双管霰弹T214×1012G2 / 240.9s极近距离爆发,装填 2.2s
27气钉炮T225特种·钉40 / 800.25s击杀时把尸体钉在墙上(挡住后方射线)
28信号枪T230 + 燃烧特种·照明1 / 61.2s点燃目标 5s(12/s)
29泰瑟枪T25特种·电极1 / 41.5s麻痹 5s,对 BOSS 无效
30泵动霰弹枪T312×812G6 / 480.75s标准散弹
31突击步枪T3265.5630 / 1800.11s中距离万金油
32射手步枪 DMRT3707.6210 / 600.35s可穿透 1 层薄墙
33喷火器T318 / 0.1s燃料200持续点燃地面 6s;密闭空间(电梯)内自伤
34低温枪T310液氮150持续叠满冻结 → 敌人变冰雕,近战一击必碎
35狙击步枪T4180.505 / 251.1s爆头 ×3;开镜时移速 −60%
36轻机枪T4227.62100 / 2000.06s移速 −25%,需 1.5s 架设进入高精度
37榴弹发射器T4220(范围 90px)特种·榴弹6 / 181.0s有自伤;可打断 BOSS 蓄力
38特斯拉线圈枪T460能量电池600.3s连锁 5 个目标,每跳衰减 15%
39轨道炮T5600特种·弹芯4蓄力 1.8s贯穿整层直线上所有敌人与薄墙

3.3 投掷物(7 种,消耗堆叠)

#名称稀有度伤害堆叠特性
40砖头T13510眩晕 1s;可从地面无限补充(部分楼层)
41飞刀T24512落地后可回收
42燃烧瓶T260 + 火池6地面燃烧 8s(20/s)
43闪光弹T205全屏敌人致盲 4s,期间背击伤害 ×2
44破片手雷T3180(范围 110px)4经典
45EMP 弹T403所有机械敌/炮台/摄像头瘫痪 10s;对 OTIS 系 BOSS 强制打断
46微型奇点T5吸入 + 4001半径 180px 吸附 2s 后内爆;全游戏最强清场道具

3.4 装置(5 种,消耗充能)

#名称稀有度效果充能特性
47诱饵机器人T2吸引仇恨40s×3会跳广场舞,敌人全冲它
48战斗无人机T325 / 发自动攻击电池 120s跟随玩家,自动索敌
49遥控地雷包T3250(范围 100px)5手动引爆;可用于 BOSS 陷阱连招
50自动哨戒炮T430 / 发弹药 200 / 存续 60s部署后 360° 自动射击
51纳米修复力场T4半径 150px 内每秒回 HP 3% + 每 2s 回全武器耐久 1 点3 次 × 12s唯一能修耐久的战场道具,极其珍贵

合计可拾取武器 = 20 近战 + 18 枪械 + 7 投掷 + 5 装置 = 50 种。 加初始砍刀共 51 个条目。

3.5 武器词缀(每把掉落武器 25% 概率带 1 条,T4+ 为 60%)

text
锋利的 伤害 +15% 耐磨的 耐久上限 +40% 轻巧的 攻速 +18% 嗜血的 击杀回复 3% 最大HP 淬毒的 附加中毒 8/s×5s 带电的 15% 概率麻痹 1s 沉重的 击退 +80%,攻速 −10% 残缺的 伤害 −20%,但耐久 ×2.5(负面词缀,用于制造取舍) 签名款 该武器专属特效强化(每把武器一条独有效果)

§4 敌人设计

4.1 杂兵(按区域解锁)

名称区域行为特点
加班白领全程直线冲撞最基础单位,数量多
保安1-20近战挥棍有 15% 格挡(会消耗你的近战耐久 −3)
外卖骑手1-20高速冲刺移速 ×1.8,冲刺后 1s 硬直
清洁机器人21-40绕圈喷水地面留水渍(可被你的电系利用)
打印机械臂21-40远程射纸射出穿透纸片,伤害低但频率高
自助收银台41-60固定炮台不移动,三连扫射
暴走咖啡机41-60喷射热液范围 DoT
服务器机架61-80召唤每 6s 召唤 2 只数据幽灵
巡检无人机61-80空中近战难以命中,需枪械/投掷
行政保镖81-100重甲近战护甲 40%,对近战耐久消耗 −2
OTIS 傀儡81-200全能会闪避你的射击预判线
反重力清扫者B栋吸附把你拉向它
镜像打工人B栋模仿使用你当前武器的复制品攻击你

4.2 精英怪(每层 15% 概率,区 BOSS 前一层必定出现)

text
监工主管 ── 全屏点名,3s 后落下激光柱 消防系统 MK2 ── 泡沫覆盖地板,使玩家翻滚失效 数据蜂群 ── 分裂为 8 只小体,需范围武器 电梯维修工 ── 会破坏本层电梯门,杀死它才能继续上楼(强制击杀目标)

4.3 区域 BOSS(10 个,每 20 层 1 个)

楼层BOSS机制要点
A-20门禁闸机王闸机墙推进挤压场地,留安全缝
A-40碎纸机巨像地面传送带把玩家拉向刀口
A-60中央空调利维坦风场改变所有投射物轨迹
A-80机房主控·冷核场地持续降温,不动就冻结
A-100董事长·一号电梯整座电梯轿厢变成 BOSS,三阶段,通关后过天桥
B-100镜像的你完全复制玩家当前 4 把武器与强化
B-80垃圾压缩核心场地每 20s 缩小一圈
B-60厨房热源体全场起火,只剩移动的安全格
B-40停车场群体·千车无限车辆冲撞,需用场景柱子卸力
B-20地下水泵泰坦水位上涨,电系武器全场导电(对双方)

4.4 最终 BOSS:OTIS-9 核心(B1 深层 · 第 201 关)

text
阶段一「机房」HP 40% ── 四根电梯井道轮流喷射轿厢,玩家需在井道间走位 ── 每 30s 召唤一波 OTIS 傀儡 阶段二「悬井」HP 35% ── 场地变为垂直井道,玩家踩钢缆平台战斗(有坠落死亡风险) ── BOSS 切断平台;EMP 弹可强制它停手 10s 阶段三「数据体」HP 25% ── BOSS 分裂为 9 个子核心,需在 60s 内全部击破,否则重新融合回 50% HP ── 此阶段全武器耐久消耗 ×0(设计上允许玩家毫无保留地倾泻火力,作为高潮) 击败后 ── 播放 30s 结算(层数/击杀/最爱武器/总破坏武器数) ── 解锁:OTIS 骨刀(砍刀 Lv7)、无尽挑战模式、NG+ 困难循环

§5 关卡结构

5.1 总体流程

text
B1 停车场(教学关,0 层) ↓ 只有砍刀,教移动/挥击/翻滚/拾取/电梯 A 栋 1F → 100F(上行) 5 个区域 × 20 层,区尾 BOSS ↓ A-100 击败董事长 → 100 层天桥过场(可选:天桥上一场追逐战) B 栋 100F → 1F(下行) 5 个区域 × 20 层,区尾 BOSS ↓ B-1 打开地下闸门 B1 深层 → OTIS-9 核心(第 201 关) 结算 → 解锁【无尽挑战 · 深渊塔】

5.2 层类型分布(每 20 层为一个区,模式固定)

区内位置层类型说明
1,2,3,4,6,7,8,9,11,12,13,14,16,17,18战斗层标准清关
5,10,15电梯厅(安全层)无敌人;刀匠工位 / 弹药贩卖机 / 维修台 / 3选1强化
19精英层必出精英怪 + 保证掉落 1 件 T3+ 武器
20区域 BOSS 层BOSS + 必掉 1 件 T4+ 武器 + 大量螺丝
随机 3 层/区特殊层(覆盖战斗层)见 §5.4

5.3 武器掉落权重(随楼层 F 迁移)

js
// 线性插值:t = clamp(F / 200, 0, 1) weight_T1 = lerp(55, 5, t) weight_T2 = lerp(30, 18, t) weight_T3 = lerp(12, 32, t) weight_T4 = lerp( 3, 31, t) weight_T5 = lerp( 0, 14, t) 每层掉落武器数 = 1 (战斗层)/ 2(精英层)/ 23BOSS层) 安全层不掉武器,但贩卖机出售 T2T4 随机 3 件(价格 = 80 * tier^1.6 螺丝)

5.4 特殊层(共 12 种,随机插入)

text
停电层 ── 只有手电筒锥形视野,敌人在黑暗中 重力层 ── 移速/击退 ×1.6,难以停下 水淹层 ── 全场积水,电系全场生效(对玩家也一样) 火灾层 ── 地面随机起火,必须持续移动 仓库层 ── 敌人少但武器箱 4 个(补给层) 监控层 ── 被摄像头照到就刷新敌人,需先打掉摄像头 广告层 ── 全屏闪烁干扰,高饱和色彩(含关闭选项,癫痫友好) 无武器层 ── 进入时所有非砍刀武器被收走在出口处归还 → 纯砍刀考验 狭廊层 ── 一条走廊,只能正面推进 玻璃幕墙层 ── 可把敌人击出窗外秒杀 赌场层 ── 用螺丝赌:1/3 得 T5 武器,1/3 得螺丝翻倍,1/3 损失一把武器 静默层 ── 不能开枪(开枪即刷新大量敌人),近战/投掷专用

5.5 程序化房间生成

text
房间尺寸 1280×720(固定单屏,不卷动) 布局模板 每区 8 套手写 tile 模板(墙体/柱子/桌椅/电梯位),随机挑选 + 随机镜像/旋转 环境互动物 可破坏:桌子、隔断、饮水机(爆水)、消防栓(爆水+推开)、 电箱(爆电)、煤气罐(大爆炸 300 伤害)、落地窗(可击碎秒杀敌人) 电梯门位置 每层随机在 4 条边之一,门旁有楼层指示灯

§6 玩家强化系统(3 选 1,每安全层一次,共约 40 次)

6.1 强化池(每条可叠加,标注最大层数)

text
【进攻】 刃锋 全近战伤害 +12% ×10 膛线 全枪械伤害 +12% ×10 投手 投掷物伤害 +20%,堆叠上限 +2 ×5 连斩 连续命中同一敌人,每段 +8% 伤害(上限5段) ×3 精准 暴击率 +6% ×8 重击 暴击倍率 +0.3 ×5 【生存】 体质 最大 HP +40 ×10 护甲板 受到伤害 −8% ×6 二段翻滚 耐力上限 +1 ×3 吸血 击杀回复 2 HP ×8 铁皮 受击后 1.2s 无敌(冷却 6s) ×2 【维护 — 本作特色线】 工匠 全武器耐久上限 +35% ×6 节省 25% 概率命中不消耗耐久/弹药 ×4 弹药贩 敌人掉落弹药量 +50% ×4 回火 每通过一层,所有武器回复 8% 耐久 ×5 遗产 武器断裂时,随机另一把武器回满耐久 ×3 第五格 【稀有】解锁第 5 个武器槽(最多取 1) ×1 【机动】 疾行 移速 +10% ×8 电梯熟练 电梯战时长 −20%,获得螺丝 +30% ×3 开锁匠 安全层多出 1 个可选强化(变 4 选 1) ×2 拾荒 掉落武器 +1 件 ×3

6.2 货币与经济

text
螺丝钉(Screw)── 唯一货币。击杀/破坏场景/BOSS 掉落。用于:砍刀升级、贩卖机、维修台、赌场。 通关全程预计总获取约 9000~13000 螺丝。 砍刀升到 Lv6 需累计 1250,刻意让玩家必须在"升刀"和"买枪/修枪"之间取舍。

§7 无尽挑战 · 深渊塔(通关后解锁)

7.1 规则

text
入口 主菜单 →「无尽挑战」(需先通关主线一次) 起始状态 HP 满、只有砍刀(继承主线解锁的砍刀最高等级)、0 螺丝、0 强化 层数 无上限,程序生成,每层随机抽取 §5.2 的区域主题与 §5.4 的特殊层 安全层 每 4 层一次(比主线更频繁,因为难度更陡) 区 BOSS 每 10 层一个,从主线 10 个区域 BOSS 中随机(带强化词缀) 历代 BOSS 每 50 层重制一个最终 BOSS 变体(OTIS-9 α / β / γ …),HP 与机制叠加

7.2 无尽成长公式

js
// E = 无尽层数 endlessEnemyHP(E) = 5000 * Math.pow(1.065, E) endlessEnemyDmg(E) = 130 * Math.pow(1.040, E) endlessScrew(E) = 260 * Math.pow(1.050, E) // 玩家侧对抗手段: // 1) 强化无上限化(所有 §6.1 的 ×N 限制取消,可无限叠) // 2) 每 10 层额外给 1 次「超载强化」:效果为普通强化的 3 倍 // 3) 武器可在安全层「熔铸」:消耗 2 把同稀有度武器升 1 级稀有度(伤害按 tier 倍率重算) // 设计目标:熟练玩家应能稳定到 60~90 层,天花板约 140 层(指数必然追上)

7.3 诅咒词缀(每 10 层强制叠加 1 条,从池中随机,不可拒绝)

text
1 脆化 武器耐久消耗 ×2 2 弹药紧缩 敌人掉落弹药 −60% 3 荆棘 敌人死亡时爆出伤害弹片 4 狂暴 敌人移速 +25% 5 护盾 所有敌人获得 20% 护甲 6 再生 未被击杀的敌人每 3s 回 2% HP 7 黑暗 视野受限为 420px 圆 8 无维修 维修台与纳米力场失效 9 缩场 房间尺寸 −25% 10 分裂 杂兵死亡分裂成 2 只 40% HP 小体 11 电梯暴走 电梯战时长 ×1.8 12 吝啬 螺丝获取 −40% 13 镜像 每层有 15% 概率刷新 1 只镜像打工人 14 空投 每 20s 天花板落下轿厢砸击 15 时限 每层 90s 限时,超时持续掉血 16 反馈 你的暴击同时使自己受到 5% 最大 HP 伤害 17 单手 同时只能携带 2 把武器(含砍刀) 18 静音 全程禁止枪械(违者刷怪) 19 粘滞 翻滚冷却 ×1.8 20 终焉 BOSS 出现频率变为每 5 层

7.4 排行榜与存档

text
localStorage 键:EW2026_SAVE { "version": 1, "main": { "cleared": true, "bestFloor": 201, "macheteLv": 7, "ngPlus": 0 }, "endless": { "bestFloor": 0, "bestKills": 0, "bestTimeSec": 0, "runs": [ { "floor": 73, "kills": 4120, "timeSec": 5400, "weapons": ["单分子刃","轨道炮","微型奇点"], "curses": [1,5,10,14,7,2,9], "date": "2026-09-10" } ] }, "unlocks": { "weaponsSeen": [/* 武器 id */], "bossesKilled": [], "achievements": [] }, "settings": { "screenShake": 1.0, "flashReduce": false, "masterVol": 0.7, "input": "keyboard" } } 本地排行榜展示 Top 10 run,按 floor 降序、同层按 timeSec 升序。

§8 操作与 UI

8.1 输入映射

操作键鼠手柄触屏
移动WASD左摇杆左虚拟摇杆
攻击鼠标左键(朝鼠标方向)右摇杆瞄准 + RT右虚拟摇杆(自动开火)
副功能/瞄准鼠标右键LT右上按钮
翻滚Space / ShiftA左下按钮
切换武器1234 / 滚轮LB / RB右侧武器栏点按
投掷/部署QB按钮
拾取EX按钮
丢弃G长按 X长按武器格
暂停EscStart右上角

8.2 HUD

text
左上 HP 条(分段显示)+ 耐力格 + 当前层数徽章(A-57 / B-33 / ∞-12) 左下 4 格武器栏:图标 + 耐久/弹药条(近战绿条、枪械黄条、投掷数字、装置蓝条) 耐久 <25% 时该格红色脉冲 + 轻微抖动 右上 螺丝钉数量 + 本层剩余敌人数 + 已叠加诅咒图标(无尽模式) 右下 小地图(显示电梯门方位、掉落物、可破坏物) 中央下 提示条("按 E 拾取 武士刀 [T3] 锋利的")

8.3 视觉风格(Canvas 程序化绘制)

text
整体 低饱和工业风 + 荧光危险色点缀(#0e1116 底 / #e8eaed 线 / #ff4d4f 敌 / #ffd666 拾取 / #36cfc9 电) 角色 简化几何(胶囊体 + 方向指示三角 + 武器线段),不做骨骼动画,靠挤压拉伸与残影传达动感 打击感 必须有:命中顿帧 40ms、屏幕震动、击飞粒子、伤害数字、血液色块喷溅(可在设置中关闭) 区域色调 每 20 层换一套配色(停车场冷蓝 / 办公灰白 / 商场暖橙 / 机房青绿 / 行政金黑) BOSS 演出 进场黑屏 + 名字大字 + 血条从两侧滑入

§9 代码架构要求

text
单文件结构顺序(GPT6 必须严格遵守此顺序,便于分段生成): 1. <style> 全部 CSS(HUD、菜单、虚拟摇杆) 2. DATA 区 WEAPONS[] / ENEMIES[] / ZONES[] / FLOOR_TEMPLATES[] / UPGRADES[] / CURSES[] / BOSSES[] 3. CORE 数学工具、RNG(可 seed,便于复现 run)、对象池、事件总线 4. AUDIO WebAudio 合成器(8 种音效:挥击/命中/断裂/枪响/空仓/拾取/电梯铃/BOSS吼) 5. INPUT 三输入统一为抽象 InputState 6. ENTITY Player / Enemy / Bullet / Pickup / Prop / Particle(全部走对象池) 7. WEAPON 武器行为机(melee/gun/throw/device 四种 behavior 分支 + 词缀修饰器) 8. FLOOR 楼层生成器(模板 → tile → 碰撞网格 → 敌人编队 → 掉落) 9. ELEVATOR 电梯战 + 电梯面板 + 坠梯事件 10. BOSS 11 个 BOSS 的状态机(每个独立 class,统一 update/draw/onPhaseChange 接口) 11. PROGRESS 主线流程、安全层商店、强化 3 选 1、砍刀升级树 12. ENDLESS 无尽模式、诅咒叠加、熔铸、超载强化 13. SAVE localStorage 读写 + 版本迁移 14. UI 菜单/HUD/结算/排行榜/设置 15. LOOP 固定时间步主循环 + 场景栈(Menu/Play/Elevator/Shop/Boss/Result) 关键实现要求: - 碰撞:统一用均匀网格(cell 64px)做 broadphase,圆-圆/圆-AABB 做 narrowphase。 - 敌人 AI:状态机(Idle/Chase/Attack/Recover/Flee)+ 简单分离力避免叠堆。 - 所有"武器特性"走统一 hook:onHit / onKill / onBreak / onFire / onEmpty, 新武器只需写数据 + 可选 hook,不改核心逻辑。 - 性能:粒子上限 600,敌人上限 60,子弹上限 400,超出复用最老对象。 - 必须带 DEBUG 模式(按 ` 键):显示 FPS、实体数、碰撞网格、一键跳层、一键给武器。

§10 分段输出计划(逐段向 GPT6 索要)

把下面每一条作为单独一轮请求发出,上一轮代码附在后面作为上下文。

轮次索要内容预计行数
1文件骨架 + <style> + CORE + INPUT + AUDIO + 主循环与场景栈(可跑出空房间+能移动的玩家)~600
2DATA 区:完整 51 条 WEAPONS、13 条 ENEMIES、10 条 ZONES、UPGRADES、CURSES 数据表~500
3ENTITY + 碰撞系统 + 粒子与打击感~500
4WEAPON 行为机:四类 behavior + 耐久/弹药/断裂 + 词缀修饰器 + 砍刀升级树~650
5FLOOR 生成器 + 12 种特殊层 + 环境可破坏物~550
6敌人 AI + 编队 + 精英怪~450
7ELEVATOR:电梯战 + 面板 + 坠梯事件~350
8BOSS 第 1 批:A-20 / A-40 / A-60 / A-80 / A-100~600
9BOSS 第 2 批:B-100 / B-80 / B-60 / B-40 / B-20 + 最终 OTIS-9 三阶段~750
10PROGRESS:主线流程、安全层商店、强化 3 选 1、结算~450
11ENDLESS:无尽塔、诅咒、熔铸、超载强化、排行榜~400
12UI/菜单/设置/存档迁移 + 教学关 B1 + 最终整合与自检~500

每轮请求模板

text
继续《电梯大战 2026》。现在输出【第 N 轮:<内容>】。 要求:完整代码,不省略,不写占位。与之前代码的接口保持一致。 已存在的全局符号:<上一轮结尾它自己列出的符号清单> 输出末尾列出本轮新增的全局符号。

§11 验收清单(全部生成后逐项实测)

功能

  • 开局只有砍刀,砍刀永不损坏,可升到 Lv7
  • 可同时携带砍刀 + 3 把其他武器;槽满时弹出替换轮盘
  • 50 种可拾取武器全部能在游戏内实际出现并正常工作(用 DEBUG 给武器逐个验证)
  • 近战耐久归零会断裂并触发碎片爆炸;枪械打空变空枪可投掷
  • 弹药按口径共享且只掉落当前持有口径
  • A 栋 1→100、B 栋 100→1、第 201 关最终 BOSS,共 201 关全部可达
  • 10 个区域 BOSS + 1 个三阶段最终 BOSS 全部有独立机制
  • 每 5 层安全层:刀匠/贩卖机/维修台/3选1强化 均可用
  • 电梯战、电梯面板 4 个按钮、坠梯事件 均触发正常
  • 通关后解锁无尽挑战;无尽每 10 层叠加 1 条诅咒;本地排行榜记录并持久化
  • 刷新页面后存档正确读回

数值

  • 第 1/50/100/150/200 层实测杂兵 TTK 落在 0.4~0.7s
  • 区域 BOSS 实测 60~120s;最终 BOSS 180~300s
  • 只用砍刀(不买不修)能打到约第 60~80 层(验证砍刀不过强也不过弱)
  • 无尽模式熟练玩法能到 60 层以上,不会在 20 层骤停

性能与体验

  • 同屏 60 敌 + 400 子弹 + 600 粒子时 FPS ≥ 55
  • 单文件大小 < 1.5 MB,离线可运行
  • 键鼠 / 手柄 / 触屏三套输入都能完整通关
  • 设置里可关闭屏幕震动、闪光、血液
  • DEBUG 模式(` 键)可跳层、给武器、看碰撞网格

§12 可选扩展(如果 GPT6 还有余力)

text
1. 种子分享:每局 run 有 seed,可输入 seed 复现同一套 201 层(方便竞速) 2. 每日挑战:按日期做 seed,固定 3 条诅咒,独立排行 3. 武器图鉴:解锁过的武器在菜单可查看数据与击杀数统计 4. 成就系统:30 条(如"只用椅子腿通过一个区域""让 50 把武器断在手里") 5. 回放热力图:结算时显示你在每层的移动轨迹热力图 6. NG+:通关后重开,敌人基线 ×1.6,但保留砍刀等级与图鉴

思考

Charting a course

I’m working through intelligently guiding the conversation to avoid common issues and elicit more details for a quicker, more precise response.

The user is detailing a process for generating code and managing schedules, focusing on brief, important conflicts, and setting defaults for efficient progress.

Examining offline file

I'm thinking through testing an offline file with Playwright, handling dependencies, and crafting an HTML file skeleton for delivery.

Worked for 47s

回答

已收到《电梯大战 2026》的完整规格。当前尚未生成代码,已存在的全局符号:无。

下一轮可直接发送:

text
开始《电梯大战 2026》第 1 轮: 文件骨架 + 全部 CSS + CORE + INPUT + AUDIO + 固定时间步主循环与场景栈。 交付一份可直接离线打开的 HTML,能够显示空房间并操作玩家移动、瞄准和翻滚。 模块排列遵守 §9;后续模块的插入位置使用明确注释标记,不写占位函数。 末尾用代码注释列出本轮导出的全局符号。

另外,规格中有一处会影响后续流程实现:A 栋 100 层之后,B-100 对应总关卡 F=101,并非每 20 关的区域末尾。“B-100 镜像 BOSS”的位置与“区域 BOSS 每 20 层出现”的规则不能同时严格成立;进入楼层与流程模块时,需要明确区分总关卡序号、楼宇显示层号、区域内位置,避免把两套编号混用。

質問

直接完成全部游戏开发不要停

思考

Crafting the game

I'm piecing together an intricate single HTML game, ensuring offline suit between browsers. Integrating native APIs and stable foundations.

Assessing budget constraints

I'm mapping out the budget flexibility and time limitations. Considering 60k output tokens, evaluating tool choices, and factoring in browser testing with Python Selenium.

Crafting design features

I'm piecing together the game world, layout, and UI elements, considering clarity, touch controls, and mobile setup. Progressing towards a cohesive design.

Ensuring proper access

I’m thinking through the elevator's accessibility for players with such limitations, guaranteeing smooth elevator access.

Evaluating stats

I'm thinking through the scaling stats for the weapon system, including HP and DPS, and assessing progression and optimization strategies.

Adjusting parameters

I’m finalizing weapon and boss HP calculations, considering tier scaling and expected DPS for precise balance.

Optimizing boss encounters

Adjusting HP and DPS calculations to better survive intense battles. Testing different variables for increased durability and damage.

Unlocking complex gameplay mechanics

I'm thinking through intricate systems like ammo pooling, special ammo types, and firearm mechanics to create a dense and challenging experience. Let's break these down to ensure a thorough understanding and balance.

Checking for hazards

I’m gathering info on hazards from the pooled entity, considering jump-through floors with platforms. Hazards like spikes and bombs need separate info; hence, examining how moving platforms and pits fit together is essential.

Mapping out details

I’m detailing room categories, environmental events, and zone mappings. Analyzing enemy spawns and upgrades to optimize spatial strategy.

Evaluating equipment options
I'm considering the impact of different items on a character's stats and combat strategy, ensuring they align with the current build and needs.

Gathering resources

I’m collecting ideas for game mechanics, including strategies for progressing through bosses and managing resources efficiently, ensuring a balanced and challenging experience.

Ensuring progress

Saving game states, tracking inventory, and logging checkpoints to maintain progression and avoid resource exploitation.

Testing and debugging

I'm digging into detailed tests, considering skip options, NG+, weapon adjustments, and more. Progress is steady, with precision enhancements as a goal.

Crafting the strategy

I'm piecing together a plan for Python and JavaScript integration, focusing on using Python to handle large files and JavaScript for the user interface. The goal is to ensure efficient data manipulation and intuitive user interaction.

Implementing game mechanics

I’m working through mechanisms like combat roles and moral alignments for rich player-villain narratives.

Seeking code assistance
I need support for core code.

Taking a closer look

I’m analyzing the Python script, identifying typing issues, and evaluating its logical progression and execution history to optimize performance and clarity.

Adjusting enemy tactics

I'm tweaking enemy strategies: setting base HP, enhancing enemy traits, and adding specific boss patterns. Progress is steady.

Refining game mechanics

I’m focusing on optimizing projectile queries and ensuring efficient resource management for subtle mechanics. This involves precise damage calculations and crafting immersive gameplay without adding complex soundscapes or visual effects.

Piecing together weapon stats

I’m gathering weapon stats, considering power calculations, affixes, and tiers. Focusing on DPS, cooldowns, and scaling factors to fine-tune effectiveness.

Tracking progress

I’m piecing together mechanics for ammo control, crafting, throwable dynamics, and hooks to handle the player state effectively.

Evaluating combat tools

I’m looking at melee weapons, considering damage potential, consumption rates, and utility aims. Energy efficiency and strategic use are key.

Analyzing game dynamics

I'm observing the boss's behaviors and power levels, including immunity to ice and TASER status effects, flood-based attacks, and the presence of friendly water hazards.

Detailing floor layout

I'm working through the floor layout, setting up AI parameters, and updating entities. This involves managing NPC stations, props, hazards, and the boss. The roadmap also scrutinizes rendering specifics, including blackout effects and advertising visibility.

Updating AI behavior

Enhancing AI states: idle, search, attack, and recovery. Progressing through actions refined with delays and steering updates.

Designing range coverage I’m gathering info on AI enemy mechanics, focusing on their bullet and melee attacks, aiming strategies, and specific abilities like mirroring or executing summon actions.

Refining class relationships

Finalizing classes with customization, focusing on pooling and ensuring proper prototype handling for enemies and bosses.

Understanding phase transitions

I’m piecing together the boss's phase transitions, core mechanics, and enemy spawn behaviors. Each phase has unique attributes like max HP, shield components, and intricate movement patterns.

Crafting the attack

Piecing together the attack array for consistency, ensuring updates through mice or controller input, and refining boss strategies for greater specificity.

Describing the boss

I’m detailing the boss mechanics, including phases, attack patterns, and environmental interactions. System variables like rage and heat are discussed, with a focus on mirroring player actions and modulating remaining time.

Mapping the game landscape

I’m identifying key elements like bosses, player actions, and core mechanics. The elevators feature wave spawns and progression through clear waves. Writing the elevboss will be my next step.

Navigating progress

I'm working through tool efficiencies, tackling updates every 15 seconds, and managing data flow effectively.

Mapping out details

I’m detailing game mechanics and automation. The focus is on persistent sessions, UI transitions, and upgrade handling. Significant progress is being made in refining these elements for a more seamless experience.

Evaluating purchasing options

It's interesting to see the complexity of choosing a budget-friendly weapon, factoring in repair and upgrade costs, and cashless or casino-based options. Progress in key areas is evident.

Updating progress measures

I’m refining boss rewards and tracking final bosses for strategy. This involves healing mechanics and linking achievements for a clear gameplay progression.

Refining the gameplay

I'm working on recalculating tiers, adding a 17-gold variant to TIER_COLORS, updating scaling, and ensuring smooth progression in the game.

Validating configurations

I’m checking numeric fields, arrays, strings, and filters for validation. Also, ensuring protections, backups, and safe JSON handling. Progress is being saved and states are checked.

Assessing tools

Checking tokens and syntax scripts for efficient coding.

Highlighting progress

Contacting for updates

Reviewing syntax

Noticing incomplete tasks

Validating syntax

Tracking project phases

Focusing on procedures

Gathering class updates

Enhancing task status

Crafting UI mechanics

I’m working on crafting various UI mechanics like procedural backgrounds and dynamic event delegation for buttons to enhance the game experience.

Crafting UI mechanics

I’m mapping out the UI mechanics, ensuring cross-platform functionality, dynamic HUD updates, and precise touch navigation, prioritizing accessibility and multitasking.

Analyzing HUD layout

Mapping hotbar, durability, and mini-map details for precise UI organization.

Summarizing browsermeasure

I’m thinking through the browsermeasure options for stress testing, evaluating checkboxdebuggrid and server stress configurations. The aim is to simulate intense gameplay dynamics like infinite enemies and particles, ensuring a robust understanding of performance under extreme scenarios.

Evaluating clipboard use

I'm curious about evaluating the clipboard's role in file handling, ensuring security and fallback options are secure. Progressing towards a solid integration with these points.

Enhancing progress

I’m noting an update to the UI with a 30-second countdown, a progress bar, and main menu buttons. The timer is set to auto-return after 30 seconds, enhancing user interaction and engagement.

Categorizing fields

Listing fields like running, ended, mode, F, rng, seed, etc., and their roles in the game's gameplay mechanics.

Enhancing clarity

I’m integrating capacity to manage 'clearWorld' scenarios, initializing, saving, and restoring followers proficiently, considering transitions, and addressing cross-platform challenges.

Updating parameters

I noticed the boss nullification affects the UI and kills count. Pulling together info on loot mechanics, considering mechanics like drop rates, ammo allocation, and economic balance, to ensure an engaging gameplay experience.

Piecing together

Garage sale preparations are coming along nicely, with a detailed outline of items, pricing strategies, and marketing tactics in place.

Gathering info

Consulting knocked-off enemies and troop movement patterns. Charting main paths for strategic analysis and gathering info for fallout steps.

Adjusting phase mechanics

I’m mapping out phase transitions, damage thresholds, and progress requirements. Attention to core destruction and enemy behaviors is noted.

Analyzing game mechanics

I'm working through the use of SceneStack to manage game flow, item reproduction, and aggressive enemy spawning patterns, aiming to maintain challenging gameplay and craft optimizations.

Mapping the UI

Tracing the layout with a skeuomorphic design that highlights clarity and hierarchy. The balance in brightness between dark and light areas is notably better.

Adjusting rendering limits

I'm setting the rendering parameters, like screen reflection and agility, to balance battery life and FPS. This includes tweaking dynamic resolution and applying effects like flash and screen shake.

Mapping the flow

I’m examining UI shortcut handling, gamepad navigation, and pause mechanics, ensuring game clock accuracy and scheduled events.

Implementing enhancements

I’m working through implementing an external run combat all weapons script. This involves evaluating per game reset, using a separate loop in one browser page context headless, and details like console error-catching with unhandledrejection and navigator.clipboard.

Addressing major bugs

I’m confirming readiness for browser tests. Bugs included: resetting runs, object pooling for bosses, saving checkpoints, managing the pause menu, reducing UI text overflow, and scene management.

Clarifying game mechanics

I'm analyzing bosses, hazards, and projectile effects to ensure they align with game progression and player immersion. This involves refining combat dynamics and evaluating potential inconsistencies.

Mapping out battle intricacies

Piecing together battle structure, ensuring smooth progression and coordination.

Executing Python script

Testing headless Chromium, capturing screenshots, and evaluating browser errors.

Setting up localhost

I’m digging into setting up a Python HTTP server on localhost, ensuring no external browser plugins or services are needed, and maintaining offline reporting constraints.

Setting up the environment

I'm thinking about using Python's http.server to set up an HTTP server. This approach avoids external tools or dependencies, making it a solid choice.

Navigating script and policy

I’m examining the Chromium script and policies to ensure tools like Playwright with bundled Chrome are compliant with localhost rules and testing requirements. Hm, that's interesting.

Testing browser behavior

I'm evaluating how various functions impact a runner's logic, using "about:blank" and network requests, while ensuring the app's security policies are intact.

Coordinating elements

I’m gathering data on combining all assets into a single file, aiming for a total size of around 262KB, and ensuring the file is verified before forcing a download at the end of testing.

Testing localStorage persists

I’m setting up localStorage mocks and using Playwright's page.set_content to inject JavaScript for testing persistence across pages and reloads.

Gathering info on imaging tools

I’m piecing together details on inspectimages, considering open_image, costs, and the absence of OCR.

Evaluating menu appeal
I’m considering whether the menu looks inviting.

Preparing test environments

Considering a detailed setup of testing environments, including JS batches and code support, to streamline testing and evaluation.

Bringing together Python and JS

I’m crafting a Python container ASCII, infusing it with embedded JavaScript. This approach efficiently tackles test harness returns and failures, ensuring robust functionality.

Noticing metrics

I’m analyzing our remaining budget and necessary improvements. Ensuring a balanced approach to calibrations and potential equipment issues is crucial.

Addressing gameplay issues

I'm examining nanorepair mechanics and weapon durability. Progressing through these steps, targeting performance optimization and effective testing.

Balancing efficiency

Managing abundant resources while ensuring updates every 15 seconds. One test took seconds, highlighting the challenge.

Refining matchmaking logic

I’m tweaking the matchmaking formula by evaluating various metrics like skill, rating, and adaptability. This ensures players are paired by consistently considering these factors in the game's ranking system.

Rolling through transitions

OK, let me see. I'm checking how core timeout and boss stun interactions unfold, particularly in phase 3. Progressing through 120 frames, I’m starting to see clearer patterns.

Balancing knife upgrades

I’m piecing together knife damage upgrades to ensure fair gameplay. Progress involves tweaking attack power without overshadowing other weapon choices, aiming for a balanced endgame.

Navigating layout issues

I'm addressing mobile buttons fitting but desktop panel issues, resulting in overflow. Adjusting menu to a horizontal layout might solve the problem.

Evaluating progress

I’m assessing the progress, considering optional elements, and addressing critical bugs like "nano infinite repair charges." Additionally, planning to add a test report and zip it for future reference.

Assessing potential issues

I’m checking for endless work and latent crashes with TIER_COLORS. Drawing functions need refinement, especially with undefined text and fill style errors.

Updating tier color logic

I’m fine-tuning the tierColor function to avoid hard-coding, ensuring an explicit minimum index for safe mapping with TIER_COLORS.

Enhancing gamepad functionality

Working through the gamepad's UI, aligning navigation and input handling to ensure smooth gameplay without leaving the menu.

Presenting the plan

I’m outlining HTML file deliverables, avoiding non-essential files, and focusing on creating a zip package with a report. Also, I’ll test collision handling.

Focusing on key areas

Conce...

Testing and fine-tuning

I’m testing various elements, ensuring they meet reliability and performance criteria.

Analyzing firearm efficiency

Grasping the gun's durability, aiming, and tremors, I'm analyzing the ammo needed for battle. Progressing nicely through each consideration.

Taking a closer look
Need to review the screenshot of the policy report for clarity.

Assessing progress

I’m analyzing infinite mode discrepancies, including item duplicates and milestone skipping. Fixes are being scoped to ensure consistency and balance.

Mapping out elite placement

I'm thinking about ensuring elite enemies always precede the boss, especially on floor 19, to maintain narrative coherence and gameplay balance.

Assessing weapon impacts

OK, let me see. The machete's bleed effect at a low floor level seems too strong and might need adjustment for balance.

Evaluating details

I'm working through the implications of adjusting the original specs for safety and functionality, ensuring the latest QA keys are included for effective testing and problem resolution.

Organizing next steps

I’m pulling together progress calls, refining testing details, focusing on streamlined controls and accurate saving features, and ensuring the game runs smoothly on Chrome.

Summarizing influences

I’m refining the report by incorporating visual influences and fixing frame rates. The analysis includes weapon timings, boss mechanics, and GPU performance, with a focus on precise testing and conclusions.

Crafting final steps

OK, let me see. Finishing final verification script, routing, and checkpoints. Evaluating gold economy after boss fights by factoring in props and enemies. Ready to simulate pretend runs.

Tweaking enemy balance
Trying a new economy scale and tweaking enemy rewards to ensure the game remains challenging and fair.

Balancing gameplay

Adjusting boss rewards, aiming to streamline progression and enhance satisfaction.

Mapping out final details

Calculating enemy spawn, loot, and map destruction balance to optimize performance. Testing and ensuring safe HTML injection practices.

Finalizing and validating

Ensuring all components, including Markdown and JSON files, are ready. Testing and debugging for accuracy, excluding some optional elements, to maintain precision. Progress is steady and thorough.

Testing mechanics

I’m digging into onKill hooks, combat mechanics, and item tier scaling. Adjustments are necessary to ensure consistent outcomes and a balanced experience. Progress is steady, with a clear focus on stability.

Evaluating progress

I’m assessing the user's progress, examining hitstop40 implementation, screen reduction, and long TTK tuning. Ensuring final benchmarks and report adjustments before delivery.

Piecing together hardware details

Collecting specifics on GPU sampling, touch controls, and viewports. Ensuring detailed report architecture compatibility.

Drafting shadow report

I'm working on a report detailing internal game instructions, weapon lists, and character movements, ensuring data zones and reproducible states are properly documented.

Identifying unique traits

I’m recognizing distinctions between clone bosses and unique bosses, focusing on equipment, class, and weapon behavior differences.

Ensuring clarity

Streamlining the game report and testing outcomes to guarantee all results are crucially examined and accurately reported, reflecting balanced, enjoyable gameplay.

Revisiting the approach

Piecing together the final notes, ensuring all criteria are met, and keeping the HTML format for the report. Progressing towards refinement.

Piecing together the game

I’m compiling a comprehensive report on the Chinese game finalNOW, focusing on a single HTML file and integrating key instructions and screenshots for clarity.

Evaluating automation tests

OK, I’m assessing the outcomes of automation tests, noting successful passes and some challenges with specific tests, particularly in game functions and local storage.

Worked for 47s

回答

《电梯大战 2026》单文件可玩版

下载游戏:ELEVATOR_WAR_2026.html

文件约 263 KB,包含全部代码、数据、程序化画面和合成音效,无外部资源依赖。保存到本机后,用浏览器打开,点击「开始行动」。

运行说明与测试报告 · 自动化测试原始记录

已整合的内容

完整主线覆盖 B1 教学 → A 栋 100 层上行 → B 栋 100 层下行 → 第 201 关最终核心。包含 51 个武器条目、永久砍刀升级、耐久断裂、共享弹药、空枪投掷、槽满替换、词缀、商店与强化。

楼层包含 10 个区域、80 套布局数据、12 种特殊层、环境破坏、基础敌人与精英,以及 11 个独立 BOSS 状态机。电梯战、四种面板操作、维修井道、坠梯、最终九子核心阶段均已接入。通关后可进入无尽模式,使用诅咒、超载强化、熔铸和本地排行榜。

菜单提供设置、图鉴、种子输入、存档导入导出;键鼠、手柄和触屏输入均已实现。

开始操作

操作键鼠
移动、攻击WASD、鼠标左键
翻滚、副功能Space / Shift、鼠标右键
拾取与交互E
切换、丢弃1–4 / 滚轮、G
投掷或部署、装填Q、R
背包、暂停I、Esc
调试面板反引号 `

调试面板可给予任意武器、跳层、显示碰撞网格和启动压力测试。最终 BOSS 的跳层序号为 201

测试结果与边界

已完成 21 项基础自检、51 个武器行为调用、全部关卡生成、BOSS 阶段、电梯分支、检查点恢复,以及模拟手柄和触屏测试,最终测试没有记录到页面运行异常。自动清敌的端到端测试走过了 0–201 全路线并触发通关解锁。

仍有未达到或未经完整实测的验收项: 部分装备配置的 TTK 未落入指定区间;压力测试最终一轮约为 56–60 FPS,但重复测试中曾出现约 54 FPS;3–5 小时人工通关、无尽长期平衡、Safari、实体手柄及本地文件存档的真实跨刷新持久化尚未完成实机验证。报告也明确记录了数值调整和镜像 BOSS 等机制的实现取舍。

このQ&Aを共有