Feature Definitions & Use Case

This page is more for developers. If you are a (future) user and want to submit a feature request please use the forum.

Requested Features Definitions, Use Case description.

• Support merged MAME data by importing custom lists with custom data, not available from current data sources (e.g. information not in mame lixtxml, catver, controls or nplayers, or e.g. "Top 100 clones worth playing"):

  • Use case: User can import custom data in supported format (tbd) to DB and use such data to complement available data for additional filtering.

• revisioning between MAME versions, exportable to custom lists.

  • Use case: User can review changes between MAME versions, e.g. MAME 0.144 -> 0.145 or a.e.g. 0.142 -> 0.145, may it be emulation status, romname changes, Game Name changes, change of other information within default filters (tbd) supported by Game Set Match, User can export list of games with changes amongst MAME versions.
  • Use case: User can create a game list based on e.g. 0.142, then later, when User wants to update created custom gamelist to e.g. 0.145, Game Set Match compares the full 0.145 data against the created custom 0.142 gamelist, and returns version changes prefiltered against the 0.142 custom list, making updates to personal game lists simple.

• data deviation management (e.g. mame listxml game X = 2p6b vs nplayers.ini game X = 2p4b; what to do?)

  • Use case: User can review mismatch among input data, options to resolve (tbd) are offered. User can export deviation data.

• resulting list management categorized to "keep", "drop", "review", functionality to move entries between these 3 views, logging of automatic and manual move processes.

  • Use case: User is presented with three such categories, and can move list entries among these three categories.

• custom definable filters incl. operators (e.g. <>=!&or) and range definition (year e.g. 1988-1997)

  • Use case: once User has applied default filters, resulting keep/drop/review-lists can be filtered by custom input queries.

• export to formats: front-end-specific game-list-formats, txt, csv, xml

  • Use case: User has created the desired file(s) for intended use, e.g. personal game list in a front-end for MAME.

• multi-platform: e.g. win, osx, linux

  • Use case: User is not depending on specific operating system to use Game Set Match.

Planned Features

• Use all information from the MAME XML data as filter except ROM data.
• Merge MAME data with data from catver.ini, nplayers.dat and genre.dat.
• Use game lists as filters.
• Use ranking/weight (e.g. from polls) to order resulting game lists.
• Translate to German and possibly other languages.

Conceptual Flowchart