Jedi Archive

Message Edited by Taliesyn42 on 08-05-2005 10:05 PM

---

Taliesyn42 wrote:

Ok, I've been doing some testing, and I think I know what is going on here. First off, there's a bug that most people have assumed is the saber crystal bug, when it's not. In a nutshell, right now, general melee speed and lightsaber speed are worthless to us. Here's why:

First off, some basics. When you make an attack, the cooldown of the skill you used for the attack (call it Primary Cooldown) is equal to 1.5 times your effective speed on that weapon, further modified by buffs such as from a doctor or Force Speed. The cooldown for the OTHER specials you have (call it Secondary Cooldown) is EQUAL to your effective attack speed, modified as above.

For specialist professions, such as pistoleer or Lightsaber Jedi, this effective speed is MUCH lower than the base speed due to general and weapon-specific speed skills. The difference between BASE speed and EFFECTIVE speed is 100% based on these two speed skills, including modifiers from CA's/AA's.

My observations and testing show that for lightsabers, for whatever reason, the game calculates Secondary Cooldown based on your weapon's BASE speed rather than the EFFECTIVE speed for all attacks other than Saber Hit.

This is tested easily enough. First, make sure you have NO buffs up. Reload your saber so that you undo the crystal bug. Now use a stopwatch to time the secondary cooldown after activating a saber hit. Your result will be very near your listed effective speed. Now for the more easily tracked part: Do a cycle of 5 head hits and 5 leg hits, alternating between the two. Check your combat logs for the time stamps afterward. You'll note that the 10-attack cycle requires ten times your BASE attack speed to complete, give or take lag time. (It's best to do 6 of the first and 5 of the second, just to give an initial hit you can time from.)

THIS is the bug I'm talking about. It's not the crystal bug, where your crystals' speed stats aren't actually applied to your saber. It doesn't involve using the same attack over and over. This has nothing to do with buffs - THEY work properly. The issue is that your inherent general melee and lightsaber speeds are not being used when you attack. This would ALSO explain why speed CA's are not working for jedi - another bug people know about. This is the bug that CAUSES that effect.

As a database developer myself, if I had to guess, I'd say that somewhere in the code, some programmer copied and pasted the wrong variable (WeaponBaseSpeed instead of WeaponEffectiveSpeed) into the cooldown calculations for every lightsaber attack other than Saber Hit. With that in play, speed-based CA's become worthless, and it explains why even master saber wielders cannot attack faster than once every two seconds.

Hopefully this will get forwarded to the devs and fixed, as it could well be a VERY easy fix to make.

---

---

Taliesyn42 wrote:

Ok, I've been doing some testing, and I think I know what is going on here. First off, there's a bug that most people have assumed is the saber crystal bug, when it's not. In a nutshell, right now, general melee speed and lightsaber speed are worthless to us. Here's why:

First off, some basics. When you make an attack, the cooldown of the skill you used for the attack (call it Primary Cooldown) is equal to 1.5 times your effective speed on that weapon, further modified by buffs such as from a doctor or Force Speed. The cooldown for the OTHER specials you have (call it Secondary Cooldown) is EQUAL to your effective attack speed, modified as above.

For specialist professions, such as pistoleer or Lightsaber Jedi, this effective speed is MUCH lower than the base speed due to general and weapon-specific speed skills. The difference between BASE speed and EFFECTIVE speed is 100% based on these two speed skills, including modifiers from CA's/AA's.

My observations and testing show that for lightsabers, for whatever reason, the game calculates Secondary Cooldown based on your weapon's BASE speed rather than the EFFECTIVE speed for all attacks other than Saber Hit.

This is tested easily enough. First, make sure you have NO buffs up. Reload your saber so that you undo the crystal bug. Now use a stopwatch to time the secondary cooldown after activating a saber hit. Your result will be very near your listed effective speed. Now for the more easily tracked part: Do a cycle of 5 head hits and 5 leg hits, alternating between the two. Check your combat logs for the time stamps afterward. You'll note that the 10-attack cycle requires ten times your BASE attack speed to complete, give or take lag time. (It's best to do 6 of the first and 5 of the second, just to give an initial hit you can time from.)

THIS is the bug I'm talking about. It's not the crystal bug, where your crystals' speed stats aren't actually applied to your saber. It doesn't involve using the same attack over and over. This has nothing to do with buffs - THEY work properly. The issue is that your inherent general melee and lightsaber speeds are not being used when you attack. This would ALSO explain why speed CA's are not working for jedi - another bug people know about. This is the bug that CAUSES that effect.

As a database developer myself, if I had to guess, I'd say that somewhere in the code, some programmer copied and pasted the wrong variable (WeaponBaseSpeed instead of WeaponEffectiveSpeed) into the cooldown calculations for every lightsaber attack other than Saber Hit. With that in play, speed-based CA's become worthless, and it explains why even master saber wielders cannot attack faster than once every two seconds.

Hopefully this will get forwarded to the devs and fixed, as it could well be a VERY easy fix to make.

---

Bravo indeed...and you even explained it in a way that n0bs like myself can understand

maybe you should PM the Jedi Corr.

/doh!

I hope this gets fixed.

eerr....gotta test that myself, hope i got it right, but woulnd that be something they should have found out already? why do they decrease force speed then? i dont get it, for sure they have testers, didnt those testers recognize that the speed is too slow?

one more thing, did u test this for other profs too or just jedi?

Ba---daa---BUMP

yo yo!! Look at the brain on Brad!~!

seriously -- nice job!

---

duurron wrote:

eerr....gotta test that myself, hope i got it right, but woulnd that be something they should have found out already? why do they decrease force speed then? i dont get it, for sure they have testers, didnt those testers recognize that the speed is too slow?

one more thing, did u test this for other profs too or just jedi?

---