11F Playtester Report

Tower of Trample: The Queen — AI Playtester Bot
最近一次測試：2026-04-26 14:41 — 14:51Last session: 2026-04-26 14:41 — 14:51

📂 資料來源：1 個檔案（0 個回合 + 主 log）Sources: 1 files (0 rounds + main log) 📝 解析 115 行115 lines parsed 🕐 資料更新：2026-04-26 14:51Data updated: 2026-04-26 14:51
TL;DR — 當機 3 次，集中在 11F 大廳（1 次）。對話超時主因：Rhea（2/2 次）。1 個事件不可到達。地圖覆蓋 13%。3 crashes, concentrated in 11F Hall (1x). Dialogue timeout hotspot: Rhea (2/2x). 1 events unreachable. 13% map coverage.
首要阻斷Top blockers: 🔴 Rhea (當機 3×crash 3×) · 🟠 Portal (不可達 1×unreach 1×)

偵錯清單Triage Checklist

從這裡開始 — 每項包含問題描述、嫌疑目標、修復建議與檢查指令。Start here — each item includes issue, suspect, fix, and inspect command.

4 重要high — 4 項目items
  1. 🟡 重要HIGH 啟動失敗 — 1 次（遊戲未進入地圖就關閉）Boot failure — 1× (game closed before reaching map)
    啟動失敗不會出現在地圖上，不屬於任何 NPC/事件問題Boot failures never reach a map — not caused by any NPC or event
    ⚡ 修復可消除 ~1 次當機（佔 33%）Fixing could eliminate ~1 crashes (33%)
    修復Fix: 檢查啟動流程：Title Scene、預載腳本、Plugin 初始化順序Check startup sequence: Title Scene, preload scripts, Plugin init order
  2. 🟡 重要HIGH 畫面凍結 — 2 次當機Screen freeze — 2 crashes
    "stale" = 畫面凍結 → 可能是無限迴圈或死鎖的平行事件"stale" = screen frozen → likely infinite loop or deadlocked parallel event
    ⚡ 修復可消除 ~2 次當機（佔 66%）Fixing could eliminate ~2 crashes (66%)
    重現路徑Repro Steps:
    1. Map 0→311
    2. 對話Talk to Rhea (Map311)
    3. 對話Talk to Rhea (Map311)
    4. 💥 當機Crash @ 11F 大廳11F Hall(22,24)
    快速定位Quick start: ruby _Tools/set_start_pos.rb 311 22 24
    修復Fix: 檢查 Rhea 的自動執行/平行處理，確認有退出條件Check Rhea Autorun/Parallel — ensure exit condition exists
    地圖Map: 11F 大廳11F Hall · 嫌疑Suspect: Rhea (EV003) · ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3 · → 當機模式→ Crash Pattern #1, #2
  3. 🟡 重要HIGH 1 個事件不可到達1 events unreachable
    主要地圖Top maps: 11F 大廳11F Hall(1)
    原因分佈Reason breakdown: 路徑失敗no path 1
    事件Event次數Hits原因Reason地圖Map檢查Inspect
    Portal EV0021路徑失敗no path11F 大廳11F Hallruby _Tools/map_inspector.rb Data/Map311.rvdata2 2
    修復Fix: 大量事件 BFS 搜尋失敗 — 檢查地圖碰撞設定是否將可走區域切斷Mass BFS failures — check map collision/passability cutting off walkable areas
    地圖Map: 11F 大廳11F Hall · → 詳見→ see 卡點分析Stuck Analysis
  4. 🔵 重要HIGH 地圖探索率 13%（2/15）— 13 個地圖未到達Map coverage 13% (2/15) — 13 maps not reached
    🔧 需檢查（7）：Queen 房間、Vera 房間、Brenna 房間、Lysandra 房間、Sherrilyn 房間、Faye 房間、東翼走廊 — 確認大廳→房間的 Transfer Event 存在且觸發條件（開關/變數）已滿足🔧 Fix needed (7): Queen's Room, Vera's Room, Brenna's Room, Lysandra's Room, Sherrilyn's Room, Faye's Room, East Wing Corridor — verify hall→room Transfer Events exist and trigger conditions (switches/variables) are met
    🔒 劇情鎖定（6）：好結局房間、壞結局房間、策略房間、監獄、道場、臣服結局🔒 Story-gated (6): Good Ending Room, Bad Ending Room, Strategy Room, Prison, Dojo, Submission End
    地圖Map狀態Status檢查入口/傳送Inspect entrances
    🔧 Queen 房間Queen's Room應可到達Should be reachableruby _Tools/map_inspector.rb Data/Map312.rvdata2
    🔧 Vera 房間Vera's Room應可到達Should be reachableruby _Tools/map_inspector.rb Data/Map313.rvdata2
    🔧 Brenna 房間Brenna's Room應可到達Should be reachableruby _Tools/map_inspector.rb Data/Map315.rvdata2
    🔧 Lysandra 房間Lysandra's Room應可到達Should be reachableruby _Tools/map_inspector.rb Data/Map316.rvdata2
    🔧 Sherrilyn 房間Sherrilyn's Room應可到達Should be reachableruby _Tools/map_inspector.rb Data/Map320.rvdata2
    🔧 Faye 房間Faye's Room應可到達Should be reachableruby _Tools/map_inspector.rb Data/Map332.rvdata2
    🔧 東翼走廊East Wing Corridor應可到達Should be reachableruby _Tools/map_inspector.rb Data/Map337.rvdata2
    🔒 好結局房間Good Ending Room需劇情推進Story-gatedruby _Tools/map_inspector.rb Data/Map324.rvdata2
    🔒 壞結局房間Bad Ending Room需劇情推進Story-gatedruby _Tools/map_inspector.rb Data/Map325.rvdata2
    🔒 策略房間Strategy Room需劇情推進Story-gatedruby _Tools/map_inspector.rb Data/Map333.rvdata2
    🔒 監獄Prison需劇情推進Story-gatedruby _Tools/map_inspector.rb Data/Map336.rvdata2
    🔒 道場Dojo需劇情推進Story-gatedruby _Tools/map_inspector.rb Data/Map257.rvdata2
    🔒 臣服結局Submission End需劇情推進Story-gatedruby _Tools/map_inspector.rb Data/Map323.rvdata2
    → 詳見 地圖旅程→ see Map Journey
NPC 問題總覽NPC Fault Summary (點擊展開click to expand)

跨區域匯總每個 NPC/事件的所有問題類型，並提供修復建議。按嚴重度排序。Cross-references each NPC/event across all issue types with fix suggestions. Sorted by severity. (2 個已在偵錯清單中2 already in Triage)

NPC / 事件NPC / Event 所有問題類型及各計數All issue types with counts">類型Issues 當機Crash 超時Timeout 不可達Unreach 成功率Success 主要地圖Top Map 建議修復Suggested Fix 檢查Inspect
HIGH Rhea ↑清單↑triage 💥3 ⏱2 3 2 — 29% 11F 大廳11F Hall → 偵錯清單 #2 → 模式→ pattern #1→ Triage #2 → 模式→ pattern #1 ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3
LOW Portal ↑清單↑triage 🚫1 — — 1 0% 11F 大廳11F Hall → 偵錯清單 #3 → 模式→ pattern #1→ Triage #3 → 模式→ pattern #1 ruby _Tools/map_inspector.rb Data/Map311.rvdata2 2

摘要Summary

當機Crash -40 · 啟動失敗Boot fail -10 · 超時Timeout -0 · 不可達Unreachable -1 · 覆蓋率Coverage -17" style="grid-row:span 2">
D
問題多 (32/100)Poor (32/100)
100 - 68 = 32 ⓘ
凍結率Freeze rate
-40/40
啟動失敗Boot fail
-10/10
不可達事件Unreachable
-1/20
覆蓋率缺口Coverage gap
-17/20
 已知 11F 地圖數量Known 11F maps in test scope">
13%
地圖覆蓋率 (2/15 已知地圖)Map Coverage (2/15 known)
Rhea
最大阻擋 NPC (2次超時)Top Blocker (2 timeouts)
2
互動事件Interactions
0
戰鬥場次Battles
57
畫面凍結 （累計）Screen Freezes (all-time) → #1
14
啟動失敗 （累計）Boot Failures (all-time) → #3
12
其他異常 （累計）Other Anomalies (all-time)
17.9/h
本次穩定度This Run （累計共 83 次）(83 all-time)
15m
累計遊玩時間Total Play Time
3
最近一次重啟Latest Restarts
當機時間分佈（每 30 分鐘）Crash Timeline (30-min buckets)
2 14:30

已到達：11F 大廳, 10F 階梯Visited: 11F Hall, 10F Stairway

觀察與建議Observations (點擊收合click to collapse)

🟡 重要問題🟡 Major Issues (1)

地圖探索率：2/15（13%）Map coverage: 2/15 (13%)

已到達：11F 大廳, 10F 階梯
❌ 未到達：Queen 房間, Vera 房間, Brenna 房間, Lysandra 房間, Sherrilyn 房間, 好結局房間, 壞結局房間, Faye 房間, 策略房間, 監獄, 東翼走廊, 道場, 臣服結局Visited: 11F Hall, 10F Stairway
❌ Not reached: Queen's Room, Vera's Room, Brenna's Room, Lysandra's Room, Sherrilyn's Room, Good Ending Room, Bad Ending Room, Faye's Room, Strategy Room, Prison, East Wing Corridor, Dojo, Submission End

🔵 資訊🔵 Info (1)

事件不可到達（1 個獨立事件，1 次嘗試）Unreachable events (1 unique, 1 attempts)

集中在 11F 大廳（佔 100%）。可能是該地圖整體碰撞/通行設定問題，而非個別事件 bug。 檢查：ruby _Tools/map_inspector.rb Data/Map311.rvdata2Concentrated on 11F Hall (100%). Likely a map-wide collision/passability issue, not individual event bugs. Inspect: ruby _Tools/map_inspector.rb Data/Map311.rvdata2

卡點分析Stuck Analysis

無法到達的事件Unreachable Events 1

↑ 偵錯清單有快速摘要Triage checklist has a quick summary

Bot 嘗試走向這些事件但連續卡住 3 次以上。🔧 = 可能是碰撞/通行 Bug（需修復），🔒 = 預期行為（守衛/寶箱/劇情鎖定）。卡住率 = 不可到達 ÷ (不可到達 + 成功互動)。Bot tried to walk toward these events but got stuck 3+ times. 🔧 = likely collision/passability bug (fix needed), 🔒 = expected (guard/chest/story-gated). Stuck rate = unreachable ÷ (unreachable + interactions).

失敗模式指南Failure Mode Guide (怎麼看、怎麼修what it means & how to fix)
模式Mode×含義Meaning編輯器修復步驟Editor Fix Steps
🗺️ BFS bfs_fail1路徑搜尋失敗 — 事件和 Bot 之間沒有可通行的路徑No walkable path — the event is completely walled off from the bot在編輯器中選擇地圖 → 檢查事件周圍的圖塊通行設定（Layer 堆疊、☆ vs ×）；或確認事件是否在不可到達的區域In editor: select map → check tile passability around the event (layer stacking, ☆ vs ×); or confirm event is in an inaccessible zone
每地圖明細（1 張地圖）Per-map detail (1 maps)
地圖Map事件數Events總嘗試Attempts不可到達嘗試 ÷ (不可到達+成功互動)Unreachable ÷ (unreachable + interactions)">卡住率Stuck%類型Type事件詳情Event Details
11F 大廳11F Hall 1 1x 33% 🔧 需修復Fix 🔧 id=2 Portal (22,22) ×1 — 路徑搜尋失敗：BFS 找不到路線 (BFS failed 2x, teleport failed)No path found: BFS failed (BFS failed 2x, teleport failed)
ruby _Tools/map_inspector.rb Data/Map311.rvdata2 2

對話超時Dialogue Timeout 2

Bot 按確認鍵但對話框不消失，共 2 次。可能是等待選項輸入、或有 Autorun 事件持續觸發。Bot pressed confirm but dialogue did not close, 2 times. May be waiting for choice input or autorun events.

按 NPC（前 8）By NPC (Top 8)

NPCNPC位置Location超時Timeouts該NPC對話出現在幾次不同當機的前置動作中Unique crashes where this NPC dialogue preceded the crash">前置當機Crash Precursors嚴重度Severity檢查Inspect
Rheaid=3 11F 大廳11F Hall23—ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3

按地圖（前 8）By Map (Top 8)

地圖Map超時Timeouts檢查Inspect
11F 大廳11F Hall2ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3

當機模式分析Crash Pattern Analysis

總共 3 次當機，歸納為 3 個根因模式：3 total crashes, grouped into 3 root cause patterns:

按原因By Reason

原因Reason次數Count說明Description
stale2遊戲畫面凍結（幀數不再增加）Screen frozen (frame count stopped)
no_state1無法讀取遊戲狀態Could not read game state

按位置（前 5）By Location (Top 5)

位置Location次數Count
🔌 啟動失敗（未進入地圖）Boot failure (never reached map)1
11F 大廳11F Hall (22,24)1
10F 階梯10F Stairway (14,22)1

根因分析 — 相同觸發模式合併Root Cause Analysis — Grouped by Trigger Pattern

相同前置動作 + 相同原因的當機合併為一組，點擊展開查看所有實例Crashes with identical preceding actions + reason are merged. Click to expand instances.

🎯 修復 1 個根因可解決多組模式🎯 Fixing 1 root causes resolves multiple patterns
嫌疑 NPCSuspect NPC類型Type總當機Crashes模式數Patterns關聯模式Related
Rheastale22#1, #2
快速索引 (3 模式)Quick Index (3 patterns)
#次數Cnt原因Reason嫌疑 NPCSuspect地圖Map修復至此模式可解決的累計百分比Cumulative % resolved by fixing up to this pattern">累計Cumul.
⚪ #11🧊 staleRhea11F 大廳11F Hall
1/3 (33%)
⚪ #21🧊 staleRhea10F 階梯10F Stairway
2/3 (67%)
⚪ #31🔌 no_stateRheaMap0
3/3 (100%)
🧊 畫面凍結Screen Freezes — 2 次當機crashes, 2 模式patterns
無限迴圈或事件死鎖。檢查：Parallel Process / Autorun 的退出條件、Move Route 是否完成、條件分歧是否遺漏Infinite loops or event deadlocks. Check: Parallel/Autorun exit conditions, Move Route completion, missing conditional branches
低頻（2 個，各 ≤2 次）Low-freq (2, each ≤2)
1× stale — 11F 大廳11F Hall ×1
觸發模式Pattern: Map 0→311 → Talk: Rhea @Map311 → Talk: Rhea @Map311
💡 疑似原因：Rhea (EV003@Map311) 事件含 Autorun/平行處理且無退出條件，重複觸發導致畫面凍結 [3m17s (11,866f) · Map]Suspect: Rhea (EV003@Map311) has Autorun/Parallel without exit condition — repeated trigger causes freeze [3m17s (11,866f) · Map]
🔧 修復：Rhea (EV003@Map311) 的事件重複觸發凍結 — 可能缺少 Autorun 關閉開關或自我關閉（self-switch）。ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3🔧 Fix: Rhea (EV003@Map311) re-triggers and freezes — likely missing Autorun off-switch or self-switch guard. ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3
查看 1 筆詳情View 1 instances
#時間Time地圖Map位置Pos狀態State📷
#12026-04-26 14:44:5711F 大廳11F Hall(22,24)3m17s (11,866f) · Map📷
crash
1× stale — 10F 階梯10F Stairway ×1
觸發模式Pattern: Talk: Rhea @Map311 → Talk: Rhea @Map311 → Map 311→242
💡 疑似原因：Rhea (EV003@Map311) 事件含 Autorun/平行處理且無退出條件，重複觸發導致畫面凍結 [8m47s (31,674f) · Map]Suspect: Rhea (EV003@Map311) has Autorun/Parallel without exit condition — repeated trigger causes freeze [8m47s (31,674f) · Map]
🔧 修復：Rhea (EV003@Map311) 的事件重複觸發凍結 — 可能缺少 Autorun 關閉開關或自我關閉（self-switch）。ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3🔧 Fix: Rhea (EV003@Map311) re-triggers and freezes — likely missing Autorun off-switch or self-switch guard. ruby _Tools/map_inspector.rb Data/Map311.rvdata2 3
查看 1 筆詳情View 1 instances
#時間Time地圖Map位置Pos狀態State📷
#22026-04-26 14:47:3410F 階梯10F Stairway(14,22)8m47s (31,674f) · Map📷
crash
🔌 啟動失敗Boot Failures — 1 次當機crashes, 1 模式patterns
遊戲未成功啟動。檢查：Data 檔案完整性、Plugin 載入順序、初始地圖設定Game failed to start. Check: Data file integrity, plugin load order, initial map setup
低頻（1 個，各 ≤2 次）Low-freq (1, each ≤2)
1× no_state — Map0 ×1
觸發模式Pattern: Talk: Rhea @Map311 → Talk: Rhea @Map311 → Map 311→242
💡 疑似原因：遊戲完全未啟動或啟動立即崩潰，未回傳任何狀態Suspect: Game failed to boot or crashed immediately — no state data ever returned
🔧 修復：從命令列執行 Game.exe 觀察是否有 DLL 缺失或初始化錯誤訊息。🔧 Fix: Run Game.exe from command line and check for missing DLL or initialization error messages.
查看 1 筆詳情View 1 instances
#時間Time地圖Map位置Pos狀態State📷
#32026-04-26 14:49:43Map0(0,0)啟動階段boot phase📷
crash

地圖旅程Map Journey

時間分佈Time Distribution (3.3m 已追蹤tracked)
11F 大廳11F Hall 100%

按風險分數排序。公式：當機×3 + 超時÷5 + (進入>20則+5)。等級：Sorted by risk score. Formula: crashes×3 + timeouts÷5 + (visits>20: +5). Tiers: 危險CRIT ≥50 高HIGH ≥10 中MED >0

ID 地圖Map 風險Risk 當機次數 ÷ 進入次數 × 100Crashes ÷ Visits × 100">當機率Crash% 當機類型分佈：🧊凍結 💀錯誤 🔌啟動Crash type breakdown: 🧊Freeze 💀Error 🔌Boot">類型Type 進入Visits Bot 在此地圖停留的估算時間Estimated time bot spent on this map">停留Time 互動Interactions 事件數Events 標記Flags 此地圖最主要的問題事件Primary event causing issues on this map">主因Top Culprit 互動對象NPCs/Events
311 11F 大廳11F Hall 中MED 3 100% 🧊1 1
3.3m
 2 1 💥 ×1 ⏱ ×2 💥 Rhea EV003 →#1 Rhea
242 10F 階梯10F Stairway 中MED 3 100% 🧊1 1 — 0 0 💥 ×1 無互動No interact 💥 Rhea →#2 —
戰鬥紀錄Battle Log (無戰鬥記錄 — Bot 未觸發任何戰鬥事件No battles — bot did not trigger any battle events)

Bot 在本次測試中未進入戰鬥。可能原因：未到達戰鬥觸發區域、缺少觸發開關、或 NPC 互動被阻擋。Bot did not enter combat this session. Possible: battle trigger area not reached, required switch not set, or NPC interaction blocked.

下次測試建議Next Test Suggestions
1. 用 set_start_pos.rb 將起始點設在戰鬥觸發附近
2. 用 debug 腳本預設必要開關（如 NPC 好感度門檻）
3. 延長測試時間讓 bot 有機會自然探索到戰鬥區域 1. Use set_start_pos.rb to place start near battle triggers
2. Use debug script to preset required switches (e.g. NPC affection thresholds)
3. Run longer sessions so bot can naturally explore to battle areas

截圖時間線Screenshot Timeline

全尺寸截圖，按時間排序。點擊放大。重複的地圖傳送截圖已自動過濾。（7 張）Full-size screenshots in chronological order. Click to enlarge. Duplicate map transition shots auto-filtered. (7 total)

當機截圖Crash Screenshots 3
當機Crash 14:44:57 — 當機 #114:44:57 — Crash #1 @ 11F 大廳11F Hall(22,24)
Talk: Rhea → Talk: Rhea
當機Crash 14:47:34 — 當機 #214:47:34 — Crash #2 @ 10F 階梯10F Stairway(14,22)
Talk: Rhea → Map 311→242
當機Crash 14:49:43 — 當機 #314:49:43 — Crash #3 @ Map0Map0(0,0)
Talk: Rhea → Map 311→242
啟動截圖Boot Screenshots 1
啟動Boot 14:42:03 — 遊戲啟動14:42:03 — Game boot
地圖截圖Map Screenshots 2
地圖Map 14:42:05 — 進入 11F 大廳14:42:05 — Enter 11F Hall
地圖Map 14:45:23 — 進入 10F 階梯14:45:23 — Enter 10F Stairway
定時截圖Periodic Screenshots 1
定時Periodic 14:47:05 — 定時截圖（10F 階梯）14:47:05 — Periodic (10F Stairway)
快速偵錯指令Quick Debug Commands

常用偵錯指令集合。點擊任意指令複製。Consolidated debug commands. Click any to copy.

檢查問題事件Inspect Problem Events



快速定位到問題點Quick Start at Problem Points




其他工具Other Tools


ruby _Tools/set_start_pos.rb --show           查看目前起始位置Show current start position
ruby _Tools/set_start_pos.rb --restore        還原起始位置Restore start position
python _Tools/patch_test_module.py             停用標題跳過Disable title skip
python _Tools/patch_test_module.py --restore  還原標題跳過Restore title skip