Advertisement
Doesnt

nightmare format

Jun 30th, 2015
300
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.93 KB | None | 0 0
  1. NIGHTMARE MODULE FORMAT
  2. -----------------------
  3. Blank lines are ignored, so you can use them to divide stuff up and make it
  4. more readable.
  5.  
  6. Lines beginning with # are comments.
  7.  
  8. Numbers are assumed to be decimal; to indicate hex, include a "0x" prefix.
  9. You can even indicate octal with a "0" prefix, if you're so inclined. :D
  10.  
  11. All numeric values can be decimal or hex interchangably, with the exception
  12. of table files - the values there are assumed to be hex. (This allows
  13. copying and pasting from existing table files.)
  14.  
  15.  
  16.  
  17. THE MODULE FORMAT
  18. -----------------
  19. The first line holds the module file version. For this file, that's "1".
  20. No decimal points or anything fancy.
  21. The second line is the module description, which appears on the title
  22. bar when the module is loaded.
  23. The third line is the root address of the data table.
  24. The fourth line is the number of table entries.
  25. The fifth line is the length of a single entry.
  26. The sixth line is a filename, indicating a list of names to be used by
  27. the entry selector. If "NULL", the entry selector will only use
  28. numbers. If names run out before numbers do, the selector will continue
  29. with just numbers.
  30. The seventh line is also a filename, indicating the table file to be used
  31. by TEXT entries. Tables here can only be letter-matching, that is, of
  32. the form XX=Y; multiple bytes or multiple characters, such as XXYY=Z,
  33. or XX=yz, are not permitted. If "NULL", standard ASCII is assumed.
  34.  
  35. Here follow entry-component handlers, until the end of the file.
  36.  
  37. It is recommended (for reasons of readability by humans) that a newline
  38. be placed here, and also after each entry-component handler.
  39.  
  40.  
  41.  
  42. ENTRY-COMPONENT HANDLER FORMAT
  43. ------------------------------
  44. The first line contains a textual description.
  45. The second line contains the offset from the start of the entry.
  46. The third line contains the number of bytes used by the component.
  47. The fourth line indicates type, which is one of the following:
  48.  
  49. TEXT - Text editbox
  50. HEXA - Hex array (useful for indicating and changing unknowns)
  51. NEHU - Numeric editbox, hex unsigned
  52. NEDS - Numeric editbox, decimal signed
  53. NEDU - Numeric editbox, decimal unsigned
  54. NDHU - Numeric dropbox, hex unsigned
  55. NDDU - Numeric dropbox, decimal unsigned
  56.  
  57. Binary toggles should use NEHU with something like "(binary)" in their
  58. description, and an explanation in comments within the module file.
  59. Types are not case-sensitive.
  60.  
  61. The fifth line is the parameter file, a name list for dropboxes. It
  62. follows this format:
  63.  
  64. <number of entries to follow>
  65. <numeric value> <written description>
  66. <numeric value> <written description>
  67. ...
  68. <numeric value> <written description>
  69.  
  70. The numeric value is displayed in the context specified by Type
  71. (hex or decimal, for example). This value is what is written to the
  72. rom when a dropbox entry is selected and Save is used. This parameter
  73. is unused ("NULL") for editboxes.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement