- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
05807 | Documentation | Minor | Have not tried | Dec 26, 2014, 09:10 | Dec 26, 2014, 22:56 |
Tester | darq | View Status | Public | Platform | |
Assigned To | Resolution | No change required | OS | ||
Status [?] | Closed | Driver | |||
Version | 0.156 | Fixed in Version | Build | ||
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 05807: sf2jl: Year should be 1992. | ||||
Description | Any particular reason why the year is 1991, or just a typo? [Capcom original date says 920312] | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | sf2jl | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
3
No.11326
Haze Senior Tester
Dec 26, 2014, 13:35
edited on: Dec 26, 2014, 13:36 |
general policy is to use the year of original release there, rather than the year of the revision / hack. (so if you search the output of the MAME XML you can see games that were released in year x, rather than seeing a game span multiple years) there's definitely an argument for the alternative tho. |
---|---|
No.11327
darq Tester
Dec 26, 2014, 15:28
|
Ah I see, then the same thing for my punisherbz report, right? I didn't know about this policy. Mystery solved :-) |
No.11328
Stiletto Developer
Dec 26, 2014, 19:26
|
There's many such unofficial policies that aren't documented anywhere (ex. "the three-year rule"), you'll do well to mentally make a note of them as you run across them. :-) |