Sample Game 1 PAK: Difference between revisions
Jump to navigation
Jump to search
imported>Dinoguy1000 No edit summary |
imported>Dinoguy1000 No edit summary |
||
| Line 107: | Line 107: | ||
<!-- | <!-- | ||
Each game listed here should link to its own page. Before you do this, be absolutely sure that the game title is spelled correctly, etc. Also, each extension used by the given game for that format should link to its own page, as seen above. | Each game listed here should link to its own page. If a game is for a non-PC platform, it should have the platform it's for in parenthesis following the game name, e.g. [[Sample Game 1 (PS2)]] or [[Sample Game 1 (Gamecube)]]. Before you do this, be absolutely sure that the game title is spelled correctly, etc. Also, each extension used by the given game for that format should link to its own page, as seen above. | ||
--> | --> | ||
| Line 119: | Line 119: | ||
Keep in mind that all category tags should include the line {{subst:PAGENAME}} after the pipe character (|), e.g. [[Category:Category|{{subst:PAGENAME}}]]. After a page is saved, the WIKI automatically replaces this line with the page's name. In general, category tags should take the form [[Category:Cat Name Here|{{subst:PAGENAME}}]] | Keep in mind that all category tags should include the line {{subst:PAGENAME}} after the pipe character (|), e.g. [[Category:Category|{{subst:PAGENAME}}]]. After a page is saved, the WIKI automatically replaces this line with the page's name. In general, category tags should take the form [[Category:Cat Name Here|{{subst:PAGENAME}}]] | ||
The specification completion categories are fairly straightforward to use. If most of a file's format is unknown (and chances are therefore | The specification completion categories are fairly straightforward to use. If most of a file's format is unknown (and chances are therefore good that it can't be supported by MexCom), one should use the category Complete WIP, indicating that the format is a work in progress. If the format is reasonably complete (few unknown values), you should use the category Complete Almost Done, and if the format is completely known, you should use Complete Complete. | ||
More | As for BMS scripts, there are only two things you should worry about: if there's no BMS script for a given format, you should have used the template {{NoBMSScript}}, and the appropriate category is added automatically. If you added a new script for a given format, you should add the category BMS New to the end of the page. | ||
Moving on to platforms a given format is used on, in general, category names take the form of Platform *platform name*, e.g. Platform PC or Platform PS2. A full list of appropriate categories follows: | |||
Platform 3DO | |||
Platform PC | |||
Platform XBox | |||
Platform XBox 360 | |||
Platform Gamecube | |||
Platform Dreamcast | |||
Platform PS1 | |||
Platform PS2 | |||
Platform PS3 | |||
Platform PSP | |||
More categories will be added as needed. | |||
When adding platform categories, just use all of them that apply. For instance, if a format I was working on was used on the PC and the Gamecube, I would use the categories Platform PC and Platform Gamecube. | |||
Finally, the categories for compression and encryption are quite simple. Most of the time, the format you're working on won't use compression or encryption, so you should use the category CE None. If it uses unknown compression/encryption, you'll want to use the category CE Unknown. If you know for sure that a givn format uses compression, use the category CE Compressed, and similarly, CE Encrypted for encryption. If a format uses both compression and encryption, skip the individual CE Compressed/CE Encrypted categories and just use CE Both. | |||
--> | --> | ||
Revision as of 17:36, 22 January 2007
Back to index | Edit this page
NOTE: This is only an example of a GRAF page. As far as I know, there is no game called "Sample Game 1", and no game uses the exact archive format given below.
PAK
- Format type: Archive
- Endianness: Little-endian
Format Specifications
char {15} - Header (Sample Game PAK)
byte {1} - null Padding
// For each file
- char {16} - File name (null padded)
- uint32 {4} - File size
- byte {x} - File data
Notes and Comments
None
MultiEx BMS Script
None written yet.
Supported by Programs
Unknown
Links
None