Advertisement
atreyu187

ReviveDC : Release Guide Lines v3.0 2013 Edition

Dec 23rd, 2012
439
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.38 KB | None | 0 0
  1. ReviveDC Bible, Version 3.0
  2.  
  3. **************************************************************
  4.  
  5. Changes:
  6. 3.0 Changes to game naming, regions
  7. 2.0 Massive text overhaul to reflect new posting style
  8. 1.0 None! Original version.
  9.  
  10. **************************************************************
  11.  
  12. Table of contents:
  13. Section 0: Changes
  14.  
  15. Section 1: The Blog
  16. 1.1 Reviews (commercial) - updated
  17. 1.2 Reviews (emulation)
  18. 1.3 Allowed postings
  19. 1.4 Do not post
  20.  
  21. Section 2: Game images
  22. 2.1 Allowed images - updated
  23. 2.2 Not allowed
  24. 2.3 Conventions - updated
  25. 2.4 Uploading
  26. 2.5 Repacks - updated
  27. 2.6 Game Queue - IMPORTANT
  28.  
  29. Section 3: Artwork
  30. 3.1 Templates
  31. 3.2 Stretching
  32. 3.3 Acceptable artwork
  33. 3.4 Resolutions
  34. 3.5 Exporting from Photoshop
  35. 3.6 Trumping artwork
  36.  
  37. Section 4: Miscellaneous
  38. 4.1 RDC-XXXX Numbers - updated
  39.  
  40. **************************************************************
  41. Section 0: Changes
  42. I'm getting the feeling that our quality has been slipping lately. I feel like we're missing out on something by not doing multiple regions since we get comments on sites from people saying "not working on PAL" and whatnot. I also feel like we can provide more information about the game,
  43. so re-read everything and get a feel for what's changing.
  44.  
  45.  
  46. Section 1: The Blog
  47.  
  48. 1.1 Reviews (commercial):
  49. Title the blog post as Game Name Review.
  50. EX: Street Fighter Alpha 3 Review
  51. Before beginning a review, a small section with game information should be included. The first should be release dates (typed as Release dates: and italicized). There should be a line for North America, Europe and Japan. If the game was not released in a region, leave the line there and type unreleased. Dates should be in the format of Month Day, Year. If the game was released under a different name then add (As XXXXX XXXXX) after the date for the region.
  52. Following the release dates section, there should also be a game details section (typed as Game details: and italicized). The information in this section should be generally what you would find on the back of the game's case (the number of players, etc.). If there are features not listed on the back of the box (such as VGA compatibility), include them.
  53. The review itself should be broken up into different sections. There should be a short introductory paragraph (not labeled), followed by six sections; gameplay, control, storyline, graphics, sound and a conclusion. After the conclusion, assign the game a rating out of 10. Avoid using slang like lol, etc. Think of it like you're writing a review for site like IGN, except you don't have advertiser dollars influencing your score of the game.
  54.  
  55. 1.2 Reviews (emulation)
  56. Title the blog post as Game Name (Emulator) Review. For example: Metal Slug (NEO4ALL RC4) Review. Instead of a release date section put Original release: (italicized) and the earliest known release date of the game (on the emulated system) and the console afterwards. For example, if writing for Metal Slug: Original release: May 24, 1996 (Neo Geo). Include the game details section with relevant information. If writing about a bleemed game make sure to put "Saving not functional." Instead of an introductory paragraph, insert the following text, italicized:
  57.  
  58. The following game was not officially released for the Sega Dreamcast. It is emulated using (emulator name) developed by (developer). This is an evaluation of the emulation of the game as well as the game itself.
  59.  
  60. (Include this section if the game functions standalone in NEO4ALL or is a bleemcast game) Using Team RDC's release, you can play this game on your Dreamcast as though it is a commercial game with only a brief loading screen.
  61.  
  62. (Include this section if the game must use the NEO4ALL menu) Using Team RDC's release, you an play this game on your Dreamcast after pressing start on the NEO4ALL emulator's menu.
  63.  
  64. In addition to the standard five sections, add an emulation section preceding the other sections. Discuss the game's speed and other aspects of the emulation. Be sure to note any slowdown that comes from the actual hardware (Metal Slug, for example features slowdown on the original hardware).
  65.  
  66. 1.3 Allowed postings
  67. News related to the Dreamcast scene, news relating to new ports of Dreamcast games, editorial content that is related to the Dreamcast (or the gaming industry in general if it ties to the Dreamcast) and announcements regarding the group.
  68.  
  69. 1.4 Do not post
  70. Download links.
  71.  
  72. **************************************************************
  73.  
  74. Section 2: Game images
  75. 2.1 Allowed images
  76. NEO4ALL games, AES4ALL games that are playable (IE decent frame rate), Bleemed games that do NOT rely on saves (no RPGs), commercial games (GDI, CDI, CDI sizes of any minutes), betas or unreleased games, demos. Music hacks that feature original music or remixes. Compilations will also be allowed for games that are somehow related. For example, a compilation of the Power Stone games is acceptable. A collection of King of Fighters and Street Fighter games is not acceptable.
  77.  
  78. 2.2 Not allowed
  79. Crappy texture hacks, Bleemed games that rely on saves, music hacks that are compiled from random sources (for example, an all rap version of MvC 2).
  80.  
  81. 2.3 Conventions
  82.  
  83. 2.3a ReviveDC IP.BIN logo will be inserted on all releases. Exceptions for games that won't boot with a logo.mr inserted.
  84. logo.mr MD5: d0910006ba71ecff70a7ea214b2c3a05
  85. logo.png MD5: bf6e4d52f97c7bc234f714b519248229
  86.  
  87. 2.3b Disc images will be named as follows: Game.Name.R-RDC.CDI
  88. Where .R is the region of the game, either J, U or E.
  89. Example: Rippin.Riders.U-RDC
  90. If a game is a language specific variant, make note.
  91. Example: Resident.Evil.E.German-RDC
  92.  
  93. 2.3c Images will be 7zipped. Folder hierarchy is as follows: In the main 7zip folder will be the CDI and the NFO titled "readme.nfo." There will be a folder called artwork. Within the folder will be the DVD Sleeve.jpg and a USA White and USA Black folder. Within each the art will be labeled Front, Back, Inlay.
  94.  
  95. Example:
  96. Artwork
  97. NTSC-U Black
  98. Front.JPG
  99. Back.JPG
  100. Inlay.JPG
  101. NTSC-U White
  102. Front.JPG
  103. Back.JPG
  104. Inlay.JPG
  105. DVD Sleeve.JPG
  106. Game.Name-RDC.CDI
  107. readme.nfo
  108.  
  109. 2.3d 7zip will be titled as Game.Name.R-RDC.7z
  110.  
  111. 2.3e ECM will not be used
  112.  
  113. 2.4 Uploads will be titled as followed on the ISO Zone Game Name (Emulator Name if applicable) - ReviveDC Release
  114. Examples:
  115. Sonic Adventure - ReviveDC Release
  116. The King of Fighters '94 (NEO4ALL RC4) - ReviveDC Release
  117.  
  118.  
  119. 2.5 Repacks
  120. If you make a mistake, repack the game. Period. It is the highest priority to have all released games working and working right.
  121.  
  122. 2.6 Game Queue
  123. Absolutely only FIVE games on FTP at a time from any ripper. No exceptions at all. This is going to be a very hard rule. If a ripper goes over 5, the game over the 5th one will be deleted and whatever game it was is up for grabs for anyone. It is the responsibility of the ripper to discuss having the art made with someone. If the game is obscure, art must be provided somehow. It is the ripper's responsibility to update the Google Docs spreadsheet with the art and let others know that a new game is up.
  124.  
  125. The Google Docs Spreadsheet is here:
  126. https://docs.google.com/spreadsheet/ccc?key=0AsnUX5_ux82hdF9fWkt6cm9NZm0yd0MwOE9xZ05NSWc#gid=0
  127. **************************************************************
  128.  
  129. Section 3: Artwork
  130. 3.1 Templates
  131. Do not move aspects of the template. For example, repositioning the Sega logo on the front. If it's that huge of a detriment to the artwork, find a different image. The only aspect of the template that should be repositioned are the rear icons which denote the features of the game (VMU, rumble, etc.).
  132.  
  133. 3.2 Stretching
  134. Artwork should not be NOTICEABLY stretched. It's impossible to avoid in the case of converting CD cases to DVD, but images should not be obviously fatter or thinner.
  135.  
  136. 3.3 Acceptable artwork
  137. Do your best to find original retail images for the game. Avoid fan or original art if possible.
  138.  
  139. 3.4 Resolutions
  140. This is difficult to determine, as some images will enlarge better than others. Find artwork of the highest resolution possible to use. Use personal judgment to determine if an image is of the appropriate quality when enlarged.
  141.  
  142. 3.5 Exporting from Photoshop
  143. Save the image as a JPEG with quality set to 11.
  144.  
  145. 3.6 Trumping artwork
  146. Artwork that appears less stretched, uses official artwork or uses assets of a higher resolution is qualification for trumping the original artwork that went out with a release. The original art will be saved as part of the forum posts. Original art is to be hosted on Mediafire. Photobucket, Tinypic, Imageshack etc. are unacceptable as they resize the image and lower quality.
  147.  
  148. **************************************************************
  149.  
  150. Section 4: Miscellaneous
  151. 4.1 RDC-XXXX Numbers
  152. Every released game will have an RDC-XXXX number. The numbers will replace the original T-XXXX or whatever it may be on the original artwork. If a different region of a game is released, it will have the number of the original game.
  153.  
  154. Example:
  155. If the original release of The House of the Dead 2 is an NTSC-U game with the release number RDC-0010, the PAL release of the game will be RDC-0010 as well. It will go under the same section in the NFO and be noted as different.
  156.  
  157. Furthermore, variations in image length will fall under the same RDC number.
  158.  
  159. Example:
  160. Vampire.Chronicle.for.Matching.Service.99.MIN-RDC and Vampire.Chronicle.for.Matching.Service-RDC both have the same RDC number of 101.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement