Halkun's post reminded me. I was going to post to see if anyone can shed any light on repeated script offsets. Here's one from uutai1, the entity is savel0:

Now, as far as I have it down, the multiple 0x1607 means that there's no actual script for these offsets where the offset is repeated. But as you'll see, rather than continue to the end of the 32 offsets, further on down the row the offset does change and all of a sudden we have new scripts after 4 repeats of 0x1607. So, ignoring these, I read the script as:
Script 1: Init
LINE (79,FD,5A,04,00,00,D7,FD,6C,04,00,00)
RET ()
RET ()
--
Script 2:
RET ()
--
Script 3:
Sound (00,67,01,40)
IfUByte (D0,5B,01,0A,16)
UC (01)
MENU2 (01)
window (00,3E,00,0A,00,B4,00,39,00)
message (00,15)
UC (00)
MENU2 (00)
BIT-ON (D0,5B,01)
SET-WORD (20,1E,00,00)
RET ()
--
Script 4:
BIT-OFF (D0,5B,01)
SET-WORD (20,1E,00,02)
OR2 (20,1E,00,01)
RET ()
So I reduced the repeated offsets to just one to see if it had any effect. Visually there were no problems with the save point, but actually going to use it caused some unusual behaviour, notably that moving through the save point repeatedly brings up the Save dialog (Access the menu and select... etc.) instead of it just appearing once until you leave and go back in (quite difficult to get out of the save point), and it also becomes difficult to get Save enabled in the menu (you seem to have to go to an exact point rather than just generally on the object).
So it would seem the repeats would be necessary; how does this affect the reading in of the script? What should the above script output really read when there are these repeats? I'm beginning to think I shouldn't have that second script, the single RET() there, but then what's the point in having these repeats? Any help is appreciated.