SHARE
TWEET

bn6f data/ coverage.

luckytyphlosion Mar 24th, 2019 135 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. dat00.s - some graphics stuff, pt_801EF84 is related to battle phrases that appear in the center of the screen (e.g. "ENEMY DELETED")
  2. dat01.s - some of it is battle stuff, some of it is unknown
  3. dat03.s - map script/map related stuff (end of asm03_2.s)
  4. dat04.s - map script/map related stuff (asm04.s)
  5. dat05.s - map script/map related stuff (asm05.s)
  6. dat06.s - map script/map related stuff (asm06.s)
  7. dat07.s - map script/map related stuff (asm07.s)
  8. dat08.s - map script/map related stuff (asm08.s)
  9. dat09.s - map script/map related stuff (asm09.s)
  10. asm10.s - map script/map related stuff (contains two maps and includes data for first map in file)
  11. dat10.s - map script/map related stuff (map data for 2nd map in asm10.s)
  12. asm11.s - map script/map related stuff (contains four maps, includes data for first three maps in file)
  13. dat11.s - map script/map related stuff (map data for 4th map in asm11.s)
  14. dat12.s - map script/map related stuff (asm12.s)
  15. dat13.s - map script/map related stuff (asm13.s)
  16. asm14.s - map script/map related stuff (contains one map, but partially includes data because IDA detected an inline asm function in map script)
  17. dat14.s - map script/map related stuff (rest of data for asm14.s)
  18. dat15.s - map script/map related stuff (asm15.s)
  19. dat16.s - map script/map related stuff (asm16.s)
  20. dat17.s - map script/map related stuff (asm17.s)
  21. dat18.s - map script/map related stuff (asm18.s)
  22. dat19.s - map script/map related stuff (asm19.s)
  23. dat20.s - map script/map related stuff (asm20.s)
  24. dat21.s - unsure. this looks like a map script (data looks very uneven), but I can't find a reference to it. perhaps it was removed data? also, there are a few inline functions in it as well
  25. dat22.s - more unknown bytecode? again, doesn't seem to be referenced.
  26. asm23.s - even more unknown bytecode! first third of the file is mostly data, rest of file are functions that are only referenced inside the file?
  27. dat23.s - more unknown bytecode
  28. asm24.s - more unknown bytecode, mixed with code
  29. dat24.s - more unknown bytecode
  30. dat25.s - more unknown bytecode. also, asm25.s only has three nonlocal functions
  31. dat26.s - more unknown bytecode, mixed in with asm
  32. dat27.s - more unknown bytecode
  33. dat28.s - mystery data is defined here, maybe some other unknown structs
  34. dat29.s - unknown single struct? not sure how it's accessed, but IDA thinks it's a byte array
  35. dat30.s - random encounter data
  36. dat31.s - (fake data)
  37. dat32.s - some structs. pointed to by the table at pt_8121200, indexed by getPETNaviSelect. format of pt_8121200 is table of pointers, with these pointers pointing to a single pointer, with that pointer pointing to a table of pointers, with these pointers pointing to an unknown struct terminated by -1. also, some fake data (asm) here.
  38. dat33.s - (fake data)
  39. dat34.s - (fake data)
  40. dat35.s - (fake data)
  41. dat36.s - unknown, first half sort of looks like bytecode but it probably isn't, second half looks like a consistent struct
  42. dat37.s - rodata for libraries
  43. dat38_0.s - fake pointer, FIXME
  44. dat38_5.s - not included in the build (oops)
  45. dat38_30.s - sprites
  46. dat38_31.s - sprites, fakepointers: byte_8340031, byte_8340901
  47. dat38_32.s - sprites, fakepointers: byte_835083F, byte_8370817
  48. dat38_33.s - sprites, unmarked sprite pointers: byte_83971C0, byte_8398048, fakepointers: byte_83C0710, byte_83C0716, (more but will find them later)
  49. from here on, not checking for fakepointers
  50. dat38_34.s - sprites
  51. (stopped for now, most of this is probably sprites, chatbox scripts, gfx, or some other bulk data)
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Top