Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Evochron Mercenary, false positive for Godot

未關閉
#30 8 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
godot
領域
tooling

研究方向

Locate the Godot detection rule that matches an .exe and same-basename .pck, then inspect how release dates could be used as an additional signal. Verify the rule against the Evochron Mercenary depot and check that legitimate Godot 3.0+ games still match. The payload names no source file or test, so the relevant rule and validation method must first be found in the repository.

由索引模型根據 Issue 內容生成。

描述

False positive
SteamDB link to the game

https://steamdb.info/app/71000/

What is it being detected as and what should it be detected as? Any other information?

Detected as Godot, but it doesn't seem to be.
Don't know what's the actual engine, might be in house.

Additional information

Windows depot: https://steamdb.info/depot/71001/

It matches the Godot rules as it has .exe and .pck with the same basename, which is indeed the main signature of Godot 3.0+ games:

EvochronMercenary.exe
EvochronMercenary.pck

But Evochron Mercenary was released in 2012, so 2 years before Godot's first open source release, and most importantly 6 years before Godot 3.0 which uses the ".pck with same basename as .exe" logic (previous releases required a main .pck named data.pck).

There's also a ton of other files which are not relevant for Godot, such as DirectX installer and MSVC redistributable DLLs. It's hard to say 100% that this could never match a Godot game as with a custom build and a custom-developed DirectX renderer one could get a distribution like this if one wanted to... but it's extremely unlikely.

If one can access the release date, the Godot rule could exclude games released before February 2014 (or possibly a few months later if needed - the first game released on Steam might be the Dog Mendonça demo: https://steamdb.info/app/330800/).

主要語言
PHP
星號
234
分支
113
PR 合併指標
30 天內沒有已合併 PR

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

SteamDatabase/FileDetectionRuleSets 的其他 Issue

查看 SteamDatabase/FileDetectionRuleSets 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。