Variant Identifiers

When porting content from other variants, an identification scheme will be needed to keep track of where the content was ported from.

The IDs would be indicated in a table like variant_elona_ids in data prototypes, or in the region annotation comments for code changes. They should use the same validation for mod/data identifiers.

Naturally, this naming scheme is only preliminary.

Variant IDs

The following are some examples of the proposed naming scheme.

(TODO: These will need to be merged with https://github.com/Ruin0x11/elona_variants for preservation/consistency.)

• elona_1_22
  • Variant: Elona
  • Version: 1.22
  • sha256: 7aba63dde658ec065a40263565cffc93e3f1d1d980618c6d388f42ed3270d543 elona.exe
• oo_20160417_1400
  • Variant: omake_overhaul
  • Version: 2016/04/17 14:00
  • sha256: ee7293e380cfd3af2698c067d667daa5a6c4c6038f557cf9ff668e790b287798 omake_overhaul.exe
• oomsestepnc_20210528
  • Variant: oomSESTep_NC
  • Version: 2021/05/28
  • sha256: 46cb617d52abc0861478a649090c8d3c79e673a41583ce5cbdc712a619a48d19 oomSESTep_NC.exe
• plus_2_04
  • Variant: Elona+
  • Version: 2.04
  • sha256: 36d064e6cf4272944b9010541a969eb1c4a86c5ec3f75188571c131e407c9d03 elonaplus.exe
• plus_custom_1_90_4
  • Variant: Elona+ Custom
  • Version: 1.90.4
  • sha256: a043419f2e5f95cd6f7e67b37e4bf61872a84ec6d6132cdd5cbce441fea4630b elonac.exe
• plus_custom_g_1_90_4_2
  • Variant: Elona+ Custom-G
  • Version: 1.90.4.2
  • sha256: ebed8d9580fdc6cfd0380fd3fa24b66258b45372999695d5e3ff2b57d944e152 elonacg.exe