Talk:BYAML (File Format)
Jump to navigation
Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Is there any download link to "yamlconv"? -- Leseratte (talk) 06:15, 26 February 2015 (UTC)
- There wasn't, so I've just released it (with source https://github.com/Chadderz121/yamlconv/releases/tag/v1.0.0).
- Chadderz (talk) 20:16, 26 February 2015 (UTC)
Object IDs
What are the objects that have these IDs?
- 9007
- 7015
- 6009
- 6003
- 1013
Null Type
At Super Mario 3D World, I've found BYAML files with the node type 0xff. The value of them are always 0. I think that this means null, because it's used for the fields "Comment" and "ModelName". (found at TitleDemo00StageMap.byml from /content/StageData/TitleDemo00StageMap1.szs)
Blue yoshi (talk) 08:58, 18 March 2018 (UTC)
- Interesting, and you're sure the node has no data? I tried using yamlconv though the BYML format is different, the Path value table node offset is missing.
--Wexos (Talk | Contribs) – CT/MK8 Wiki Admin 16:48, 19 March 2018 (UTC)
- I used an own (not published) tool to convert the file. The table which describes the header says that "Path value table node" may be 0 if path values are unused. So the file is valid (although a few string values contain special chars). Blue yoshi (talk) 18:15, 19 March 2018 (UTC)
- The file is valid but different. In this documentation the header is 0x14 bytes long and therefor the first offset should be 0x14, but in BYML the header is only 0x10, because the first offset is at 0x10. So the path value table node offset is missing, because the first two offsets (starting at 0x04) link to string tables (0xC2 nodes) and the third to the root node (in this case 0xC1).
--Wexos (Talk | Contribs) – CT/MK8 Wiki Admin 20:10, 19 March 2018 (UTC)
- The file is valid but different. In this documentation the header is 0x14 bytes long and therefor the first offset should be 0x14, but in BYML the header is only 0x10, because the first offset is at 0x10. So the path value table node offset is missing, because the first two offsets (starting at 0x04) link to string tables (0xC2 nodes) and the third to the root node (in this case 0xC1).
- You're right (and I was wrong). I didn't realized that because I didn't added decoding paths yet. Looks like it's another type of byaml which is very similar. So I would suggest to document that if an offset is 0x10, then there are no paths. Additionally, I want to ask if I can/ should add to the table that the type 0xff with the value 0 is eventually null with a link to the discussion page. Blue yoshi (talk) 15:41, 20 March 2018 (UTC)
- Sure, just add 0xFF to the node type table.
--Wexos (Talk | Contribs) – CT/MK8 Wiki Admin 17:42, 22 March 2018 (UTC)
- Sure, just add 0xFF to the node type table.