Offer more computer difficulty levels than three
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 55/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
- 領域
- game-dev
研究方向
Read js/ai.js lines 13–17, then inspect the settings selector and saved-setting migration in js/config.js and js/main.js. Run npm test and review tests/unit/ai-strength.test.js to understand how strength is measured. Done when old easy, medium, and hard settings retain their strengths and every new level tests measurably stronger than the one below.
由索引模型根據 Issue 內容生成。
描述
Summary
The computer has only three levels, and the gap between them is large. Offer a finer scale, for example 1 to 6, built from the knobs the engine already has: depth, thinking time, blunder rate and tolerance.
Where
js/ai.js:13-17(AI_LEVELS: easy is depth 1 with 30% blunders, medium is depth 2, hard is depth 3 with a 1 s timed search)- The settings level selector, and the migration of the saved setting
Impact
Improving players get a step between medium and hard, and beginners get something gentler than easy. Stronger levels depend on a faster move generator, which is tracked separately (move generation dominates search).
Suggested fix
Turn AI_LEVELS into a numbered scale. Map today's easy, medium and hard to three of its steps, so saved settings keep their meaning. Add the new steps around them.
Open question: should this wait for #160 (a record of results against the computer), which could suggest a level?
Acceptance criteria
- Saved settings of easy, medium and hard still load as the same strength.
- Each level plays measurably stronger than the one below it in the existing
ai-strengthtests.
Getting started
- Relevant files:
js/ai.js,js/config.js,js/main.js(settings),tests/unit/ai-strength.test.js - How to run tests:
npm test
Filed by repo-audit/full-audit at 01c6a35. Severity: low. Effort: S. audit-key: enhancement|js/ai.js|AI_LEVELS
- 主要語言
- JavaScript
- 星號
- 4
- 分支
- 2
- 平均合併
- 22 小時 16 分鐘
- 30 天內合併 PR
- 9
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TMHSDigital/Static_Chess 的其他 Issue
-
enhancement help wanted severity: low
難度 4/5 3-5 天 新手友好度 58/100
TMHSDigital/Static_Chess#182 ·
維護者通常 1 天內回覆
-
help wanted severity: medium tech-debt
難度 4/5 3-5 天 新手友好度 45/100
TMHSDigital/Static_Chess#173 ·
維護者通常 1 天內回覆
-
severity: medium tech-debt
難度 5/5 一週以上 新手友好度 35/100
TMHSDigital/Static_Chess#171 ·
維護者通常 1 天內回覆
-
help wanted performance severity: medium
難度 5/5 一週以上 新手友好度 38/100
TMHSDigital/Static_Chess#168 · 1 則留言 ·
維護者通常 1 天內回覆
-
enhancement help wanted severity: low
難度 4/5 3-5 天 新手友好度 61/100
TMHSDigital/Static_Chess#161 ·
維護者通常 1 天內回覆
查看 TMHSDigital/Static_Chess 的全部 Issue
相似的 Issue
-
priority: low server testing
難度 1/5 1 小時以內 新手友好度 88/100
blamechris/chroxy#9277 ·
維護者通常 1 天內回覆
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)未關閉
難度 2/5 1-3 小時 新手友好度 62/100
microsoft/playwright#44289 ·
維護者通常 1 天內回覆
-
Bug
難度 2/5 1-3 小時 新手友好度 75/100
Ionaru/easy-markdown-editor#657 ·
-
難度 2/5 1-3 小時 新手友好度 66/100
TMHSDigital/Free-Game-Dev-Assets#320 ·
維護者通常 1 天內回覆
-
area:webapp bug finding
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆