IUPAG

Spec-Sheet ~ Prefixes & Suffixes (v2).txt

Aug 10th, 2023 (edited)
576
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 23.13 KB | Gaming | 0 0
  1. # ****************************************************************
  2. # IUPAG Nomenclature (Naming Convention): (v2025-01-17)-(rev3.5):
  3. # ****************************************************************
  4. # - By Gamers, For Gamers:
  5. # ..Committed to the Organization, Preservation, & Development of Romhacks.
  6. # ****************************************
  7. # IUPAG Prefixes: (v2025-01-17)-(rev3.5):
  8. # ****************************************
  9. # 1R: (1)-dimensional (R)un-N-Gvn: Platform SH00T3Rs.
  10. # 2R: (2)-dimensional (R)un-N-Gvn: Overhead SH00T3Rs.
  11. # 3R: (3)-dimensional (R)un-N-Gvn: FPS & Gallery SH00T3Rs: {LG} suffix indicates Light-gvn compatible.
  12. # 4S: (H)ybrid (S)H00T3R with multiple game modes (like 1R/2R, 1R/5H, or 2R/3R (etc), but NOT 5H/5V).
  13. # 5F: (S)H00T3R (F)lying: 1st & 3rd Person, 3D SIM &/or Action Arcade style.
  14. # 5H: (S)H00T3R (H)orizonal.
  15. # 5HV: (S)H00T3R (H)orizonal & (V)ertical: Multiple game modes: 5H & 5V.
  16. # 5V: (S)H00T3R (V)ertical.
  17. # 5Z: (S)H00T3R Miscellaneous(Z): Isometric scrolling &/or Multi-directional without auto-scrolling (etc).
  18. # 6O: (O)lympic (G)ames.
  19. # 720: Skating, Skiing, & Snowboarding games w/ 180, 360, [720], & 1080 tricks.
  20. # 841: =BALL: Dodgeball, Kickball, Volleyball, & other Misc Sports, like Speedball & Rugby, etc.
  21. # 964: Rhythm & Action games: (P)ower-Pad, (G)uitar, & Controller Rhythm & (A)ction games.
  22. # BG: (B)oard (G)ames & TV show games: e.g. (Monopoly)/(Wheel of Fortune).
  23. # BMC: Fishing games: (B)ass (M)aster (C)lassic.
  24. # DIS: Disney, Warner, & Hanna-Barbera cartoon based games (except sports).
  25. # F1: (F)ormula-(1): 1st-person & 3rd-person Racing games with a 3D view.
  26. # F2: (F)ormula-(2): 2nd-person Racing games with a birds-eye, overhead view.
  27. # F7: (F)amily (T)rainer: All other Power-Pad games (except sports: 6O & 964).
  28. # FIFA: Soccer games: (F)ederation (I)nternationale de (F)ootball (A)ssociation.
  29. # K0EI: Koei (& Koei-like knockoff) strategy games: Aerobiz, Gemfire, Genghis, Nobunaga, Romance, Sangokushi, etc.
  30. # Mario: All Mario, Wario, & Yoshi games that take place in the Mario universe (except sports).
  31. # MLB: Baseball games: (M)ajor (L)eague (B)aseball.
  32. # NBA: Basketball games: (N)ational (B)asketball (A)ssociation.
  33. # NFL: Football games: (N)ational (F)ootball (L)eague.
  34. # NHL: Hockey games: (N)ational (H)ockey (L)eague.
  35. # P1N: Pinball games: IFPA: (I)nternational (F)lipper (P)inball (A)ssocation.
  36. # P88I: Table-top (P)ool, (8)-ball, & (B)(I)=Billiards games.
  37. # PB4: Bowling games: (P)rofessional (B)owlers (A)ssociation: PBA.
  38. # PG4: Golf & mini-golf games: (P)rofessional (G)olfers (A)ssociation: PGA.
  39. # Pokemon: All Pokemon & Pikachu games that take place in the Pokemon universe (except sports).
  40. # PZ: (P)uzzle games: Like Tetris, Puyo Puyo, Panel de Pon, etc.
  41. # Simpsons: All Bart & Krusty games that take place in the Simpsons universe (except sports).
  42. # Sonic: All Sonic & Tails games that take place in the Sonic universe (except sports).
  43. # T3N: Tennis games: Association of Tennis Professionals: ATP.
  44. # TMNT: All (T)eenage (M)utant (N)inja (T)urtles universe games (except sports).
  45. # VS: [Versus], Two-Player Fighting games & Boxing games (VS BX), but NOT "Beat'em-Ups".
  46. # WSOP: Gambling games: (W)orld (S)eries (O)f (P)oker.
  47. # WWF: Wrestling games: (W)orld (W)restling (F)ederation: (aka WWE).
  48. # Zelda: All Zelda & Link games that take place in the Hyrule universe (except sports).
  49. # **********************************************
  50. # IUPAG Symbols & Tags: (v2025-01-17)-(rev3.5):
  51. # **********************************************
  52. # The default ordering of Tags can be read as:
  53. # ..."by, for, on, as, in, flagged, with, and".
  54. # ..."(@BY), (#FOR), (vON), (revAS), (T-IN), [flagged], {with}, (and)".
  55. # ..."by Author, for Region, on Date, as Revision, in Language, dump-flag, with Attributes, and MetaInfo.
  56. # --------------------------------------------------------------------------------------------------------
  57. # PR3F1X Title - Subtitle (@Dev,Pub)-(#Region)-(vYYYY-MM-DD)-(rev10)-(T-En) [!]-{Attributes}-(MetaTag).ext
  58. # --------------------------------------------------------------------------------------------------------
  59. # PR3F1X: One of the above IUPAG "Sports" prefixes.
  60. # Title: Rules:
  61. # : (1) "Title" is the name of the "Series" (if one exists):
  62. # : ..in which case the original "Title" becomes the "Subtitle":
  63. # : ..e.g. "Soul Trilogy" 1,2,3: Soul Blazer, Illusion of Gaia, Terranigma.
  64. # : ..e.g. "Zelda" 1,2,3: Legend of Zelda, Adventure of Link, A Link to the Past.
  65. # : (2) When all Regions have a different release name:
  66. # : - then the "Title" is the shortest name (with exception), of all the Regions:
  67. # : ..e.g. Sanguozhi, Tenchi wo Kurau, Destiny of an Emperor:
  68. # : .."Sanguozhi - Destiny of an Emperor (@Capcom)" (North American ROM).
  69. # : .."Sanguozhi -; Tenchi wo Kurau @Capcom)" (Japanese ROM).
  70. # : .."Sanguozhi -; Ying Jie Zhuan (@Waixin)" (Chinese Pirate ROM).
  71. # : Exceptions (with preference given to the North American release title):
  72. # : .."Streets of Rage - Bare Knuckle".
  73. # : .."Earthbound 0 - Mother 1".
  74. # : .."Earthbound 1 - Mother 2".
  75. # : .."Earthbound 2 - Mother 3".
  76. #Separators: (between Title & Subtitle):
  77. # "-": Parent.
  78. # "-;": Clone (or official Translation).
  79. # ";=": Unofficial, 3rd Party Translation.
  80. # "~": Hack.
  81. # "~[X]": SMW Hack with difficulty "X": 0-9, P (Puzzle), T (Troll).
  82. # "~_[GP];": Optional, Gameplay Patch (aka "QoL" Patch).
  83. # Subtitle: Rules:
  84. # : The Subtitle is generally the Hack Name.
  85. # : ..the "subtitle" (hackname) can be prefixed with difficulty, patchtype, &/or Holiday Theme, etc.
  86. # : - invalid filename characters: \/:*?"<>|\t\r\n\0
  87. # : Dashes & Colons:
  88. # : ..replace dashes & colons with semi-colons.
  89. # : Slashes: (backslashes & forward slashes):
  90. # : ..replace slashes with the percent-sign (%): Mostly used for Randomizer URLs.
  91. # : Parentheses:
  92. # : - because these denote "Tags",
  93. # : ..they are generally discouraged as valid characters in the title & subtitle:
  94. # : ..except when the 1st Tag is a "Named Tag" (a Tag with a consistent prefix):
  95. # : ..e.g. (@Author), (#Region), (vDate), (revZ), (T-Lang).
  96. # : ..Not allowed when the 1st Tag is "unnamed", like (Region) instead of (#Region).
  97. # : ..Not allowed inside any (Tag), like (@Authors).
  98. # (@Author): Author, Publisher, Developer, Hacker, &/or Translation Team.
  99. # : - For ROMs, this is typically (@Developer,Publisher).
  100. # : - For Hacks, the order is chronological: So, if you hack a preexisting Romhack,
  101. # : ..then you would just append your name: e.g. (@pacnsacdave,YourName),
  102. # : ..in order to retain credit for the original author.
  103. # : - Exception:
  104. # : ..exception is given for Romhacking Communities that share a common "base hack",
  105. # : ..where potentially many, many people contributed:
  106. # : ..And each "fork" deviates substantially in goal & theme (like completely different levels):
  107. # : ..in which case, credit is given via the {Patches Tag} (see below).
  108. # : ..However, the chronological append rule still applies if it's just a small update to the "base hack".
  109. # : - Maximum of 3-4 credits (depending on length):
  110. # : ..if the number of contributors (or length) gets too long, then:
  111. # : ..designate either a team name identifier (or "(@Authors=25)"), then
  112. # : ..list the credits in the (MetaTag): [$]-{--}-({@Auth1,Auth2,Auth3,Auth4,Auth5,Auth6}).nes
  113. # (#Region)/(#Base-Code):
  114. # : (#Region) for Parent/Baseroms (and their "clones"):
  115. # : (#Base-Code) for Hacks & Translations.
  116. # (#Region): Fully-Qualified, comma-separated list of supported Regions: i.e. (#USA,Europe).
  117. #(#BASE-00): This is the Region-Revision number that was used as the BASE for the Hack/Translation:
  118. # : ..e.g. (#USA-00) / (#Europe-10) / (#Japan-11).
  119. # : ..a List of Regions (#USA,Europe) (rev12) can be shortened to: (#USA-12)
  120. # : If the Parent/Baserom is unknown, then it can be determined with the following command:
  121. # : for file in Example\ -*; echo "$file"; cmp -l "$file" 'Example ~ Hack.ext' | wc -l; done
  122. # : ..note, however, that the above backslash is NOT a directory: It is a SPACE.
  123. # (vDate): Guidelines:
  124. # : Date of Publication/Compilation: ...with "Unix Time Zero" (v1970-01-01) as "Unknown Date".
  125. # : - For Official, Licensed releases, the Date of Publication is favored (with exception).
  126. # : ..One exception being that the Pub Date is before the Build Date, which is impossible & incorrect.
  127. # : - For Romhacks & Translations, the Date of Compilation is favored (with exception).
  128. # : ..ideally, the Pub Date & Build Date should match.
  129. # : ..if the Build Date is after the Pub Date, then it means either:
  130. # : ..(1) The original patch was lost to time & remade & uploaded by someone else (not the Author).
  131. # : ..(2) The "Pub Date" likely only signifies the 1st release: Not the current updated version.
  132. # : Ambiguity: "Langrisser 2 English Patch - 3/21/2001 (released 9/16/2004)"
  133. # : https://www.romhacking.net/translations/70/
  134. # : https://www.romhacking.net/translations/genesis/patches/70readme.txt
  135. # : ..Use Build Date, since the patch was created with 2001 tools (if any existed).
  136. # : ..Pub Date is deceptive as the patch was not created with 2004 tools.
  137. # : ..Furthermore, Romhackers can claim that it was never officially published, but...
  138. # : ..once they hand it off to other Team Members (Testers/Devs), then...
  139. # : ..it means that the "private release" could be floating around in the Wild..
  140. # : ..causing massive confusion having the exact same file with two different Dates.
  141. # (revZ): Guidelines:
  142. # : (1) ROMS:
  143. # : - Generally, "(rev10)" (pronounce "One-OH", not "ten") defines the initial release.
  144. # : ..this is equivalent to "(Rev 0)" in a no-intro set.
  145. # : ..while "(rev11)" would be equivalent to "(Rev 1)" in no-intro.
  146. # : - "(rev00)" is normally a prototype (Proto),
  147. # : ..while 01-09 are reserved for Alpha/Beta/Demo/Sample releases.
  148. # : - This system ensures an easy reference to the Parent/Baserom for patches & auto-patchers.
  149. # : ..which reduces the computational strain at runtime & speeds-up the execution for patching entire Sets.
  150. # : (2) Romhacks & Translations:
  151. # : ..(revZ) tag is their "version number", which can be absolutely anything,
  152. # : ..but generally, below one is an Alpha, Beta, or Demo pre-releases (previews).
  153. # : ..while greater than one signifies a polished, bug free, finished state.
  154. # "TEXT"/Language:
  155. # (T-Ln): "Text-IN": "T dash" means "Text-IN" for all ROMs (except translations).
  156. # : ...Prevents "Naming Collisions" for ROMs released in more than one Language.
  157. # (T+Ln): "Text+TO": "T plus" means "Text+TO" for translations.
  158. # : ...This is primarily a Translation Project only (with minimal QoL patches).
  159. # [flags]: "Dump Info Flags":
  160. # [!]: Verified Good Dump (except hacks):
  161. # : Title - Subtitle (@Dev,Pub)-(#Region)-(vYYYY-MM-DD)-(rev00)-(T-En) [!]-{Genre}-(MetaTag).ext
  162. # : Title -; Subtitle (@Dev,Pub)-(#Region)-(vYYYY-MM-DD)-(rev00)-(T-Lx) [!]-{Genre}-(MetaTag).ext
  163. # [$]: Verified Good Hack (or Translation):
  164. # : Title ;= English (@Auth)-(#BASE-10)-(vYYYY-MM-DD)-(revZ)-(T+En) [$]-{--}-(MetaTag).ext
  165. # : Title ;= English (@Auth)-(#BASE-11)-(vYYYY-MM-DD)-(revZ)-(T+En) [$]-{Optional.ips}.ext
  166. # : Title ~ HackName (@Auth)-(#BASE-10)-(vYYYY-MM-DD)-(revZ)-(T-En) [$]-{--}-(MetaTag).ext
  167. # : Title ~ HackName (@Auth)-(#BASE-11)-(vYYYY-MM-DD)-(revZ)-(T-En) [$]-{Optional.ips}.ext
  168. # [x]: Unverified ROM dump.
  169. # [h]: Unverified Hack:
  170. # [tr]: Unverified Translation:
  171. # : ..These are hacks/translations from unknown &/or untrusted sources,
  172. # : ..that haven't been tested & verified to work on at least one emulator.
  173. # : - Basically, this system of [h] & [tr] to [$] ensure that patches were verified to be applied correctly:
  174. # : ..designate [h] (or [tr]) when adding, and later, change to [$] when verified as good & working.
  175. # [o]: Over dump.
  176. # [b].mia: placeholder for an undumped game: "Missing In Action".
  177. # : ..In order to be processed by Rom Managers, cannot be an empty, zero-byte file:
  178. # : ..Can write anything to the file, like a unique number OR simply the filename (or both).
  179. # [p].ips: means "Patch" & signifies to Auto-Patchers to retain as patchfiles.
  180. # : .."Pirate" goes under the (MetaTag).
  181. # [a]: Deprecated: Use (MetaTag) for tagging "Alternate"/"Alt" dumps (see below).
  182. # [f1]: Deprecated: Use {Attributes/PatchList} tag to denote "fixes" (see below).
  183. # {Attributes}: A List of Attributes for a ROM (or romhacks & their patches).
  184. # : For Parent/Baseroms/Clones, the {Attributes} tag lists:
  185. # : ..{<Number of Players>,<Genre/GameTypes>,<Controller Support>}
  186. # : Romhacks (& Translations) inherit all these attributes, and instead, list:
  187. # : ..all the extra patches applied to the romhack, or none via: [$]-{--}.ext
  188. # {Genre}: {Attributes/GameTypeList}:
  189. # [!]-{X,Y}: Comma-separated List of L33TC0D3 GameTypes for the Baseroms (and {Patches} for hacks).
  190. # : ..These L33TC0D3S are easier to parse with and are listed in the "Suffixes" section.
  191. # : - Becomes a csv List of Internal, Optional, & External Patches for Hacks.
  192. # : ..In the rare case where the hack genre differs from the Baserom genre,
  193. # : ..then use a "prefixed Subtitle tag" to denote this difference: e.g.
  194. # : 2R BattleCity ~ [1R]; Star Wars (@TLT)-(#Japan)-(v2007-07-06)-(rev1.4)-(T-En) [$]-{--}.nes
  195. # {patch}: {Attributes/PatchList}:
  196. # [$]-{--}: Comma-separated List of patches that were:
  197. # : (1) applied by Author during development (internal patches),
  198. # : (2) applied by Player with release (optional patches),
  199. # : (3) applied by Player after release (external patches).
  200. # : These patches are Listed IN THE ORDER that they were applied.
  201. # : UNLESS an actual verification process was used to determine 100% compatibility & zero conflicts:
  202. # : (a) address verification during compilation.
  203. # : (b) address verification before being applied.
  204. # : (c) hash code testing on the binaries.
  205. # : ...In which case, Alphabetical Order is preferred for each category:
  206. # : ...1st, internal patches listed in Alphabetical Order.
  207. # : ...2nd, optional patches listed in Alphabetical Order.
  208. # : ...3rd, external patches listed in Alphabetical Order.
  209. # {--}: Means that optional, or external patches were applied to this Hack.
  210. # : ...Example: One patch applied, with abbreviated initials "IC" (Improved Controls): [$]-{+IC}.ext
  211. # : ...Example: Multiple patches applied: [$]-{+BF,IC}.ext
  212. # {%}: Means Unknown: Documentation doesn't state which [GP] patches were used in development.
  213. # {=BF}: Patch definition: Defines an abbreviation "BF" for the named patch ("Bugfixes").
  214. # : ...A popular & common combination of patches defined (or released as a Set): [$]-{+AC,BF,IC=ABC}
  215. # : ...{+ABC} can now be used to refer to an entire LIST of patches.
  216. # {+BF}: An eternal patch, abbreviated with the initials BF ("Bugfixes") has been applied to the hack.
  217. # : The {=BF} patch file encodes all meta-info: Author, Date, Revision, etc.
  218. # [fN]: The GoodSets designation for the number (N) of optional patches (fixes) applied: Deprecated.
  219. # :
  220. # Finally, since Tag separation is done differently in no-intro (spaces) & TOSEC (no spaces),
  221. # IUPAG Parent Spec will use dash separators, with a space in between the Tags & [Dump-Info-Flag].
  222. # ..This is a nod to our IUPAC heritage that signifies "A Chain of Carbon" atoms that makeup a molecule.
  223. # ..As well as signifying that, while we take inspiration from our predecessors, we don't play favorites,
  224. # ..and THIS (as well as other issues) is something best left to the players individual preferences,
  225. # ..which is unfortunately lacking in the current standards.
  226. #
  227. # **********************************************************************
  228. # IUPAG Genre & GameType Attributes (Suffixes): (v2024-09-06)-(rev3.5):
  229. # **********************************************************************
  230. # -------------------------------------------------------------------------
  231. # - Order: {<Number of Players>,<Genre>,<Controller Support>}
  232. # : ...e.g. "{2P,3A,LG}":
  233. # : ...Means "{2-Player, 3-dimensional Action/Adventure, Light-Gvn}"
  234. # -------------------------------------------------------------------------
  235. # {1P}: 1-Player Game: Required for games with a "Sports" prefix (otherwise, optional as its assumed by default).
  236. # {2P}: 2-Player Game: Mandatory for all games with multiplayer functionality: e.g. {2P,4P}.
  237. # {B34T}: Beat'em up.
  238. # {PL4T}: "1-dimensional" Platformer with Linear Progression (on a single "axis" left-to-right).
  239. # {1A}: (1)-dimensional Platformer with Adventure & requiring exploration to progress.
  240. # {2A}: (2)-dimensional Action Adventure with an Overhead, Birds-eye view.
  241. # {3A}: (3)-dimmenional Action Adventure with a 3D (Dungeon Crawler) view.
  242. # {4A}: (A)ction or (H)ybrid Adventure with multiple game-modes.
  243. # {5A}: (S)trategy Adventure: e.g. (Starflight).
  244. # {6A}: (S)pace Adventure (with alt-gravity &/or alt-physics).
  245. # {7A}: (T)ext-based Adventure: e.g. (Erika to Satoru no Yume Bouken).
  246. # {8A}: (B)eat'em up view / isometric perspective Action Adventure: e.g. (Time Lord).
  247. # {9A}: (P)ower-Pad (A)dventure game: e.g. (Street Cop - Manhattan Police).
  248. # {1RPG}: (1)-dimensional Platformer with RPG elements (like xp & level-ups).
  249. # {2RPG}: (2)-dimensional RPG with an Overhead, Birds-eye view: Traditional JRPGs.
  250. # {3RPG}: (3)-dimensional RPG with a 3D (Dungeon Crawler) view.
  251. # {4RPG}: (A)ction (H)ybrid RPG with multiple game-modes, like 1/2 or 2/3 (for example).
  252. # {5RPG}: (S)trategy RPG (Turn Based Strategy): e.g. (Shining Force).
  253. # {5RTS}: (S)trategy RTS (Real Time Strategy): e.g. (Command & Conquer).
  254. # {1S&P}: (1)-dimensional (S)trategy (&) (P)uzzle: e.g. (A Boy & His Blob).
  255. # {2S&P}: (2)-dimensional (S)trategy (&) (P)uzzle: e.g. (Quinty)/(Mendel Palace).
  256. # {3S&P}: (3)-dimensional (S)trategy (&) (P)uzzle: e.g. (Portal).
  257. # {4S&P}: (A)ction (H)ybrid (S)trategy (&) (P)uzzle: e.g. (Spy vs Spy).
  258. # {S1M}: Simulation: e.g. (SimCity),(The Sims),(Flight Simulators), etc.
  259. # {$SIM}: Strategy Simulation: e.g. (Koei Historical Warfare games).
  260. # {QZ}: Quiz Game: e.g. (King of Kings by Wisdom Tree).
  261. # {Mouse}: Controller Support: Mouse compatible game.
  262. #Power-Pad: Controller Support: Power-Pad compatible game.
  263. # {Rod}: Controller Support: Fishing-Rod compatible game.
  264. # {LG}: Controller Support: Light-Gvn compatible game.
  265. # ***************************************
  266. # IUPAG MetaTag: (v2025-01-17)-(rev3.5):
  267. # ***************************************
  268. # The (MetaTag) can be used for a variety of extra information:
  269. # - Like (Alpha), (Beta), (Demo), (Proto) releases.
  270. # - And nsfw designation: "Not Safe For Work":
  271. # ..The nsfw tag is primarily used to denote nudity,
  272. # ..since blood, violence, & language are pretty common in most games.
  273. # For Parent/Baseroms,
  274. # - (Unl; Aftermket) &/or (Pirate).
  275. # - including re-releases from (Virtual Console), (Switch Online), (Steam), (GOG), etc.
  276. # - Order of Precedence:
  277. # ..highest priority (first): Unl, Pirate, Aftermarket.
  278. # ..lowest priority (last): Proto, Alpha, Beta, Demo, Sample, Reprint, Alt.
  279. # ..e.g. (Unl; Aftermarket; Steam, Itch, GOG; Windows, Mac, Linux; Demo)
  280. # For Romhacks:
  281. # - The number of Exits in a Super Mario World romhack: (Exits=100)
  282. # - The number of Stars in a Super Mario 64 romhack: (Stars=120)
  283. # - The Mapper number of an NES Hack with multiple versions: (M#001)/(M#004)
  284. # - The "Brand", like 'TMNT of Rage': 'Turtle Power', 'Remix', 'The Final Shell Shock', etc.
  285. # ..as if you put this into the sub-title, then they're not sorted in chronological order.
  286. # - And other MetaInfo, like ('Special Edition'), for example.
  287. # For Translations:
  288. # ..in rare cases, some Translation Teams have released two versions,
  289. # ..with different "types" of translations:
  290. # (1) a more strict, "literal" translation, and
  291. # (2) a more creative interpretation with "localization":
  292. # ..Here, the (MetaTag) can be used to differentiate between the two.
  293. # For Patches:
  294. # - Can also be used for "Dependency Declarations": aka "Addendum" ("&") patches:
  295. # ..that says you need to apply another patch first.
  296. # ..e.g. "-(&{for Stef's [PCM] Driver Fix}).ips"
  297. # ..or, "-(&{for Stef's Sound Driver Fix; [PCM]}).ips"
  298. # ..where [XYZ] is the abbreviated initials of the required patch,
  299. # ..and can appear anywhere in the comment "-(&{...})":
  300. # ..beginning, middle, or end... doesn't matter.
  301. # Rules:
  302. # ..Obviously, the (MetaTag) cannot start with characters:
  303. # .."(@","(#","(v","(rev","(T-","(T+"...
  304. # ..as these symbols already denote "Named Tags" for,
  305. # ..Authors, Region, Date, Revision, & "Text" (Language).
  306. # ..However, the (MetaTag) can be used to list additional credits:
  307. # ..(when the list is too long for the (@Author) tag):
  308. # ..[$]-{--}-({@Auth1,Auth2,Auth3,Auth4,Auth5,Auth6}).ips
  309. # *********************************************************************
  310. # IUPAG Rating/Ranking/Percentile Tag: (v2025-01-17)-(rev3.5-SNAPSHOT):
  311. # *********************************************************************
  312. # - OPTIONAL, NOT DEFINED, NOT IMPLEMENTED, PROPOSAL ONLY:
  313. # ..Either filename Tag or DAT Element Tag,
  314. # ..for searching, sorting, filtering, trimming:
  315. # For example,
  316. # ..to trim Sets down to the "Top 100", "Top 80%", "TOP 2gb" of games.
  317. # ..to provide a mechanism to sort games by rating/ranking.
  318. # **************************************************
  319. # IUPAG Sets:--------------------------------------
  320. # **************************************************
  321. https://pastebin.com/u/IUPAG
  322. # **************************************************
  323. # IUPAG DATs:---------------------------------------
  324. # **************************************************
  325. https://github.com/IUPAG
  326. # **************************************************
  327. # IUPAG Archive & Repository:-----------------------
  328. # **************************************************
  329. https://archive.org/details/@iupag
  330. # **************************************************
  331. # IUPAG Discord server:-----------------------------
  332. # **************************************************
  333. https://discord.gg/kEe3aUzJ5D
  334.  
Add Comment
Please, Sign In to add comment