[DiscordArchive] i think i just understand what you're doing, you're collecting all the offsets, sort them and then c
[DiscordArchive] i think i just understand what you're doing, you're collecting all the offsets, sort them and then c
Archived author: <o> • Posted: 2022-11-02T10:45:25.748000+00:00
Original source
i think i just understand what you're doing, you're collecting all the offsets, sort them and then chop the string block up?
Archived author: Rymercyble • Posted: 2022-11-02T10:45:48.570000+00:00
Original source
yes
Archived author: <o> • Posted: 2022-11-02T10:46:03.715000+00:00
Original source
that would _probably_ work with most blizzard dbcs, but the file format doesn't guarantee it
Archived author: Rymercyble • Posted: 2022-11-02T10:47:38.817000+00:00
Original source
i mean if some string is at offset 4 and other string at offset 20 but actually first string ends at 16 and 17 18 19 is empty thats straight up just error....i cant think of any other issue with approach im using
Archived author: <o> • Posted: 2022-11-02T10:48:48.182000+00:00
Original source
it's not necessarily an error, you can do that for alignment purposes in some tables, but blizzard files have plenty of errors in them as well
Archived author: <o> • Posted: 2022-11-02T10:49:16.327000+00:00
Original source
though i don't think any table actually does that, at least i can't think of any. maybe in wdc+
Archived author: <o> • Posted: 2022-11-02T10:50:36.918000+00:00
Original source
generally, many things from blizzard will cause undefined behavior when you make assumptions about well-formatted data, but you can just test what you have now and make sure