[Next Message in Time] | [Previous Message in Time] | [Next Message in Topic] | [Previous Message in Topic]

Message ID: 743
Date: Sat May 15 13:13:08 BST 1999
Author: John Kim
Subject: Re: Ack! These songs do nothing TOO!?


Ok, I retested this. Slightly different results, and some
possible explanations. Here's a recap of what I found last
time.

On Wed, 12 May 1999, John Kim wrote:
>
> I just timed this last night. With a combine longsword (delay
> 28), I swing 5 times in roughly 14.0 seconds. This is
> consistent with my previous findings that the weapon delay is
> just the recycle time in tenths of seconds (so 28 delay means
> 2.8 seconds between swings).

No change here. No song, 28 seconds to swing 10 times. (I
checked all of these with a stopwatch three times.)

> With only the whistling warsong playing, it dropped to about
> 12.5 seconds, or about 25 delay (so my combine longsword is
> working like a well-balanced longsword :-). Roughly a 10%
> speedup (my bard is L15).

This dropped to 23.7-23.9 sec for 10 swings, or about a 24
delay. My singing skill was maxed when I tested it the first
time, so the only difference I can think of was that my bard
was about level 15.6 the second time, compared to 15.2 the
first.

> With only the anthem playing, it
> was about 12.5 seconds, maybe 13.0 seconds (my stopwatch
> results for this one had about a half second of scatter). So
> again the speedup is about 10%, maybe a hair slower than the
> warsong.

No change here.

1) Jonathan's Whistling Warsong definitely does speed up your
attacks. Enough so that it's obvious to me just watching it,
even without a stopwatch. The speedup seems to be dependent
on level, or both level and skill (or maybe it's charisma?
:-).

2) I've noticed with all my characters that they seem to have
an easier time fighting in the second half of a level than in
the first. The difference in the above timings support this.
It's possible that some calculations are made based on the
your exact level (e.g. 15.4) instead of just the integer
portion.

--
John H. Kim
kim@...