Hourglass behaviour

The problem

According to the Logical Manuals, the duration a level can be played before reaching a TIMEOUT is determined by multiplying the inputted value (ranging from 1 to 10) by 1.5. We’ll refer to this 1.5-minute interval as an “hourglass cycle.” Therefore, the number of cycles the hourglass completes should match the inputted value. However, during gameplay, you may observe that these values are inaccurate. In reality, the actual number of cycles completed is equal to the inputted value plus 1.

Green for manual value, blue for actual value:

xychart-beta
    title "Times according to manual"
    x-axis "Input" 1 --> 10
    y-axis "Time (in cycles)" 0 --> 10
    bar "actual" [2, 3, 4, 5, 6, 7, 8, 9, 10, 10]
    bar "manual" [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]

Loading

The proposed solution is to rely on the actual values rather than following the manual. However, there’s a complication: in the editor, you can add more than one hourglass tile, which further distorts the values during gameplay. As I don't have the knowledge needed to make a decompilation, I (for now) will resort to timing instead.

Italics are assumptions, blanks are not yet calculated, h is amount of hourglasses, c is the amount of cycles, and the hex code is the file value:

	1h	2h	3h	4h	5h	6h	7h	8h	9h
0x01	2c	1c	1c						1c
0x02	3c	1c
0x03	4c	1c
0x04	5c	1c
0x05	6c	2c	1c
0x06	7c	4c	1c
0x07	8c	6c	4c	2c	1c
0x08	9c							2c	1c
0x09	10c							2c	1c
0x0A	10c	10c							10c