Add v1.2 development quest progression and experimental battle runtime
This commit is contained in:
@@ -0,0 +1,110 @@
|
||||
# v1.2 实施记录与阶段交接
|
||||
|
||||
状态日期:2026-11-08。开发分支:`develop/v1.2.0`。当前版本:**1.2.0.dev1**;原始资料基线:Android **1.9.68**。
|
||||
|
||||
任务资料、状态规划器、普通地图/任务/委托战斗编排和界面已经实现,当前进入独立 QA 与运行时集成阶段。原 AIR 已自然完成合成 1-1 离线实验,独立 Python 实验模型也已运行;任意实际阵容的原引擎输入桥接仍在完善,完整集成 QA 正在进行。当前没有全部主线、全部战斗或服务器接受结算的验证结论,也未发布 v1.2 正式标签。
|
||||
|
||||
用户操作见[辅助使用说明](../ranch_assistant/README.md#v12-自动主线与战斗设置)。研究依据和原验收标准见[实施方案](V1_2_PLAN.md)、[任务调用链研究](V1_2_TASK_RESEARCH.md)。本页汇总交接时已收到的阶段证据;最终集成结果尚待回填。
|
||||
|
||||
## 当前实施范围
|
||||
|
||||
| 模块 | 已实现内容 | 代码与证据 |
|
||||
| --- | --- | --- |
|
||||
| 完整任务与地图资料 | 独立资料包保留 1165 个任务、1178 个关卡、337 个 NPC、4269 份脚本,以及任务/地图/收集来源索引。4239 份脚本归入已支持线性类别,主线引用中为 718/720;这些是分类数量,不是任务完成率。 | [资料读取](../ranch_assistant/game_data.py)、[构建工具](../tools/build_progression_data.py)、[资料清单](../ranch_assistant/data/progression_manifest.json)、[支持范围](../ranch_assistant/data/progression_support.json) |
|
||||
| 数据加载 | 任务与索引使用 `progression.json.gz`,地图战斗使用独立 `progression_battles.zip`,按所需关卡延迟读取并校验摘要。保留现有精简 `Catalog`,应用启动不解析 APK,也不一次展开全部地图战斗配置。 | [ProgressionData](../ranch_assistant/game_data.py)、[资料测试](../ranch_assistant/tests/test_progression.py) |
|
||||
| 有状态任务规划 | 接取、前后剧情、本地位置、服务器步骤确认、本地收尾、领奖后继与补链分别建模;保存每个角色的检查点,防止旧快照、重复确认和跨角色状态污染。 | [ProgressionPlanner](../ranch_assistant/progression.py)、[任务研究](V1_2_TASK_RESEARCH.md) |
|
||||
| 任务缺口收集 | 已识别的成年目标击杀、物品及蛋缺口可选择普通地图来源;物品可按条件选择扫荡。检查解锁、位置截获、体力、金币、道具保留和所选战斗能力,结算后重新核对真实库存/击杀。 | [规划器](../ranch_assistant/progression.py)、[引擎集成](../ranch_assistant/engine.py) |
|
||||
| 委托调度 | 全量规划器负责已支持的委托步骤,既有 `QuestPolicy` 继续拥有启用、城市、接取、实战许可和交付保护。候选委托检查整份已知需求,支持日切刷新;旧委托规划器不会同时重复执行。 | [QuestPolicy](../ranch_assistant/quests.py)、[规划器](../ranch_assistant/progression.py)、[Engine](../ranch_assistant/engine.py) |
|
||||
| 战斗与事件编排 | 普通地图、任务内嵌战斗、任务通关战斗分别开始和结算;地图奖励事件独立完成,隐藏战斗重新检查能力。包含战败、取消、模型时钟等待、未知结果与恢复保护。 | [BattleOrchestrator / BattleJournal](../ranch_assistant/battles.py)、[编排测试](../ranch_assistant/tests/test_battle_orchestration.py) |
|
||||
| 用户界面与配置 | “自动主线”的任务状态、推进策略、模式选择和“战斗记录”已接入后台引擎。规则自动保存、按账号/角色隔离,并纳入统一策略导入/导出;顶部绿色“开启”/红色“停止”统一执行。 | [任务界面](../ranch_assistant/progression_gui.py)、[主界面](../ranch_assistant/gui.py)、[策略导入导出](../ranch_assistant/policy_io.py)、[界面测试](../ranch_assistant/tests/test_progression_gui.py) |
|
||||
|
||||
## 三条战斗路径
|
||||
|
||||
| 路径 | 当前用途和证据 | 边界 |
|
||||
| --- | --- | --- |
|
||||
| 早期普攻估算 | 使用简化战斗单位和有限公式做离线胜负/耗时估计,保留为研究工具。 | 不负责应用中的普通挑战或任务结算,不代表原引擎执行。见[估算实验](V1_2_OFFLINE_EXPERIMENT.md)、[估算工具](../tools/battle_estimate_v12.py)。 |
|
||||
| 原始 AS3/AIR 内核 | 已通过原始 `BattlePanel` 自然完成合成阵容的 1-1 离线战斗,取得实际战场统计与原检查,样例 `cheatNum=0`。原版模式是应用默认选择。 | 已证明的范围仅限该离线样例;任意实际阵容的数据桥接、任务路线、资源匹配和广泛覆盖仍待集成验证。当前原版适配器尚未验证支持线上开战/结算,尚未验证的请求会被能力检查阻止。见[适配器](../ranch_assistant/battle_runtime.py)、[原引擎实验说明](V1_2_RUNTIME_IMPLEMENTATION.md)。 |
|
||||
| 独立实验模型 | `ExperimentalBattleRuntime` 在单独 Python 进程中执行 AP、出场、移动、攻击、已知技能及自然终局,输出实际模型轨迹和统计,已经接入应用编排。 | 使用原始数值资料,仍包含机制近似与遗漏;必须显式选择实验模式,不能自动降级混入原版模式。完整集成、原引擎对拍和真实账号验证待完成。见[模型实现](../ranch_assistant/battle_simulator.py)、[机制与测试说明](V1_2_SIMULATION_IMPLEMENTATION.md)。 |
|
||||
|
||||
实验模型已实现技能 **3、5、7、9、38 的部分机制**,以及实际模型轨迹中的击杀、存活、AP、剩余时间、伤害与异常记录。出场、移动、攻击与技能会改变战场状态,胜负由模型运行产生;没有保证胜利、修改原始伤害或清空异常来构造结算。配置自带的缩放按其原有含义处理。
|
||||
|
||||
当前结构准入统计:地图战斗配置 **941/2512**,任务内嵌战斗配置 **106/199**。另有 **12 场合成阵容地图执行自然胜利**。准入数表示近似模型能接收这些配置;既不是原版机制覆盖率,也不是实际账号通关率。不能把 1178 个地图条目、各难度战斗配置数和可执行场次数混为一谈。
|
||||
|
||||
技术契约中,原版路线要求运行时支持且结果具备原版结算资格;实验结果始终标记 `execution_mode='experimental'`、`approximate=True`、`faithful=False`、`settlement_eligible=False`。编排仅在显式实验模式、自然完成、定位匹配、无异常且 `experimental_settlement_eligible=True` 等条件成立后,才允许进入对应的实验结算分支。该标志是本地集成条件,不证明服务器接受或原版完整校验通过。诊断、遗漏和异常随记录保存,原版样例的零检查分也不替代实际阵容验证。
|
||||
|
||||
## 调度与恢复约定
|
||||
|
||||
| 场景 | 当前路线 | 关键约束 |
|
||||
| --- | --- | --- |
|
||||
| 普通地图战斗 | 能力及资源预检 → `stageService/stageStart` → 事件分流 → 运行时 → 成功时 `battleService/battleEnd` → 对应战绩记录 → 刷新核对 | 当前位置关联任务时优先交给任务路线;不能直接当普通地图或扫荡。 |
|
||||
| 普通地图奖励事件 | 开始响应中的已发奖励 → 本地奖励/事件记录 → 刷新 | 不运行战斗,不额外调用普通战斗结算,不把奖励事件记成战斗胜利。 |
|
||||
| 任务 `battle` | `battleService/battleStart` 的任务分支 → 本步骤内嵌配置 → 实际运行 → `taskService/taskCompleteStep` 携带 `battleData` | 主线、支线与委托使用同一类任务路线;接取/交付仍受所属策略限制。 |
|
||||
| 任务 `passStage` | 同一任务开始分支 → 引用地图/难度的战斗配置 → 任务步骤结算 → 已确认的本地通关/解锁收尾 | 不额外调用普通 `battleEnd`,也不用扫荡替代该任务专属战斗。 |
|
||||
| 任务缺口收集 | 已识别来源 → 普通地图战斗或合规扫荡 → 刷新目标计数/库存 → 重新规划任务 | 来源任务信息只用于诊断;收集动作不能直接确认任务步骤。扫荡不提供击杀信用。 |
|
||||
| 扫荡 | 既有 `SweepRunner` 处理三个难度已通关的普通关卡,奖励事件仍单独分流 | 检查特殊关卡、任务位置、开放状态、资源与队伍;逐关规则和本日次数继续由“自动扫荡”管理。 |
|
||||
| 战败或自然战斗时间耗尽 | 保留实际失败结果,走对应失败/战绩路径并累计停止条件 | 不提交胜利结算或本地提前推进任务;工作进程超时、取消、未知结果另归待核对。 |
|
||||
|
||||
代码入口:[编排](../ranch_assistant/battles.py)、[引擎请求构建](../ranch_assistant/engine.py)、[扫荡](../ranch_assistant/sweeping.py)。客户端证据:[任务研究](V1_2_TASK_RESEARCH.md)、[地图分支](STAGES_DAILY.md)、[方案调用链](V1_2_PLAN.md#请求流程必须按战斗类型区分)。
|
||||
|
||||
规划器拥有任务客户端游标与普通剧情检查点。`none` 步骤也先取得服务器步骤确认,再执行后续剧情和本地收尾;不能因为没有资源需求就跳过确认。服务器使用的一基任务步骤和战斗定位中的零基步骤分别转换。领奖响应中的已接取后继与仅解锁任务分开处理,补链按已知图和条件核对,不按任务编号递增猜测后继。
|
||||
|
||||
同账号的请求与战斗串行,战斗计算在独立工作进程中执行。发送写请求前持久化 `BattleJournal`,任务状态和剧情检查点按账号/角色保存;战斗或任务存在未核对状态时,暂停可能改变阵容、资源的牧场、赠礼及任务等冲突写操作,其他账号独立运行。实际目录由账号工作区提供,策略导出不携带凭据、执行日志、待核对状态或服务器进度。
|
||||
|
||||
超时、开战后停止、结算响应未知、进程中断或未支持的隐藏事件都会保留 pending 记录。恢复后只用新取得且角色匹配的服务器快照核对;充分证据可解除阻塞并继续已保存的剧情收尾。旧通关记录、体力变化、未变化的步骤或单独的本地胜利不能证明未知请求已完成。核对过程不重放未知的接取、开战、提交、结算、领奖或战绩写请求;证据不足就继续阻塞,不能靠导入策略、重启或删除日志假装成功。
|
||||
|
||||
### 离线时钟与实际经过时间
|
||||
|
||||
独立离线模拟按模型时钟计算,可比战斗逻辑耗时更快返回,不为模拟时长休眠。实验结果声明需要真实时钟等待;应用编排从开战确认后开始计时,只补足尚未经过的战斗时长,等待可取消,取消后保留待核对状态。该等待不能证明网络结算已获服务器认可。
|
||||
|
||||
模型中的自然时间上限到期属于已完成的战败;工作进程墙钟超时或资源上限属于未完成执行,不携带可结算战果。原 AIR 样例仍按原生时钟运行;加速离线研究不能用于假定线上时序可省略。相关覆盖见[编排测试](../ranch_assistant/tests/test_battle_orchestration.py)和[模型测试](../ranch_assistant/tests/test_battle_simulator.py)。
|
||||
|
||||
## 尚不支持与待验证内容
|
||||
|
||||
- **剧情与入口:**30 份特殊选择等脚本(含 2 份主线引用)、4 类特殊接取入口和任务1001006第4步的 `task1` 抽蛋钩子尚不支持。活动、羁绊、未知任务类别及未验证引导按原因阻塞。线性脚本支持包含已识别的展示与布尔答案事件,不代表完整脚本解释器。具体分类见[支持清单](../ranch_assistant/data/progression_support.json)。
|
||||
- **场地机制:**实验模型拒绝未支持的战斗/魔物控制器、触发器、非歼灭目标、保护/破坏单位及活动场地区域;动态控制器/技能生成目标也不是收集索引的完整来源。
|
||||
- **技能和运动:**技能 3、5、7、9、38 仍是部分移植,其他技能逐项列为遗漏。直线移动、碰撞、惯性、击退、弹道、初始冷却、皮肤动作及随机流存在近似;部分装备效果与 `sunFire`、`moonHeal`、`deadBoom` 等属性机制未实现。可运行的模型仍须披露遗漏,不承诺原版胜负一致。
|
||||
- **原始数值与资源事实:**资料来自原始 APK,实际阵容需完整成长、突破、潜能、装备/聚合属性、好感、升星及队伍等输入,不能用界面参考属性替代。资料摘要验证不等于线上热更新匹配;任意实际阵容的原 AIR 桥接和与原引擎相同时钟/操作/随机流的对拍仍待完成。
|
||||
- **实际游戏:**本轮开发验证未执行真实游戏 API,真实账号的任务、开战、失败、结算、奖励、进度和服务器接受条件仍待用户手动验证。软件在用户开启策略后,可按配置和能力检查自动执行已支持操作;PVP、排行榜/BOSS及特殊活动不属于当前交付承诺。
|
||||
|
||||
## 验证记录
|
||||
|
||||
收尾常规回归检查 **497 项**:首轮 **493 项通过、4 项错误**;4 项均为旧界面测试在切换页面后立即访问尚未完成的后台魔物表格,补齐异步等待后,原 4 项复测全部通过。此结论来自一次全量常规运行及定向复测,并非修正后再次全量运行。常规回归不包含 **14 项原 AIR 长时间试跑**;真实游戏请求未执行。账号回归另有 **13 项通过**,86 份 Python 文件语法检查及暂存内容空白检查通过,未出现 Qt 表格所有权告警。
|
||||
|
||||
原版运行时已用本地缓存阵容离线完成三条战斗路线,原回调样例 `cheatNum=0`;Engine 到原版适配器的最终集成及完整装备/皮肤场景仍未验收,自动原版开战准入保持关闭。实验模式可对明确支持的配置执行,不代表全部主线可用。以下表格保留各阶段的定向验证记录,不能将各组数量相加。
|
||||
|
||||
以下是交接时收到的实现阶段记录,非本文编辑时重新执行的测试。测试组可能相互重叠,不相加为全量总数;常规回归结果见上文,原版运行时与真实账号集成仍待完成。
|
||||
|
||||
| 验证组 | 已报告证据 | 适用边界与复查入口 |
|
||||
| --- | --- | --- |
|
||||
| 数据与规划 | **145 项定向测试通过**;禁用 socket 后检查 **6 份本地日志中的 514 个快照,规划器异常 0 次** | 只读快照和离线规划,不证明写请求或战斗成功。[数据/规划测试](../ranch_assistant/tests/test_progression.py);不公开日志原文及账号资料。 |
|
||||
| 战斗编排 | **66 项编排测试通过** | 模拟服务/运行时下的路线、资源、事件、时钟、取消、异常和恢复保护。[编排测试](../ranch_assistant/tests/test_battle_orchestration.py)。 |
|
||||
| 选定集成回归 | **212 项选定回归通过** | 为实现阶段选定集合,包含重叠测试;不能视作最终全量 QA。[测试目录](../ranch_assistant/tests)。 |
|
||||
| 界面定向验证 | **30 项界面目标测试通过** | 任务/记录界面、模式、配置和交互的目标验证,非真实账号实战。[任务界面测试](../ranch_assistant/tests/test_progression_gui.py)、[规则管理测试](../ranch_assistant/tests/test_rules_management.py)、[策略配置测试](../ranch_assistant/tests/test_policy_config.py)。 |
|
||||
| 独立实验模型 | **38 项测试通过**;结构准入 **941/2512** 地图配置、**106/199** 任务内嵌配置;**12 场合成地图执行自然胜利** | 模型证据,不是原 AIR 对拍、全部关卡或真实账号验收。[模型测试](../ranch_assistant/tests/test_battle_simulator.py)、[模型说明](V1_2_SIMULATION_IMPLEMENTATION.md)。 |
|
||||
| 原 AIR 实验 | 合成 1-1 自然完成,实际原始 `BattlePanel` 统计与检查,样例 **`cheatNum=0`** | 仅该合成离线场景;实际阵容桥接和广泛覆盖待验证。[原版适配器测试](../ranch_assistant/tests/test_battle_runtime.py)、[原引擎说明](V1_2_RUNTIME_IMPLEMENTATION.md)。 |
|
||||
| 完整集成与真实账号 | 独立 QA 正在运行;原版/模型最终集成结论待回填;本轮开发验证未执行真实游戏请求 | 不能据局部结果标记全量通过、服务器接受或发布就绪。 |
|
||||
|
||||
从仓库根目录运行相应离线回归,使用 `-B` 避免生成字节码缓存;界面测试需要已安装的项目依赖。下列是复查命令,不表示本文已执行或这些命令对应所有历史测试组。
|
||||
|
||||
```console
|
||||
python -B -m unittest discover -s ranch_assistant/tests -p "test_progression.py" -v
|
||||
python -B -m unittest discover -s ranch_assistant/tests -p "test_battle_orchestration.py" -v
|
||||
python -B -m unittest discover -s ranch_assistant/tests -p "test_progression_gui.py" -v
|
||||
python -B -m unittest discover -s ranch_assistant/tests -p "test_battle_simulator.py" -v
|
||||
python -B -m unittest discover -s ranch_assistant/tests -v
|
||||
```
|
||||
|
||||
原 AIR 准备与运行涉及单独的本地运行时资源,依赖说明留在[原引擎技术文档](V1_2_RUNTIME_IMPLEMENTATION.md),不作为用户启动辅助的额外配置步骤。
|
||||
|
||||
## 阶段交接与后续验收
|
||||
|
||||
| 后续工作 | 完成判据 | 当前状态 |
|
||||
| --- | --- | --- |
|
||||
| 独立集成 QA | 对当前整合代码核对回归输出、失败/跳过原因、任务服务确认与本地收尾、路线分流、取消/时钟、配置和多账号隔离,记录准确命令与测试数量。 | 进行中;最终结果待回填。 |
|
||||
| 原版输入桥接 | 任意受支持实际阵容快照能按原始规则构建输入,保持属性、站位、技能、检查与输出语义;能力检查只放行已验证场景。 | 完善中;合成 1-1 已证明原内核能够自然完成。 |
|
||||
| 模型最终集成 | 真实模型进程在普通地图、任务 `battle`、`passStage` 和委托路线产生可追踪结果;保留近似、遗漏、异常、资格标志,并验证真实时钟等待与停止恢复。 | 编排已接入;独立集成与原引擎对拍待完成。 |
|
||||
| 用户手动实际验证 | 本轮由用户操作真实账号,分别核对奖励事件、胜负、体力与物品、经验、任务/地图进度和未知响应恢复;写请求不重复。 | 尚无本阶段服务器验收结论;开发验证继续使用离线资料和模拟服务。 |
|
||||
| 扩展覆盖 | 每次增加脚本、技能或控制器,都有明确支持清单、可复现轨迹与对应回归,覆盖不足继续显示原因。 | 按明确场景逐步增加,不承诺全关卡。 |
|
||||
| 正式发布 | 完成最终验证与遗留问题评审,文档和版本一致。 | 验证完成前保持开发版;尚未创建稳定标签或合入main。 |
|
||||
|
||||
接续工作先读取各运行时的最新技术记录和独立 QA 结果,再更新本页、[方案阶段状态](V1_2_PLAN.md)及两份 README。不得沿用早期“只完成静态资料”的描述,也不能把局部原引擎成功或模型准入解释成全主线完成。保持原数值基线的离线近似实验继续推进;本轮真实账号联网验证由用户手动进行,软件在用户开启策略后可自动执行已支持操作。
|
||||
+31
-22
@@ -1,21 +1,31 @@
|
||||
# v1.2 预研:主线任务、普通挑战与战斗委托
|
||||
# v1.2 方案与实施状态:主线任务、普通挑战与战斗委托
|
||||
|
||||
日期:2026-11-08。基线:辅助 v1.1.1、原始 Android APK 1.9.68。
|
||||
状态:已完成配置恢复和重点调用链研究,并运行了离线普攻估算原型;忠实执行原始规则的独立战斗引擎尚未跑通,未提交模拟挑战或验证服务器接受结果。
|
||||
状态更新:2026-11-08。研究起点:辅助 v1.1.1、原始 Android APK 1.9.68;当前实现为 `develop/v1.2.0` 的 **1.2.0.dev1**。
|
||||
状态:完整任务资料、有状态任务/对话/补链/收集规划、普通地图与任务/委托战斗编排、界面及策略保存已经实现。原 AIR 已通过原始战斗面板自然完成合成 1-1 离线实验,取得实际统计与检查,样例 `cheatNum=0`;任意实际阵容桥接仍在完善。独立实验模型已接入编排,完整集成 QA 正在运行,服务器接受结果仍未验证。验证完成前保持开发版;尚未创建稳定标签或合入main。
|
||||
|
||||
实验安排:按用户本轮授权,离线解析、运行壳和战斗实验直接推进,无需再次确认。预研中的真实账号接任务、开战、结算与领奖由用户手动操作;本轮不自动进行联网游戏实验。
|
||||
实验安排:继续推进离线解析、运行壳和战斗实验。本轮真实账号接任务、开战、结算与领奖验证由用户手动操作;软件在用户开启策略后,可按配置和能力检查自动执行已支持操作。
|
||||
|
||||
新增的[离线实验与实机采样说明](V1_2_OFFLINE_EXPERIMENT.md)记录了可运行的函数、示例结果和本地对比流程。它是有限机制的估算实验,不能替代下面 P1/P2 要求的原引擎运行与对拍。
|
||||
当前交接与准确验证记录见[V1_2_IMPLEMENTATION.md](V1_2_IMPLEMENTATION.md)。下文保留研究证据与验收标准;[早期普攻估算](V1_2_OFFLINE_EXPERIMENT.md)、[原 AIR 运行实验](V1_2_RUNTIME_IMPLEMENTATION.md)、[独立实验模型](V1_2_SIMULATION_IMPLEMENTATION.md)是不同路径,不能互相替代覆盖或对拍证据。
|
||||
|
||||
## 当前阶段状态
|
||||
|
||||
| 范围 | 当前实现与验证状态 |
|
||||
| --- | --- |
|
||||
| 数据和规划 | 独立索引资料包包含1165任务、1178关卡、337 NPC、4269脚本;4239份线性脚本支持,主线引用718/720。145项定向测试通过;禁用socket检查6份本地日志中的514个快照,规划器异常0次。30份特殊选择等脚本(含2份主线)、4类接取入口和任务1001006抽蛋钩子仍不支持。 |
|
||||
| 调度和界面 | 已实现服务器步骤确认后再执行本地剧情收尾、补链、缺口收集、QuestPolicy拥有的委托调度、普通地图奖励事件/战斗分流、三难度全通后扫荡及任务专属战斗路线;编排66项、选定回归212项、界面目标30项为阶段记录,集合有重叠,不相加为全量总数。 |
|
||||
| 原 AIR | 合成1-1已自然完成,使用实际原始BattlePanel统计与检查;当前只是局部离线能力证明,任意实际阵容桥接和广泛支持仍待验证,默认原版模式不放行未验证开战。 |
|
||||
| 实验模型 | 独立进程模型已有38项测试;结构准入941/2512地图战斗配置、106/199任务内嵌配置,12场合成地图执行自然胜利。AP、出场、移动、攻击及技能3/5/7/9/38部分实现,仍有近似与遗漏;已接入应用,须显式选择实验模式。 |
|
||||
| 集成与发布 | 独立完整QA和原版/模型最终集成结论待回填;本轮开发验证未执行真实游戏请求,实际账号验收由用户手动进行。维持开发版,不承诺全部主线或服务器接受结算。 |
|
||||
|
||||
## 可行性结论
|
||||
|
||||
**有技术可行性,但需要恢复一个能够执行原始规则的战斗引擎。任务接取接口不是主要难点。**
|
||||
**原始战斗内核已有单场合成离线成功证据,任务与战斗调度已实现;实际阵容桥接、机制覆盖与完整集成仍需验证。**
|
||||
|
||||
手机可以不启动游戏;电脑辅助仍需登录并与服务器通信。电脑侧可以负责选择任务、准备阵容、运行战斗、提交实际结果、核对任务进度,再继续下一步。
|
||||
战斗必须能够自然得到胜利、失败或超时;强度不够时应停下或等待培养。按原始规则运行不代表任何阵容都能推过主线。
|
||||
|
||||
本次确认了客户端会在本地创建战场、执行AI与技能,再从战场状态生成结算数据。
|
||||
但源码只能说明客户端行为,不能证明服务器不做额外校验,也不能证明一个尚未实现的替代引擎会被服务器接受。
|
||||
但源码和局部离线执行只能说明对应客户端行为,不能证明服务器不做额外校验,也不能证明现有实验模型的结果会被服务器接受。
|
||||
这是后续联调需要验证的条件,不能用扫荡的简化数据代替普通挑战数据。
|
||||
|
||||
## 本次已经确认的证据
|
||||
@@ -25,7 +35,7 @@
|
||||
| 原始APK身份 | SHA-256为 `01678ee3a8465d818d32cbbd94baa0d8253b04b4c57b70ebc5544ed341f1015d`,与原始分析对象一致;未使用伤害修改包 | REA `open_binary` 与本次静态归档检查 |
|
||||
| 主程序 | `assets/MYRMain.app` 为4,196,806字节的FWS/SWF,版本字节为50,SHA-256为 `c6838331a198a22ffa486cbf61cc74c97619e011bc3364c8bb8dc99e269036cf` | [配置与文件清单](V1_2_BATTLE_INVENTORY.json) |
|
||||
| 完整资料可恢复 | 1,178条关卡记录、3,534条难度记录,其中2,512个非空战斗字典;1,165条任务、199个非空任务步骤战斗字典、749种魔物、266组技能配置 | 从原APK中解压并用AMF解析,非空字典不等同于已验证可挑战关卡 |
|
||||
| 当前辅助资料不完整 | 当前目录只保留83条每日委托任务,没有完整技能表/场地表,关卡难度里的战斗字典已被提取脚本剔除 | [提取脚本](../tools/extract_ranch_catalog.py#L70)、[本次清单](V1_2_BATTLE_INVENTORY.json) |
|
||||
| 预研起点的辅助资料不完整 | 既有精简catalog只保留83条每日委托任务,关卡战斗字典被剔除;现已保留原catalog并新增完整任务索引、延迟读取的战斗资料和实验战斗表 | [提取脚本](../tools/extract_ranch_catalog.py#L70)、[原清单](V1_2_BATTLE_INVENTORY.json)、[当前实施](V1_2_IMPLEMENTATION.md) |
|
||||
| 战场在客户端生成 | 关卡配置构造成 `BattleVo`,加入所选玩家队伍,再创建 `BattlePanel` | [BattleCenter.as:36](as3/scripts/net/pixvi/myr/center/BattleCenter.as#L36) |
|
||||
| 战斗有实际循环 | 每帧处理控制器、场地区域、触发器、AI、碰撞、子弹;另有按秒触发的逻辑 | [BattleGround.as:1718](as3/scripts/net/pixvi/myr/battle/BattleGround.as#L1718)、[1844](as3/scripts/net/pixvi/myr/battle/BattleGround.as#L1844) |
|
||||
| 胜负不只有消灭敌人 | 有时间条件、我方全灭、保护/破坏目标、波次和主动撤退等判断 | [BattleGround.as:1141](as3/scripts/net/pixvi/myr/battle/BattleGround.as#L1141) |
|
||||
@@ -83,15 +93,15 @@ REA归档检查的父证据为 `ev_3bb779224b3b2f1754b820542d4efc08d829f6da1e106
|
||||
证据:[BattlePanel.as:262](as3/scripts/net/pixvi/myr/panel/battle/BattlePanel.as#L262)、[314](as3/scripts/net/pixvi/myr/panel/battle/BattlePanel.as#L314)。
|
||||
|
||||
资源还必须与实际服务版本匹配。APK内配置是本次离线基线,不等同于该账号当前热更新资源。
|
||||
后续建立资料包时要带版本、文件摘要和必要的热更新来源记录,避免把旧敌人/技能参数混进新版本战斗。
|
||||
现有资料包已携带原APK版本、来源及文件摘要;线上热更新匹配仍待验证,不能把静态摘要通过解释为实际服务资源一致。
|
||||
|
||||
## 推荐的引擎路线
|
||||
|
||||
| 路线 | 用途与可行性 | 本次结论 |
|
||||
| --- | --- | --- |
|
||||
| Python按公式简单估算 | 可用于阵容强度预览;无法覆盖帧序、弹道、复杂技能和场景触发 | 不作为实际挑战的结算引擎 |
|
||||
| 原始AS3/AIR战斗内核加独立运行壳 | 更适合保持原有逻辑和数值语义,也可作为其他实现的对照基准;需补依赖并切开登录、平台SDK、资源和展示入口 | 优先验证;还没有成功运行的原型 |
|
||||
| 将战斗逻辑逐步移植到独立工作进程 | 能满足长期无需手机、无需完整游戏客户端的目标;需要覆盖度管理和严格对拍 | 运行壳验证后再确定范围;不可承诺一次覆盖全部技能 |
|
||||
| 原始AS3/AIR战斗内核加独立运行壳 | 更适合保持原有逻辑和数值语义,也可作为其他实现的对照基准;需补依赖并切开登录、平台SDK、资源和展示入口 | 原始BattlePanel已自然完成合成1-1;实际阵容桥接及广泛能力仍待验证,尚不能据此认定支持全部原版战斗 |
|
||||
| 将战斗逻辑逐步移植到独立工作进程 | 能满足长期无需手机、无需完整游戏客户端的目标;需要覆盖度管理和严格对拍 | 独立Python实验模型已实现并接入编排,38项模型测试;近似与遗漏明确披露,完整集成和原引擎对拍待完成 |
|
||||
| 直接把完整游戏SWF交给替代播放器 | 依赖AIR接口、显示列表、资源和原生扩展的兼容性 | 本次不能认定可用,也不作为交付前提 |
|
||||
|
||||
AIR官方ADL文档支持开发期运行SWF,并提供命令行模式;但命令行模式的 `stage` 为null、没有显示列表。
|
||||
@@ -102,8 +112,7 @@ AIR官方ADL文档支持开发期运行SWF,并提供命令行模式;但命
|
||||
Ruffle官方兼容性页仍将AS3语言与API兼容性分别列为未全覆盖;这也不能直接推出本游戏可运行或一定不可运行,必须做本游戏的兼容性验证。
|
||||
来源:[Ruffle兼容性说明](https://ruffle.rs/compatibility)。
|
||||
|
||||
当前PATH可发现Java,但未发现ADL、mxmlc或FFDec命令;这只是PATH范围内的观察,不等同于整机没有安装。
|
||||
AS3运行壳尚未执行。新增 Python 普攻估算实验只覆盖下文列明的有限机制;AS3运行壳仍是下一阶段的工程验证项。
|
||||
预研初期的PATH检查只发现Java;后续已准备本地AIR运行资源并执行合成离线战斗,最新依赖与运行证据见[原引擎技术记录](V1_2_RUNTIME_IMPLEMENTATION.md)。早期Python普攻估算仍是独立研究工具,不是当前应用的实验战斗模型。
|
||||
|
||||
## v1.2 分阶段实施方案
|
||||
|
||||
@@ -116,8 +125,8 @@ AS3运行壳尚未执行。新增 Python 普攻估算实验只覆盖下文列明
|
||||
| P4 主线和委托调度 | 主线接取、步骤推进、地图挑战、任务专属战斗、提交与领奖;恢复未完成步骤 | 覆盖一个包含非战斗和战斗步骤的任务链;战斗完成后再核对任务状态,不凭本地胜利预先推进 |
|
||||
| P5 扩大覆盖与多账号 | 扩充技能、场景和事件覆盖;独立工作进程、配置导出、诊断与任务界面 | 大列表和战斗不阻塞Qt;角色互不串数据;遇不支持内容、实际战败或资源不足时按策略停止 |
|
||||
|
||||
推荐先交付P0的任务可视化和P1的离线战斗验证,再评估P2/P3的工作量。
|
||||
若独立运行壳与原引擎对拍尚未通过,v1.2就不应宣称已经支持完整自动推主线。
|
||||
当前进度:P0资料和任务可视化已实现;P1取得原AIR合成单场自然完成证据,实际阵容输入仍待完成;P2已有有限机制实验模型,原引擎严格对拍待完成;P3/P4的普通地图、任务和委托编排及模拟测试已实现,真实账号闭环未验收;P5的进程、配置和界面已接入,完整QA及覆盖扩展继续进行。各阶段具体交接见[实施记录](V1_2_IMPLEMENTATION.md#阶段交接与后续验收)。
|
||||
当前局部运行与测试不构成完整自动推主线的验收。
|
||||
大量特殊机制的覆盖成本只有验证具体阵容、敌人、技能与关卡后才能估算,现在给出全部完成日期没有依据。
|
||||
|
||||
## 程序结构与调度
|
||||
@@ -136,7 +145,7 @@ flowchart TD
|
||||
C --> Q
|
||||
```
|
||||
|
||||
建议的模块边界:
|
||||
原方案的模块边界如下;当前实现映射为 `game_data.py`、`progression.py`、`engine.py`、`battles.py` 和两个独立运行时,具体状态见[实施范围](V1_2_IMPLEMENTATION.md#当前实施范围):
|
||||
|
||||
- `game_data`:完整资料包、配置摘要、版本匹配与能力查询;不持有账号Token。
|
||||
- `progression`:任务图、主线/委托步骤分类、地图定位、剧情触发和下一步解释。
|
||||
@@ -150,16 +159,16 @@ flowchart TD
|
||||
关卡开始、任务步骤或结算请求结果不明确时,先记录待核对并查询现状,不自动重发,也不随意重新开始同一场。
|
||||
本地尝试ID用于防止本程序重复执行,不代表服务器提供幂等接口。
|
||||
|
||||
界面增加“自动主线”页,展示已完成/进行中/可接取/条件不足/不支持的任务和下一步;“战斗记录”展示本场队伍、胜负、耗时和阻塞原因。
|
||||
界面已增加“自动主线”页,展示任务状态、位置、需求、对话、下一步与支持原因;“战斗记录”展示上下文、队伍、结果、模式和原因,耗时等执行证据保存在本地日志中。
|
||||
仍复用顶部绿色“开启”与红色“停止”,不再增加“仅监控/执行”两套开关。
|
||||
配置只包含任务范围、可用战队、保留体力、失败停止次数与是否包含委托等偏好,并纳入现有统一导入/导出;服务器通关进度不能靠配置文件设置。
|
||||
|
||||
## 本次预研的边界与待验证项
|
||||
|
||||
- 已证实:原APK身份、配置可以恢复、本地战斗核心与统计采集入口、普通地图/任务分流,以及当前辅助资料被精简的事实。
|
||||
- 工程推断:完整输入、时序、技能与依赖补齐后,独立执行原始规则有可行路径;普攻估算原型已经运行,尚不能证明原始战斗机制的覆盖、准确性和速度。
|
||||
- 未验证:当前线上热更新与APK的差异、独立运行壳的兼容性、动画与时钟完整迁移、随机流复现、具体账号的所有加成是否完整可得、服务器接受真实独立战斗结果的条件。
|
||||
- 已证实:完整静态资料已经进入独立资料包;任务、剧情检查点、补链、收集、委托、编排与界面已实现。原始战斗内核自然完成合成1-1并取得实际统计与检查;实验模型有局部结构准入和合成执行证据。
|
||||
- 工程边界:原AIR单场成功、实验模型执行与早期普攻估算分别评价;原版能力检查和显式实验模式分开,有限技能及场地支持不能解释为全关卡完成。
|
||||
- 未验证:完整集成QA、任意实际阵容的原引擎桥接、线上热更新匹配、完整动画/时钟/随机流对拍、实际角色全部加成与服务器接受结算条件。
|
||||
- 范围:当前方案先覆盖已验证普通关卡和任务战斗。PVP、排行榜/BOSS及特殊活动不纳入首批交付。
|
||||
- 本轮工具不自动登录真实账号或发送任务/战斗写请求;用户手动运行手机游戏,电脑被动记录指定接口。采样准备包括本机代理、USB转发和公开CA证书传输;没有改动1.1.1的辅助执行逻辑。
|
||||
- 本轮开发验证未执行真实游戏请求;真实账号接取、开战、结算和领奖验证由用户手动进行。开发分支已加入v1.2自动策略执行编排;未知写请求保持待核对,不自动重放。
|
||||
|
||||
下一步建议:完成“一场离线普通战斗的忠实运行与对拍”,再开展联网挑战和任务闭环。
|
||||
下一步:完成实际阵容桥接与原版/模型集成,回填独立QA准确结果,再由用户手动核对本轮实际游戏闭环。验证完成前保持开发版;尚未创建稳定标签或合入main。
|
||||
|
||||
@@ -0,0 +1,34 @@
|
||||
# v1.2 privacy audit
|
||||
|
||||
Date: 2026-11-08. Scope: known personal workstation paths and device identifiers in current tracked text, with edits limited to the two legacy tools below and SDK decompiler path comments.
|
||||
|
||||
- Initial scan: 18 occurrences across 17 files (16 local profile paths, one device identifier, one workstation ADB executable path). No matching files outside the authorized edit scope.
|
||||
- Final scan: 1,464 tracked text files checked; zero remaining occurrences of the known identifiers. One binary file was excluded from the text scan. The new audit was checked separately. Results contain filenames and counts only, without the identifier values.
|
||||
- `read_device_battle_assets.py` now accepts `--adb` (otherwise uses PATH) and `--serial`. Actual invocation checks ADB authorization; automatic selection requires exactly one authorized connected device. Import and `--help` perform no discovery, device operations, or writes. Packaged-asset extraction and matching remain available.
|
||||
- `build_battle_v3.py` now requires `--build-tools`, or the explicit `build_tools` keyword argument when called from Python. APK modification, repacking, signing, cache options, and verification logic are preserved.
|
||||
- Removed only the source-local-path JADX comment in each of the 15 Java files listed below. Vendor namespaces, public endpoints, protocol information, and Java logic remain unchanged. Author and contributor attribution was not edited; AttilaNet <zbolink@foxmail.com> remains permitted.
|
||||
|
||||
Validation passed: in-memory Python syntax compilation for both tools; inert imports and both `--help` entrypoints with subprocesses, tool discovery, and file writes forbidden; nine mocked device-selection cases; missing-ADB rejection; static equality of APK build function bodies apart from the configured tool-directory name; Java comparison against the index after Git newline normalization and removal of the permitted comments only; whitespace checks. No ADB process, device/game operation, APK modification, or signing was executed.
|
||||
|
||||
Changed files:
|
||||
|
||||
- `tools/read_device_battle_assets.py`
|
||||
- `tools/build_battle_v3.py`
|
||||
- `analysis/sdk_login/com.diyidan.game.api.DydGameApi.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.common.Constants.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.dialog.LoginDialog.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.entity.impl.DydPlayerModel.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.BaseNetwork2.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.SuccessListener.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.UserNetwork2.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.model.JsonData.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.model.ListJsonDataModel.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.util.AESTools.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.util.DydOkHttpNetwork.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.network.util.DydStringRequest.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.util.JsonUtils.java`
|
||||
- `analysis/sdk_login/com.diyidan.game.util.Utils.java`
|
||||
- `analysis/sdk_login/net.pixvi.ane.dydsdk.functions.LoginFunction.java`
|
||||
- `analysis/V1_2_PRIVACY_AUDIT.md`
|
||||
|
||||
This finding applies to current tracked working-tree text and the new audit, for the exact known identifiers (including ordinary and escaped path separators). It is not an exhaustive search for unrelated personal information, secrets, ignored/untracked files, or publication artifacts. Git history and the index were not changed; older revisions may still contain the removed values. The cleaned files need to be included in the published revision. No feature files, game data, logs, commits, or remote state were changed by this task.
|
||||
@@ -0,0 +1,281 @@
|
||||
# v1.2 original offline battle runtime — development build
|
||||
|
||||
Updated 2026-11-08. The original compiled engine now completes actual offline
|
||||
scenes through `BattleCenter → BattleGround → BattlePanel.battleCompleteHandler`.
|
||||
Ordinary stage, embedded task battle, and task `passStage` each have a completed
|
||||
snapshot-driven native scene with original statistics and original checks.
|
||||
This is executable development functionality; complete game coverage, matching
|
||||
the current live resources, and server acceptance have not been established.
|
||||
No game API actions were performed for this validation.
|
||||
|
||||
**Frozen development checkpoint:** scope stopped at the user's quota request.
|
||||
The fixed bridge completed the cached roster in all three contexts with
|
||||
`cheatNum=0` and two retained player checks per scene. Its actual cached team has
|
||||
two occupied slots. The final identity comparison accepts original decimal-string
|
||||
audit IDs without modifying either output. Revalidation of all three existing
|
||||
executed callback bodies passes; no additional native trial was launched.
|
||||
Automatic native admission is deliberately disabled by
|
||||
`NATIVE_ADMISSION_ENABLED=False` pending final Engine/native/fake-client integration
|
||||
QA. Offline execution remains available. This is an integration checkpoint,
|
||||
not a restriction based solely on untested server acceptance.
|
||||
|
||||
## Public integration contract
|
||||
|
||||
The runtime accepts `BattleRequest` or the equivalent dictionary:
|
||||
|
||||
```python
|
||||
request = BattleRequest(
|
||||
context="ordinary_stage", stage_id="0101", difficulty=1,
|
||||
original_data={"battle": canonical_original_battle},
|
||||
roster=raw_master_snapshot, team="teamB",
|
||||
battle_position={"battleType": "stage", "stageId": "0101",
|
||||
"stageLevel": "1", "taskTypeId": None, "taskStep": 0},
|
||||
)
|
||||
runtime = BattleRuntime() # optional config: {"backend": "original_air"}
|
||||
capability = runtime.inspect(request)
|
||||
result = runtime.run(request, cancel_event=event, timeout=None)
|
||||
```
|
||||
|
||||
`roster={"snapshot": raw_master_snapshot, "team_name": "teamB"}` is also
|
||||
accepted for CLI callers. Both forms normalize to the same native input.
|
||||
An explicit team is required. Conflicting selectors refuse; no default changes
|
||||
`teamB` to `teamA`. Requests are copied once before inspection and execution.
|
||||
`original_data` optionally accepts `source="original_apk"` and the exact pinned
|
||||
`resource_identity`; it never accepts executable commands, replacement tables,
|
||||
an estimated result, or a manifest claiming verification.
|
||||
|
||||
| Context | Original config selected | Native BattlePosition |
|
||||
| --- | --- | --- |
|
||||
| `ordinary_stage` | `stage_info[stage_id].level[difficulty].battle` | `battleType=stage`, string stage ID/level |
|
||||
| `task_battle` | `task_info[type_id].steps[step_index].battle`, status `battle` | `battleType=task`, task type and zero-based step |
|
||||
| `task_pass_stage` | stage/level from the original step's `statusValue`, status `passStage` | Same task position; no ordinary-stage result substitution |
|
||||
|
||||
With canonical orchestration requests, `battle_position.taskTypeId` identifies
|
||||
the original task definition; `task_id` may retain the account task-instance ID.
|
||||
Without `battle_position`, legacy CLI task requests use `task_id` for the original
|
||||
task type. Task step conflicts and wrong supplied positions refuse. The supplied
|
||||
battle must equal the independently decoded original config for that context.
|
||||
The engine-side `runtime_request` must retain `battle`, `team`, and
|
||||
`battle_position`; an identity-only request cannot reconstruct the selected team.
|
||||
|
||||
`inspect` returns `supported`, `offline_supported`, specific `reasons`, original
|
||||
resource identity, input coverage, native position, original battle duration, and
|
||||
derived watchdog. Support refers to offline execution of those supplied inputs,
|
||||
not to every stage or skill having an observed test. The complete original SWF
|
||||
contains the combat implementations; this adapter does not handport skill math.
|
||||
Unknown controllers, effects, formations, data shapes, and required missing images
|
||||
refuse. The native bridge additionally validates and constructs the snapshot.
|
||||
An unseen dynamic dependency can still fail execution and produce no outcome.
|
||||
|
||||
Validated snapshot execution reports original-code fidelity (`faithful=True`,
|
||||
`approximate=False`); diagnostic fixtures and invalid inputs do not qualify.
|
||||
`settlement_eligible=False` remains enforced at this frozen checkpoint pending
|
||||
final integration QA. `server_acceptance_verified=False` and the compatibility
|
||||
alias `server_validated=False` are independent of original-code fidelity.
|
||||
The implemented eligibility path requires original input/resource validation,
|
||||
natural completion, zero original check points, callback/roster/route binding,
|
||||
complete original statistics, and a valid asset audit. Strict synchronized trace
|
||||
parity and current server resource matching remain unverified. Online orchestration
|
||||
must gate before starting a battle.
|
||||
|
||||
Successful `run` results contain `status="completed"`, `battle_executed=True`,
|
||||
`battle_completed=True`, `outcome`, and `offline_result` with the actual original
|
||||
`battle_data`, `anomaly_records`, per-unit original records, timing, and terminal
|
||||
reason. Positive original `cheatNum` yields `status="anomaly"`, preserves the
|
||||
completed native evidence, and keeps eligibility false. Unsupported, cancelled,
|
||||
technical timeout, or failed jobs do not return an outcome or BattleData.
|
||||
Interrupted worker execution is `battle_executed=None` when progress is unknown;
|
||||
pre-start refusal/cancellation is `False`.
|
||||
|
||||
## Native execution and artifact identity
|
||||
|
||||
REA inspected the shipped original APK; retained AS3 was used for focused call
|
||||
inspection, not rebuilt as a replacement engine. The shipped identities are:
|
||||
|
||||
| Resource | Identity |
|
||||
| --- | --- |
|
||||
| APK 1.9.68 SHA-256 | `01678ee3a8465d818d32cbbd94baa0d8253b04b4c57b70ebc5544ed341f1015d` |
|
||||
| `assets/MYRMain.app` SHA-256 | `c6838331a198a22ffa486cbf61cc74c97619e011bc3364c8bb8dc99e269036cf` |
|
||||
| Main SWF header | Version 50, **50 FPS**, 640×960 RECT; FPS was decoded separately from the version byte |
|
||||
| Local SDK | Official AIR SDK 51.5.1.1, Windows x64; executable/JAR/SWC pins in `trusted.py` |
|
||||
|
||||
`swf_library.py` removes document-class binding ID 0 and makes DoABC blocks lazy.
|
||||
All 1,641 main ABC payloads remain byte-identical; 1,324 eager flags change.
|
||||
Executable/import tags are refused. Neither the original game document class nor
|
||||
the loader's login/update startup executes. Framework, main, UI, and movieclip
|
||||
library copies load into one child ApplicationDomain. No native extension, phone,
|
||||
rooting, protection bypass, rebuilt APK, or modified battle code is required.
|
||||
|
||||
`OriginalProbe.as` is a small compiled bootstrap. It injects original compressed
|
||||
AMF tables using native `ByteArray.readObject`, initializes the generic display
|
||||
framework, invokes `SnapshotBridge.build`, and starts the stock BattleCenter.
|
||||
Stock movement, AP, AI, skills, collisions, animation callbacks, timers, result
|
||||
statistics, and cheat checks execute. Only local win/loss observers are installed;
|
||||
the harness never forces a winner. Component probes are a separate action, so they
|
||||
do not consume random values or temporary unit IDs before a scene.
|
||||
|
||||
All original NetCenter service bases are replaced with a nonexistent local file
|
||||
URI before snapshot/scene construction. The image hook refuses URL/colon/path
|
||||
traversal inputs; sounds are disabled through original settings. Completion checks
|
||||
the original NetCenter request counter is zero. Python execution imports no game
|
||||
transport. This is deliberate transport isolation and neutralized startup,
|
||||
not a claim of an OS network sandbox around arbitrary AIR code.
|
||||
|
||||
The correct launcher is `adl64.exe -runtime ... -nodebug -profile
|
||||
extendedDesktop descriptor.xml -- ...`. The x86 launcher returned exit 4;
|
||||
misordered `-runtime` arguments were rejected. ADL uses the SDK runtime without a
|
||||
global installation. `-cmd` is unsuitable because its stage is null; the game uses
|
||||
display objects and frame callbacks. See [official ADL documentation](https://airsdk.dev/docs/building/air-debug-launcher).
|
||||
|
||||
## Assets, callbacks, and timing
|
||||
|
||||
Normal preparation builds a ZIP-entry index directly from the pinned APK:
|
||||
original hashed resource key, local-header data offset, compressed size, size,
|
||||
method, and CRC32. It verifies local/central metadata and entry bounds. Native
|
||||
FileStream reads the original packed bytes, decompresses ZIP deflate, verifies
|
||||
size/CRC, and passes those bytes to the original image decoder. Reading a new
|
||||
unit's assets does not require extracting the 1.4 GB resource tree. Existing
|
||||
earlier extracts remain ignored. Post-run audit compares every observed resource
|
||||
with the APK ZIP metadata. The native compression API is documented in the
|
||||
[official ByteArray reference](https://airsdk.dev/reference/actionscript/3.0/flash/utils/ByteArray.html).
|
||||
|
||||
An absent required image refuses. Empty optional frame declarations that are
|
||||
also absent from the original APK retain the original local IO-error callback;
|
||||
their paths remain in evidence. No replacement pixels or fabricated completion
|
||||
callbacks are supplied. The base slime's original `1001010_q_2s.png` absence is one
|
||||
such observed fallback. Native skill effects and additional spawned-unit assets
|
||||
are audited when read; an unapproved missing dependency stops the scene.
|
||||
|
||||
The stage runs hidden, 640×960, at the original 50 FPS. The harness records a
|
||||
separate ENTER_FRAME/100 ms Timer sample and full-scene frames/wall time, plus
|
||||
original frame-driver callback/delta observations. Initial short cold samples
|
||||
were about 42.7 FPS; full 1-1 scenes were about 49 FPS. New measurements include a
|
||||
300 ms warm-up and 2.5-second observation window. The subsequent three hidden
|
||||
samples measured 48.26–48.30 FPS and 22 Timer ticks over 2.505–2.527 seconds;
|
||||
the repeated task scene measured 47.45 FPS over 7.566 seconds. Requested FPS is
|
||||
never presented as measured FPS. Hidden-window execution is demonstrated on this workstation;
|
||||
timing under another host's background throttling remains an environment limit.
|
||||
|
||||
A critical bootstrap error was fixed: original EnterFrameDriver's constructor
|
||||
already calls `startup()`. Calling it again created a second ENTER_FRAME source,
|
||||
corrupted delta timing, and froze a skill pause. The harness now only registers
|
||||
its observer. Earlier 30-FPS and stalled 50-FPS evidence remains retained, and is
|
||||
not counted as correct original-timing validation.
|
||||
|
||||
The default technical watchdog is `2 × original battle seconds + 90` (690 s for
|
||||
the original 300-second normal limit). An explicit caller deadline is preserved,
|
||||
including source inspection and bootstrap. Cold APK hashing checks cancellation
|
||||
and the deadline between chunks; a 0.1-second cold deadline returned in 0.103 s
|
||||
without launching combat. Natural native clock completion is a completed native
|
||||
result with `terminal_reason="time_limit"`; winner still comes from original
|
||||
rules, including survival scenes that win on time. A technical watchdog supplies
|
||||
no BattleData and never changes the battle's original time limit.
|
||||
|
||||
## Observed completed native scenes
|
||||
|
||||
The following runs use unchanged original battle configs. Synthetic selected IDs
|
||||
exceed the NPC/player-check exemption threshold. Every row has retained original
|
||||
player check records; callback data is original `BattleData.getObj()`.
|
||||
|
||||
| Input and route | Outcome | Original clock used | Scene wall time / frames | Original checks |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Three level-1 adult green slimes, mean original growth, master level 1, ordinary `0101/1` | Win | 37.127 s | 41.112 s / 2,020 = 49.13 FPS | `cheatNum=0`, 3 player records |
|
||||
| Complete synthetic snapshot, original levels 1/2/3, ordinary `0101/1` | Win | 38.883 s | 44.299 s / 2,190 = 49.44 FPS | `cheatNum=0`, 3 player records |
|
||||
| Same snapshot, original task `2002014`, zero-based step 2 | Natural loss | 5.133 s of 60 s | 8.701 s / 405 = 46.55 FPS | `cheatNum=0`, 3 player records |
|
||||
| Same snapshot, task `1001004`, step 0 (`passStage` 0101/1) | Win | 30.943 s | 35.473 s / 1,750 = 49.33 FPS | `cheatNum=0`, 3 player records |
|
||||
|
||||
The first row read 12 distinct asset members with one genuine original optional
|
||||
absence and zero CRC/size mismatches. It retained 11 original unit records:
|
||||
player-side damage 784; enemy-side damage 371; five enemies dead. Native final
|
||||
AP was 13 and `aliveNum` was 5. These are actual engine outputs, not expected
|
||||
values filled by the harness. Randomness is native and unseeded, so subsequent
|
||||
valid fights need not reproduce those numbers.
|
||||
|
||||
Legacy `killNum`, `totalDamage`, `deadNum`, and `bossDamage` remained zero as in the
|
||||
retained original code path. `killMonster={}` in 1-1 follows the original mode-2
|
||||
enemy counting condition; its five enemies are juvenile mode 1. No counters are
|
||||
repaired. `anomaly_records` has four fields, not four anomalies: the count is
|
||||
`battle_data.cheatNum`, and even a zero count may retain `+0uneqmon` audit text.
|
||||
|
||||
Additional bounded experiments: an authored 30-second survival/spawn-controller
|
||||
scene completed in a natural loss before time expired, `cheatNum=0`. An invalid
|
||||
synthetic level-90/potential-1 roster triggered three original `+50overlv` records:
|
||||
`cheatNum=150`, adapter status `anomaly`, all records retained. That attempt is
|
||||
negative validation, not a successful timing or valid-roster proof.
|
||||
|
||||
## Snapshot bridge status and resolved bootstrap blockers
|
||||
|
||||
The independently owned `SnapshotBridge.as` compiles with the native harness.
|
||||
It uses original History/Monster/Bag/Team/global/addition builders and original
|
||||
AP getters, preserves input, and restores prior master on construction failure.
|
||||
The complete synthetic snapshots above passed the real bridge and full scenes.
|
||||
|
||||
The first authorized cached-snapshot attempt stopped before combat at:
|
||||
|
||||
```text
|
||||
phase: original_snapshot_bridge
|
||||
SnapshotBridge[missing_attributes] monsterAttributes:
|
||||
a complete attribute row is required for every selected monster instance
|
||||
```
|
||||
|
||||
Original MasterCenter allows a complete empty independent-addition list; the
|
||||
earlier bridge instead required every selected row. It also indexed
|
||||
`Table.skin_info.skins`, whereas original
|
||||
Table startup and this harness expose the flat `Table.skin_info` dictionary.
|
||||
The helper owner fixed both issues. No zero rows or nested table wrappers were
|
||||
fabricated. Cached-roster scenes now complete in all three contexts with zero
|
||||
original check points; their callback bodies pass the corrected binding validator.
|
||||
The original audit IDs may be strings while BattleData IDs are numbers; comparison
|
||||
normalizes identity only and retains original output types. A full skin/equipment
|
||||
scene and final Engine/native/fake-client integration remain pending at freeze.
|
||||
Private roster content,
|
||||
account identifiers, paths, statistics, and logs are omitted from this document.
|
||||
|
||||
## Process isolation and validation
|
||||
|
||||
Every worker has a fresh cwd/log directory, input/result nonce, captured compiler
|
||||
sources and their hashes, unique AIR application ID, and distinct native storage
|
||||
directory. Fixed Python → Java → ADL commands run without a shell. The Windows
|
||||
Job Object kills the worker and descendants on cancellation, deadline, or parent
|
||||
close. A process-tree test confirms the descendant is terminated. Imported runtime
|
||||
commands/paths/env/support manifests and unsigned verification claims are refused.
|
||||
SDK and prepared libraries use bundled reviewed hashes; native result verification
|
||||
also checks APK/main identity, input digest, nonce, route, outcome, anomaly count,
|
||||
actual execution/completion, and resource audit.
|
||||
|
||||
Two simultaneous native component probes passed with different native app IDs,
|
||||
storage directories, and nonces. The first concurrent trial exposed Windows
|
||||
`WinError 5` replacing a shared asset index during a read. Preparation now reuses
|
||||
identical immutable verified bytes and safely accepts a competing identical write;
|
||||
the repeated simultaneous trial passed. No cross-account invoke forwarding or
|
||||
shared application storage was observed.
|
||||
|
||||
Focused validation: **46 no-network unit tests pass**. They cover data/route/team
|
||||
contracts, unknown mechanics/assets, native result binding, anomaly preservation,
|
||||
time-limit result semantics versus watchdogs, default/explicit deadlines, arbitrary
|
||||
command rejection, SWF document neutralization/ABC preservation, ZIP offsets/CRC,
|
||||
resource preparation races, cancellation, and process-tree termination. Native
|
||||
execution is explicit opt-in and is not part of routine unit tests.
|
||||
The same 46 tests also passed with Python socket connection methods blocked.
|
||||
Combined runtime/orchestration validation passed **130 tests**. The latest
|
||||
explicit native task/concurrency validator exited 0, and no ADL worker remained
|
||||
after completion.
|
||||
|
||||
```powershell
|
||||
python -B -m unittest ranch_assistant.tests.test_battle_runtime -v
|
||||
python -B -m tools.battle_runtime.prepare
|
||||
python -B -m tools.battle_runtime.probe --compile-only
|
||||
python -B -m tools.battle_runtime.validate_native
|
||||
python -B -m tools.battle_runtime.validate_native --contexts task_battle --concurrent
|
||||
```
|
||||
|
||||
`validate_native --request <local JSON>` runs the public API against a data-only
|
||||
request, writes full evidence under ignored local_state, and prints aggregate
|
||||
results. `--rich` selects synthetic gear/skin inputs; their full-scene validation
|
||||
remains pending at freeze. The opt-in `acquire_air` tool downloads pinned
|
||||
51.5.1.1 dependencies into ignored local_state using official ZIP ranges; normal
|
||||
runtime/test execution never downloads anything or alters PATH/global config.
|
||||
|
||||
This owner changed only `battle_runtime.py`, its runtime tools/tests, and this
|
||||
document. Engine/UI/progression/AMF fixes belong to their respective owners.
|
||||
No commit, push, game request, battle submission, or reward action was performed.
|
||||
@@ -0,0 +1,280 @@
|
||||
# v1.2 experimental offline simulation
|
||||
|
||||
Implemented as a separate experimental Python model, parallel to original AIR
|
||||
runtime research. This is useful approximate combat, not an AIR engine replay.
|
||||
|
||||
## Public request/result contract
|
||||
|
||||
`ranch_assistant.battle_simulator.ExperimentalBattleRuntime` implements
|
||||
`inspect(request)` and `run(request, cancel_event=None, timeout=30.0)`.
|
||||
Both accept dicts or objects with the same attributes. Request fields are
|
||||
`context` (`ordinary_stage`, `task_battle`, `task_pass_stage`),
|
||||
`original_data` containing the original `battle` dictionary, `roster` containing
|
||||
the full raw snapshot (or `snapshot.raw`), `team` (original ordered team string),
|
||||
and `battle_position`. Optional `seed` defaults to zero. No game API is called.
|
||||
|
||||
Every response carries `execution_mode='experimental'`, `approximate=True`,
|
||||
`faithful=False`, `settlement_eligible=False`, `diagnostics`, and
|
||||
`ignored_mechanics`. `supported` means this approximate model can execute;
|
||||
it is never a claim of original engine fidelity or permission to settle.
|
||||
Unsupported objectives/controllers/triggers return `outcome='unsupported'`.
|
||||
An executed result includes natural `win`/`loss`, or technical `timeout`/`cancelled`,
|
||||
`units`, `events`, `elapsed_ms`, AP history, kill counters, and detected
|
||||
anomalies. Any `battle_data` will be explicitly model-derived evidence,
|
||||
never a fabricated victory or an authorization to submit.
|
||||
|
||||
### Worker contract
|
||||
|
||||
```python
|
||||
request = {
|
||||
"context": "ordinary_stage", # also task_battle / task_pass_stage
|
||||
"original_data": {"battle": original_battle_config},
|
||||
"roster": snapshot.raw, # full monsters/master/teams/monsterAttributes
|
||||
"team": "teamA", # team name, preserves its ordered monster slots
|
||||
"battle_position": original_battle_position,
|
||||
"seed": 0,
|
||||
}
|
||||
capability = ExperimentalBattleRuntime().inspect(request)
|
||||
result = ExperimentalBattleRuntime().run(request, cancel_event=event, timeout=30.0)
|
||||
# result:
|
||||
# execution_mode: 'experimental'; approximate: True; faithful: False
|
||||
# settlement_eligible: False (offline evidence only, explicit future review required)
|
||||
# requires_realtime_wait: True
|
||||
# supported: bool; outcome: win/loss/timeout/cancelled/unsupported/error
|
||||
# elapsed_ms: modeled game clock; elapsed_seconds: elapsed_ms / 1000
|
||||
# timeout_kind: wall_clock / resource_limit for technical timeouts
|
||||
# units: per-unit initial stats, hp, position, waiting/active/dead, summon origin
|
||||
# events: bounded deterministic trajectory; trace_truncated / omitted_events explicit
|
||||
# ap: team -> {initial, current, max, spent, recovered}; kills: all enemy deaths
|
||||
# kill_monster: source-selective non-player, non-object, mode==2 death map
|
||||
# anomalies: every anomaly detected, unfiltered; diagnostics; ignored_mechanics
|
||||
# battle_data: trajectory-derived source fields for completed win/loss only;
|
||||
# never treat these as authorized live settlement, never discard anomalies.
|
||||
# battle_data.battleMonIds: original ordered roster instance IDs from selected
|
||||
# team; includes waiting originals, excludes summons, empty for hideTeamMon
|
||||
# execution_status: completed / timed_out / cancelled / unsupported / error
|
||||
# terminal: True only for completed model win/loss
|
||||
# terminal_reason: elimination / battle_time_limit for completed models
|
||||
```
|
||||
|
||||
Natural expiry of `battle.time` is **completed loss**, with
|
||||
`terminal_reason='battle_time_limit'`, `battle_data.win=False`, `leftTime=0`,
|
||||
and the full configured modeled elapsed time. Technical worker timeout is
|
||||
`outcome='timeout'`, `execution_status='timed_out'`, `terminal=False`, and
|
||||
`battle_data=None`. Cancellation also has no battle data. This distinction
|
||||
separates incomplete execution from a completed natural loss.
|
||||
|
||||
`run` uses `Popen([sys.executable, '-m', 'ranch_assistant.battle_simulator',
|
||||
'--worker'], CREATE_NO_WINDOW on Windows)` with pipes and bounded output.
|
||||
CPU simulation does not run in the GUI process. The worker cannot use sockets;
|
||||
it reads only bundled combat artifacts and one JSON request on stdin. It has
|
||||
no imports of engine, GUI, battle_runtime, or battles. `simulate(request)` is
|
||||
the direct deterministic entrypoint for offline tests. Results return as soon
|
||||
as computation ends, without sleeping for the modeled battle duration.
|
||||
Orchestration owns any cancellable wait before a future reviewed live route.
|
||||
|
||||
### Explicit experimental eligibility (latest integration contract)
|
||||
|
||||
`settlement_eligible=False` and `faithful=False` always refer to original
|
||||
engine fidelity. After an actual supported model completes (including a
|
||||
natural loss), `experimental_settlement_eligible=True` only when `battle_data`
|
||||
was computed and there are no unresolved inputs or detected anomalies.
|
||||
Otherwise `experimental_eligibility_reasons` gives the reason and the flag is
|
||||
false. Inspection and technical timeout/cancel/error never assert experimental
|
||||
eligibility. Known approximate mechanics remain disclosed even when eligible;
|
||||
this does **not** claim that original cheat checks ran or were complete.
|
||||
|
||||
Integration must use the experimental flag only under the explicitly selected
|
||||
`policy.battle_mode='experimental'`, never the native route. Production
|
||||
integration and the real-time wait remain owned by orchestration; this module
|
||||
does not start or settle any live battle.
|
||||
|
||||
## Original inputs and reproducible static data
|
||||
|
||||
The builder uses `tools.research_battle_v12.recover_table` with the repaired
|
||||
AMF Reader (empty arrays remain `[]`). It rejects any APK whose SHA-256 is not
|
||||
`01678ee3a8465d818d32cbbd94baa0d8253b04b4c57b70ebc5544ed341f1015d`.
|
||||
The retained main SWF SHA-256 is
|
||||
`c6838331a198a22ffa486cbf61cc74c97619e011bc3364c8bb8dc99e269036cf`.
|
||||
The SWF header independently decodes to **50.0 fps**; the fixed model clock
|
||||
therefore advances 20 ms per tick.
|
||||
|
||||
```powershell
|
||||
python tools/build_battle_simulation_data.py
|
||||
python tools/build_battle_simulation_data.py --output local_state/battle_simulator/rebuild
|
||||
```
|
||||
|
||||
Both builds were run; the two gzip artifacts and manifest matched byte for
|
||||
byte. Gzip has a fixed zero timestamp, JSON is sorted and compact, and the
|
||||
manifest retains per-table original compressed-member digests, logical names,
|
||||
decoded sizes, APK identity, and 196 attack profiles' retained AS3 source hashes.
|
||||
No personal path or account data enters these artifacts.
|
||||
|
||||
| Artifact | Bytes | Contents |
|
||||
| --- | ---: | --- |
|
||||
| `combat_tables.json.gz` | 242,430 | 749 species, 266 skill definitions, original numeric/settings/team/potential/entangle/upstar/item tables, default fields, 196 attack profiles |
|
||||
| `combat_battles.json.gz` | 1,465,404 | All 1,178 original stage records' level configs and 1,165 tasks' combat/status steps |
|
||||
| `combat_manifest.json` | manifest | Original source and artifact digests and retained-source fingerprints |
|
||||
|
||||
The runtime validates identity and compressed/decoded artifact hashes, then
|
||||
freezes dictionaries and arrays recursively. The independent cache does not
|
||||
use Catalog. Normal workers never decode the roughly 62 MB full battle corpus;
|
||||
they receive one original battle config and read the small combat bundle.
|
||||
`combat_battles()` is a lazy public-static research helper. Neither runtime
|
||||
method imports the builder, opens the APK, or contacts the network.
|
||||
|
||||
## Implemented trajectory
|
||||
|
||||
Player HP/ATK/DEF/DEX follow `MonsterVo`:
|
||||
|
||||
```text
|
||||
int((base + actualGrowth * (level + min(tpLevel, 4) - 1)
|
||||
+ monsterAttributes[stat] + pStat + master.globalStat)
|
||||
* (1 + clamp(feel, 0, 200) / 2000 + game_setting.upStarAdd * upStar))
|
||||
```
|
||||
|
||||
Growth comes from the raw monster, never a generic Fighter or midpoint player.
|
||||
Potential uses actual `pAtk/pDef/pHp/pDex`. Server `monsterAttributes` supplies
|
||||
the aggregate bonuses once; equipment is not added again. Attack interval is
|
||||
the species interval plus source integer dex adjustment and `atkSpd`; movement
|
||||
uses species speed plus the source two-decimal dex adjustment. Crit and AP cost
|
||||
saving come from the same server attributes. Upstar skill replacements and
|
||||
breakthrough-derived skill levels use the original tables. Missing growth or a
|
||||
nonpositive computed attack interval is rejected, not replaced or clamped.
|
||||
|
||||
Configured enemies retain their individual authored values. `autoValue` uses
|
||||
the source species midpoint construction, level and global additions. Only
|
||||
authored `scaleAbility`/`scaleHp` fields change configured enemy numbers; they
|
||||
are not user-selectable damage cheats. Normal stage/task combat does not apply
|
||||
the unrelated PvP `pveHpScale` or `pveApStartScale`.
|
||||
|
||||
Teams preserve the selected snapshot team order and original position mapping
|
||||
`1,4,2,5,6,7,8`. Player field capacity follows unlocked `team_info.battleTeam`
|
||||
slots, capped at four. Enemy capacity comes from original `numMax`. Deployment
|
||||
uses original spawn rectangles, `joinTime` in seconds, and per-team waves.
|
||||
Wave unlock waits 700 ms; scheduled reinforcements are admitted on the source
|
||||
one-second deployment cadence. `hideTeamMon` removes roster combatants and
|
||||
allows authored allies. Summons do not consume field capacity.
|
||||
|
||||
Player AP starts at `startAp + (master.level-1)*addApByLevel`. Enemy AP starts
|
||||
at authored `ap` with max `2*ap`. The clock recovers one AP per original
|
||||
`apCD=2000` ms; delayed roster joins restore the original fraction of max AP.
|
||||
Automatic deployment has **no invented AP charge**: source
|
||||
`prepareTimeMonster` checks time/wave/capacity, not cost. AP is spent on actual
|
||||
skill casts. Position-command AP spending is outside this automatic model.
|
||||
|
||||
The model selects spatial targets, moves toward them, tests the source attack
|
||||
box (`abs(dx)<range`, `abs(dy)<range*0.5`), schedules original attack action
|
||||
hit delays, and adds projectile travel using recovered projectile speed and
|
||||
`(distance-30)/speed*(1000/50)`. Target death and skill-5 projectile loss cause
|
||||
real misses. Damage uses original critical chance, critical and elemental
|
||||
factors, integer stages, dex-dependent random range, defense and reduction.
|
||||
HP loss, healing, poison, stun, reflection and lifesteal change the trajectory.
|
||||
The model waits the source one-second delayed game-over check after deaths.
|
||||
|
||||
| Skill | Source mechanics implemented | Remaining approximation |
|
||||
| --- | --- | --- |
|
||||
| 3 `Skill3Copy` | One summon; original level ability factor; scaled ATK/DEF/DEX; HP from current parent HP; no inherited skills or capacity cost | Physical split impulse, visual/equipment callbacks and exact clone motion |
|
||||
| 5 `Skill5FlashMove` | Source distance AI and AP/CD; movement displacement using original speed; loses incoming model projectiles | Impulse is one displacement; inertia and temporary knockback resistance are omitted |
|
||||
| 7 `Skill7Copy3` | Exactly three summons; original factor; scaled max HP; child AP-cost metadata 1; no capacity cost | Physical spreading impulses and clone animation |
|
||||
| 9 `Skill9AreaHit` | Next attack is ready; original attack factor damages nearby enemies in source +/-150 by +/-91 box; primary hit preserved | Knockback, visual shake and exact projectile-versus-activation timestamp edge cases |
|
||||
| 38 `Skill38Miohit` | Four hits; original random attack factor; attack type 28/100 ms windup, 150 ms recovery, 50 ms quick-CD scheduling | Rush motion, final knockback, temporary resistance and skin-specific motions |
|
||||
|
||||
Known skills use the original random AI probabilities. Player auto-skill checks
|
||||
use the source 30-frame cadence, enemy AI 20/60/100 frames by mode, and at most
|
||||
one cast per model tick. Missing framework `Cooldowner` initialization and
|
||||
callback timing are approximated; the model assumes initial attacks are ready.
|
||||
Enemy initial skill readiness is approximated at two seconds.
|
||||
|
||||
`atkStun`, `defStun`, five-second poison with one-second ticks, thorns,
|
||||
`atkVim`, and five-second `selfCure` have trajectory effects. `sunFire`,
|
||||
`moonHeal`, and `deadBoom` are not implemented and are explicitly reported when
|
||||
present. All other skill IDs are individually listed as omitted by inspection;
|
||||
the five implemented skill families are partial, not full-fidelity ports.
|
||||
|
||||
## Counters, evidence and anomaly retention
|
||||
|
||||
| Output | Exact model meaning |
|
||||
| --- | --- |
|
||||
| `kills` / `all_kills` | All modeled non-player, non-object deaths, regardless of adult/juvenile mode; includes summons |
|
||||
| `kill_monster` / `battle_data.killMonster` | Source `deadHandler` selection only: non-player, non-object, **mode 2** deaths; includes adult summons |
|
||||
| `alive_num` / `battle_data.aliveNum` | Active plus waiting non-object player units, including summons; not just deployed original survivors |
|
||||
| `battle_data.battleMonIds` | Selected team order of original roster **instance IDs**, including waiting originals; excludes clones/summons and species IDs; empty when the source hides the roster |
|
||||
| `damage_hp_lost`, unit `damage_dealt` | Measured HP actually removed by this model |
|
||||
| `battle_data.totalDamage`, `killNum`, `deadNum` | Source-declared integer defaults **0**; no assignments found in retained combat source; never filled from invented counters |
|
||||
| `bossDamage` | Source marker `bossPoint=-1` credits actual HP loss; positive markers credit actual deaths |
|
||||
|
||||
`battle_data` exists for completed model win/loss only. It also carries actual
|
||||
model AP, left time and filtered original BattlePosition fields. It is local
|
||||
evidence; no callback or game route is invoked here. Unknown/cancelled/timed-out
|
||||
execution has no battle data. Internal model errors retain partial traces and
|
||||
every anomaly already recorded, while keeping eligibility false.
|
||||
|
||||
Original observed thresholds are not softened: damage over 80,000 records
|
||||
`+10overdamage`/10 points; player requested healing over 20,000 records the
|
||||
source's `+15overcure`/**19** points even if effective healing is small.
|
||||
The observable snapshot subset of `BattlePanel.cheatCheck` records excess
|
||||
affection, growth-derived totals, potential and level with original scores and
|
||||
the original temporary/NPC-id exemption. Original full character equivalence,
|
||||
runtime memory/table comparison and all skill-specific checks are **not fully
|
||||
replayed**. Artifact integrity checks and these partial checks are not a claim
|
||||
of a clean original engine execution.
|
||||
|
||||
Anomalies are retained separately from the bounded event trace and copied
|
||||
unchanged into model evidence; they prevent experimental eligibility. Event
|
||||
truncation reports `trace_truncated` and `omitted_events`. Default trace limit
|
||||
is 2,000 events, maximum 10,000. Input/output are bounded to 16 MiB; 1,024 total
|
||||
created units, 10,000 detected anomalies or 180,000 logical ticks stop work as
|
||||
a technical resource limit. Recorded anomalies are never removed to manufacture
|
||||
an acceptable result. This code does not normalize cheat scores or clear records.
|
||||
|
||||
## Completeness and offline validation
|
||||
|
||||
Inspection of the entire original corpus with a synthetic four-unit roster:
|
||||
|
||||
| Original configurations | Inspected | Admitted by this approximate model |
|
||||
| --- | ---: | ---: |
|
||||
| Stage level battle configs | 2,512 | 941 |
|
||||
| Inline task battle configs | 199 | 106 |
|
||||
|
||||
Admission is structural model support, not a fidelity or gameplay-success rate.
|
||||
Non-elimination objectives, authored battle/monster controllers, triggers,
|
||||
protected/destroyed units, and active field areas are rejected with reasons.
|
||||
Twelve admitted original stage configs were also executed with a synthetic
|
||||
level-20 roster using species 1001010, 1030010, 2004010, 3010010; all twelve
|
||||
completed model wins. They were not account replays and were not calibrated
|
||||
against recorded AIR fights.
|
||||
|
||||
Remaining limitations include straight-line movement, no collision/inertia or
|
||||
flight height, simplified retargeting/retreat, visual object collision omitted,
|
||||
projectile paths/easing/offsets omitted, skill presentation replaced with model
|
||||
activation, no full physics/knockback, omitted equipment special words and skin
|
||||
attack overrides, and Python RNG rather than original Math.random/Random.
|
||||
These limitations accompany every inspection/result even when the model admits
|
||||
the battle. No percentage of original engine fidelity is claimed.
|
||||
|
||||
```powershell
|
||||
python -m unittest ranch_assistant.tests.test_battle_simulator -v
|
||||
```
|
||||
|
||||
**38 simulator tests passed**, and **59 tests passed** when combined with the
|
||||
estimator and AMF suites: immutable original artifacts and constants; all three
|
||||
contexts; snapshot growth/tp/potential/global/feel/upstar/attributes; normal wins,
|
||||
natural elimination losses and completed clock-expiry losses; order, capacity,
|
||||
waves and join delays; each of skills 3/5/7/9/38; projectiles, statuses/healing;
|
||||
waiting/summon alive counts and selective kills; source default counters; hidden
|
||||
teams and boss markers; anomaly retention through truncation and model failure;
|
||||
explicit unsupported mechanics; identical seeded direct/worker trajectories;
|
||||
object/dict requests; all three original route fields and ordered instance-ID
|
||||
lists (including waiting/excluding summons); fixed Windows worker command and no GUI imports;
|
||||
socket audit rejection; child cancellation, wall timeout and interrupt cleanup.
|
||||
|
||||
A sample worker completed in approximately 0.16 wall seconds with 2.7 modeled
|
||||
seconds. This is an observation, not a performance guarantee. There is no
|
||||
offline real-time sleep; `requires_realtime_wait=True` delegates the cancellable
|
||||
elapsed-clock wait to orchestration before any separately reviewed live route.
|
||||
|
||||
Only public original configs and synthetic fixtures were used. No actual
|
||||
account input, log, personal identifier, credential, real game request,
|
||||
production integration, commit or push was made by this workstream. The
|
||||
experimental module is independent of the native original-engine runtime.
|
||||
@@ -63,7 +63,6 @@ import com.diyidan.game.util.Utils;
|
||||
import com.diyidan.game.widget.DydToast;
|
||||
import com.diyidan.game.widget.FloatView;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class DydGameApi {
|
||||
public static final String LOGIN_TYPE_QQ = "QQ";
|
||||
public static final String LOGIN_TYPE_WEIBO = "WEIBO";
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
package com.diyidan.game.common;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class Constants {
|
||||
public static final String ACTION_RECEIVER_FINISH_PAYMENT_PAGE = "action.dydgame.close.payment.page";
|
||||
public static final String ACTION_RECEIVER_PAYMENT_CALLBACK = "action.dydgame.payment.callback";
|
||||
|
||||
@@ -17,7 +17,6 @@ import com.diyidan.game.util.PrivacyUtils;
|
||||
import com.diyidan.game.util.Utils;
|
||||
import com.diyidan.game.widget.DydToast;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class LoginDialog extends Dialog implements View.OnClickListener {
|
||||
private BaseDialog dialog;
|
||||
private CheckBox mCbPrivacy;
|
||||
|
||||
@@ -3,7 +3,6 @@ package com.diyidan.game.entity.impl;
|
||||
import com.diyidan.game.entity.DydPlayer;
|
||||
import java.io.Serializable;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class DydPlayerModel implements DydPlayer, Serializable {
|
||||
private static final int USER_TYPE_ADMIN = 200;
|
||||
private static final int USER_TYPE_MOBILE_PASS = 111;
|
||||
|
||||
@@ -10,7 +10,6 @@ import com.diyidan.game.util.Utils;
|
||||
import java.util.Map;
|
||||
import java.util.concurrent.TimeUnit;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class BaseNetwork2<T> {
|
||||
protected INetworkHandler callbackHandler;
|
||||
protected Context mContext;
|
||||
|
||||
@@ -5,7 +5,6 @@ import com.diyidan.game.network.model.JsonData;
|
||||
import com.diyidan.game.util.JsonUtils;
|
||||
import org.apache.http.HttpStatus;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class SuccessListener implements Response.Listener<String> {
|
||||
private INetworkHandler callbackHandler;
|
||||
private Class clazz;
|
||||
|
||||
@@ -6,7 +6,6 @@ import com.diyidan.game.network.model.ListJsonDataModel;
|
||||
import com.diyidan.game.util.Utils;
|
||||
import java.util.HashMap;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class UserNetwork2 extends BaseNetwork2<ListJsonDataModel> {
|
||||
public UserNetwork2(Context context, INetworkHandler iNetworkHandler, int i) {
|
||||
super(context, iNetworkHandler, i);
|
||||
|
||||
@@ -2,7 +2,6 @@ package com.diyidan.game.network.model;
|
||||
|
||||
import java.io.Serializable;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class JsonData<T> implements Serializable {
|
||||
private static final long serialVersionUID = 1183879419184262397L;
|
||||
private String apiVersion;
|
||||
|
||||
@@ -4,7 +4,6 @@ import com.diyidan.game.entity.impl.DydPlayerModel;
|
||||
import com.diyidan.game.util.Utils;
|
||||
import java.util.List;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class ListJsonDataModel extends BaseModel {
|
||||
private static final long serialVersionUID = 4037399126099105967L;
|
||||
private List<FriendModel> friendList;
|
||||
|
||||
@@ -6,7 +6,6 @@ import javax.crypto.SecretKeyFactory;
|
||||
import javax.crypto.spec.DESedeKeySpec;
|
||||
import javax.crypto.spec.IvParameterSpec;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class AESTools {
|
||||
private static final String encoding = "utf-8";
|
||||
private static final String iv = "01234567";
|
||||
|
||||
@@ -8,7 +8,6 @@ import java.util.ArrayList;
|
||||
import java.util.Arrays;
|
||||
import java.util.List;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class DydOkHttpNetwork implements Dns {
|
||||
@Override // com.squareup.okhttp.Dns
|
||||
public List<InetAddress> lookup(String str) throws UnknownHostException {
|
||||
|
||||
@@ -17,7 +17,6 @@ import javax.crypto.spec.SecretKeySpec;
|
||||
import org.apache.http.auth.AUTH;
|
||||
import org.apache.http.cookie.SM;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class DydStringRequest extends StringRequest {
|
||||
private static long APP_ID;
|
||||
private static String AUTH_RESULT;
|
||||
|
||||
@@ -9,7 +9,6 @@ import java.lang.reflect.Type;
|
||||
import java.util.List;
|
||||
import java.util.Map;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class JsonUtils {
|
||||
public static <T> JsonData<T> parseNetworkResponse(String str, TypeReference<JsonData<T>> typeReference) {
|
||||
return (JsonData) JSON.parseObject(str, typeReference, new Feature[0]);
|
||||
|
||||
@@ -39,7 +39,6 @@ import java.util.zip.ZipEntry;
|
||||
import java.util.zip.ZipFile;
|
||||
import org.zengrong.ane.funs.pref.PreferenceType;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class Utils {
|
||||
private static final String[] strSplits = "1234567890qwertyuiopasdfghjklzxcvbnmQWERTYUIOPASDFGHJKLZXCVBNM".split("");
|
||||
private static final Random random = new Random();
|
||||
|
||||
@@ -14,7 +14,6 @@ import net.pixvi.ane.dydsdk.DydSdkContext;
|
||||
import net.pixvi.ane.dydsdk.DydSdkEvent;
|
||||
import net.pixvi.ane.dydsdk.DydSdkEventStatus;
|
||||
|
||||
/* JADX INFO: loaded from: C:\Users\11789\Documents\Projects\Codex_ws\myrzx_fang\analysis\base_classes.dex */
|
||||
public class LoginFunction implements FREFunction {
|
||||
private DydGameApi.ExitCallback mFloatViewExitCallback;
|
||||
private OnAccountUpgradeListener mFloatViewUpgradeListener;
|
||||
|
||||
Reference in New Issue
Block a user