See Comment, I do not believe that we should just be reading a single byte, but an entire IffData repeating element, and there are 31 null() calls that need to be fixed.

Thanks @treybgreen you've given me reason to pause and check the spec.

If I'm reading it right, it's the IFF Data Specification record that contains one or more IFF data records.

It's one that has a null() too.

For IFF data, I'm seeing an issue with the code when I read the spec. The record length isn't for the data portion of the record, it's for the whole record including the type, length, data and padding.

There are more nulls to fix, but the nulls fixed in this PR are still useful so I'm going to merge this as is since I've been busy and not sure when I will get back to fixing the rest.