ShuriZma
/
BizHawk
mirror of https://github.com/TASEmulators/BizHawk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add some sort of documentation for B/V gamedb flags

This commit is contained in:
YoshiRulz 2023-01-05 00:41:25 +10:00
parent 60f99bc3ab
commit af9f5b9b9c
No known key found for this signature in database
GPG Key ID: C4DE31C245353FB7
2 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Assets/gamedb/gamedb.txt
View File

@ -33,6 +33,12 @@
#include gamedb_channelf.txt
#includeuser gamedb_user.txt
; so, there's just zero explanation anywhere for B vs V status flag
; really, I checked https://github.com/TASEmulators/BizHawk/commits/c8727ae01fc051429a59c4b91189ef479d578be7?after=c8727ae01fc051429a59c4b91189ef479d578be7+34&branch=c8727ae01fc051429a59c4b91189ef479d578be7&path%5B%5D=BizHawk.MultiClient&path%5B%5D=output&path%5B%5D=gamedb.txt&qualified_name=c8727ae01fc051429a59c4b91189ef479d578be7
; (if link dies, it's last page of history for `/BizHawk.MultiClient/output/gamedb.txt`)
; and it's not a borrowed convention from no-intro or bootgod either as far as I can tell
; based only on the unstructured comments in the inital upload (054ad76ac), I'm guessing B = bad and V = very bad --yoshi
; ************ TI-83 ************
4EDF419CAA9FB0542B4FED8BCD8B54C2 TI-83 v1.02 TI83 initPC=6ce

4
src/BizHawk.Emulation.Common/Database/Database.cs
View File

@ -128,8 +128,8 @@ namespace BizHawk.Emulation.Common
Status = items[1].Trim()
switch
{
"B" => RomStatus.BadDump,
"V" => RomStatus.BadDump,
"B" => RomStatus.BadDump, // see /Assets/gamedb/gamedb.txt
"V" => RomStatus.BadDump, // see /Assets/gamedb/gamedb.txt
"T" => RomStatus.TranslatedRom,
"O" => RomStatus.Overdump,
"I" => RomStatus.Bios,