Monster Generator Timins (new research) - DMute/DM

[Gambit37]

<pedant>
I've done some timings of monster generator recharge times using FTL PC DM. In DMute, if you view a generator at hex level, you'll see that the 8th byte controls the delay between each monster being generated. DM (and CSB) won't allow a generator to create a new monster until this delay has elapsed, regardless of how many times you might activate the generator.

I built a test dungeon and changed the timing of the generator to different values to see if I could find a pattern. I didn't have a stop watch so could only time these using a clock, which means the timings aren't that accurate.

8th byte= 0 : No delay
8th byte= 10 : ~5 seconds
8th byte= 20 : ~7 seconds
8th byte= 30 : ~9 seconds
8th byte= 40 : ~11 seconds
8th byte= 50 : ~13 seconds
8th byte= 60 : ~15 seconds
8th byte= 70 : ~17 seconds
8th byte= 80 : ~20 seconds
8th byte= 88 : ~2 mins 5 seconds (DMute default)
8th byte= 90 : ~3 mins 50 seconds
8th byte= A0 : ~7 mins 40 seconds

I stopped timing at this point as it was getting very boring... However, you'll notice
there are two patterns here. Using values 10-80 seems to increment the timer by
approximately 2 seconds each . At value 88 things change, and a default time is created (2 mins 5 secs approx). I timed 90 and A0 and discovered a new pattern; that the A0 timer doubled the previous 90 timer. It's therefore logical that if byte 8 is in the range B0-E0, these would be the recharge times:

8th byte= B0 : ~15 mins 20 seconds
8th byte= C0 : ~30 mins 40 seconds
8th byte= D0 : ~61 mins 20 seconds
8th byte= E0 : ~2hr 2 mins 40 seconds
8th byte= F0 : ~4hr 5 mins 20 seconds

This seems ridiculous, but I did try timing F0 and got bored after 17 minutes, so it's
possible the delay really is that high! Has anyone else done any work on this? I would be interested to see what interim times might be. I got quite bored, so perhaps someone else wants to try values such as 38 or A8. Do they fall between the previous and next timer?

The reason for doing all this is to make RTC more accurate. Having looked through the .TXT files it seems the highest recharge time is 250. This equates to about 42 seconds, much lower than the default time for DM/CSB. I don't yet know if that's the highest the recharge timers in RTC can go... I need to test it.
</pedant>