2
<p>IT WORKS! I have DAT2 now! </p><p>lets see how it breaks when we try DAT3...</p>
<p>ALRIGHT HERE&#39;S WHAT WE&#39;RE DOING. WE&#39;RE DOING IT LIVE.</p><p>loadChunk is gonna fail. Fine.<br />We ignore it, then call load_dat_file on the correct dat, then we call loadChunk again! </p><p>This is stupid, but it means I don&#39;t have to move the fucking start position!</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> they probably had a rush of adware proposed to approval, so they put the warning upfront 😂</p>
<p>my code starts right AFTER the chunk is loaded. I&#39;d have to move it. MOTHERFUCKER</p>
<p>yep, changing it to DAT2 breaks it. I can&#39;t swap DAT2 into the place of DAT1, because it does indeed need other chunks from it.</p><p>UGH.</p><p>maybe I can just add my own call to load_dat_file at the top of my assembly. I do NOT want to have to relocate it, that sounds like it&#39;d be REALLY FUCKING HARD</p>
<p>Updated: it was already a rule as it turns out, but now far more visible. Added a note to the top.</p>
<p>I should do this to Carmen when I get back to that project. Then instead of understanding it&#39;s compression, I just bypass it completely</p>
<p>I can&#39;t just extract them all to the same folder, because there&#39;s duplicates. possibly different duplicates!</p>
<p>... they put BIB100.MUS in DAT1 and DAT2.</p><p>MOTHERFUCKER</p>