Welp. CHR 13 becomes CHR 10 in files.

I agree that the CHR$(13) replacement was a bad choice, and I hope they fix it. However, from my experience, things like this usually don't get fixed, so we might just have to deal with it. Now, you can always convert the file to be saved as a DAT file. Just store the ASC of each character into an array, and save it. You could also store 2 characters in each array element (of an integer array), or 4 if you're just using characters less than 256 (extended ascii)

I figured out a simple way to avoid this issue, specifically for my String Mapping.

I figured out a simple way to avoid this issue, specifically for my String Mapping.

How nice for you.

I figured out a simple way to avoid this issue, specifically for my String Mapping.

Not gonna tell us then?

He adds 14 to each number when saving, then subtracts when loading.

so maximum number -14 is the new maximum value?

so maximum number -14 is the new maximum value?

Yeah. He's using it for saving BG maps, which works fine since BG only goes up to 1023 without rotations or flipping.