Halby hits every 2 seconds with 25 dex?

[Vlastslav]

Yah I read the entire thing, the links in my original post. Seems as if the 2sec hit was implemented then fixed in several patch notes... the main reason why I posted this thread is to see why it is still in on UOSA.

[Senses]

Faust in another thread:
"Having a hally hit every 2 seconds without this is beyond stupidity though."

I'm kind of a UO newbie and I can't remember shit from that time but I just think its funny that on one hand, in a thread about weapon speeds, hally hits every 2 seconds is beyond stupid, but here, in a thread about instant hits, not having hally hits every 2 seconds is beyond stupid.

[Fwerp]

I have to side with Vlast on this one, the hally timer seems very, very hyper. The 3 seconds or so on live UOSA seems too fast to me =\.

[Kraarug]

I don’t see a 2 second hally whack, even at 100 stamina. What am I doing wrong?


FORMULA: Attack Speed= 15,000 ÷ ( [Stamina +100] x Weapon Speed )
Contants 15000 100

Speed Stamina 25 Stamina Attack Speed Stamina 100 Stamina Attack Speed
Hally 25 25 4.8 100 3.0
Q stave 48 25 2.5 100 1.6
Kryss 53 25 2.3 100 1.4
Kat 58 25 2.1 100 1.3
War Axe 40 25 3.0 100 1.9

[MatronDeWinter]

I don’t see a 2 second hally whack, even at 100 stamina. What am I doing wrong?


FORMULA: Attack Speed= 15,000 ÷ ( [Stamina +100] x Weapon Speed )
Contants 15000 100

Speed Stamina 25 Stamina Attack Speed Stamina 100 Stamina Attack Speed
Hally 25 25 4.8 100 3.0
Q stave 48 25 2.5 100 1.6
Kryss 53 25 2.3 100 1.4
Kat 58 25 2.1 100 1.3
War Axe 40 25 3.0 100 1.9

Watch how others do it closely, they all have something in common. Also T2A wiki has info on the insta-hit

[Faust]

Faust in another thread:
"Having a hally hit every 2 seconds without this is beyond stupidity though."

I'm kind of a UO newbie and I can't remember shit from that time but I just think its funny that on one hand, in a thread about weapon speeds, hally hits every 2 seconds is beyond stupid, but here, in a thread about instant hits, not having hally hits every 2 seconds is beyond stupid.

If you actually paid any attention in the other thread you wouldn't have made yourself look stupid in this thread. The topic in the other post talks about the swing timer ticking down while on the move. There is CLEARLY a difference between having to "stop" and "wait" for 2 seconds compared to "moving" and receiving it. Have you not followed this topic at all during this thread before responding? Take a look at Jiggo's response where he mentions spell casting involving this function. Most players during this time period used spell casting as a measurement tool for an insta hit refresh. Did spell casting receive the ability to move while casting?

Yah I read the entire thing, the links in my original post. Seems as if the 2sec hit was implemented then fixed in several patch notes... the main reason why I posted this thread is to see why it is still in on UOSA.

Umm, okay? Where was it fixed in several patch notes? This part of your response is well beyond me... It is still here because this is a t2a shard that is replicating that era including this feature of that particular era.

I don’t see a 2 second hally whack, even at 100 stamina. What am I doing wrong?

Cycle your weapon.

I have explained it in full detail in the thread that discusses the feature. If you follow that you should have no problem figuring it out.

All weapons still obey the standard timer. However, this can be manipulated by the two second unequip delay. Weapons both have an equip and unequip delay. The equip delay was implemented in '97, and the unequip delay was added in early '99 to fix an exploit. The insta hit patch removed the equip delay when your swing was ready. This created an exploit that allowed people to cycle hallies even quicker than 2 seconds. A hally could hit as fast as a katana at one point very briefly. OSI decided to add a moderate unequip delay of 2 seconds to fix this exploit. This brought about the insta hit refresh bug where you could cycle a hally to override a current swing delay.

[Kraarug]

I don’t see a 2 second hally whack, even at 100 stamina. What am I doing wrong?


FORMULA: Attack Speed= 15,000 ÷ ( [Stamina +100] x Weapon Speed )
Contants 15000 100

Speed Stamina 25 Stamina Attack Speed Stamina 100 Stamina Attack Speed
Hally 25 25 4.8 100 3.0
Q stave 48 25 2.5 100 1.6
Kryss 53 25 2.3 100 1.4
Kat 58 25 2.1 100 1.3
War Axe 40 25 3.0 100 1.9

Watch how others do it closely, they all have something in common. Also T2A wiki has info on the insta-hit

I'm pretty clear on how 'insta-hit' works.

Here's a quote from the wiki:

Pre T2a weapon animations could actually be outrun. This means you could literally time to run away when someone was swinging a weapon at you. In T2a weapon hits would "instantly hit" eliminating the ability to dodge an attack. Weapons now have timers determining how fast one can swing a weapon. Bigger, more powerful weapons such as 2 Handed Weapons took longer to swing. This gave birth to a new fighting system. One which lower Dexterity characters, such as Mages, could utilize bigger weapons without waiting for a weapon timer to reload.

After a swing the weapon timer would start. Even with the weapon unequipped the timer continues going. This allows characters to unequip the weapon and do other actions such as spell casting or drinking potions while they wait for their weapons to be ready. This gave birth to a new fighting style. Mages would focus on high Strength and Intelligence and take the minimum 25 Dexterity. Even with this low Dexterity, Mages could cast spells in between weapon hits with their large 2 Handed Weapons.

http://wiki.uosecondage.com/index.php?title=Insta_Hit

That doesn't talk about excellerating the swing timer. The math, as provided, shows a minimum attack speed of 4.8 seconds for 25 stamina and 3.0 seconds for 100 stamina. My question is where does a 2 second or any swing faster than 4.8 seconds at 25 stamina come from.

Insta-hit is basically the fact a swing is attempted before the animation and, from what is quoted above, the swing timer cools over time weather it's equiped or not (just not if the user is moving.)

So, a person could swing, unequip to cast to wait out their swing timer refresh, and then equip for another insta-hit. Where's the excelleration?

[Faust]

Read the bottom portion of my last response Cortez.

[RAAAAAAAAAAAAAAAR]

You know that to counter the 2 second hally whack all you have to do is maintain adjacent position to the target and spam attack last.

Secondly why would WTF man post a forged screen shot, you think there against us being T2A accurate or something, it is a ludicrous assumption.

Thirdly if people remember spell refresh and this creates spell refresh then why would you change it?

[Jaster]

[17:13] <Faust> that's the only reference to the disarm delay
[17:13] <Faust> is the one on stratics
[17:13] <Faust> saying it's 2 seconds

so, what do we know from memory?

A 6th circle spell refreshed a hally hit [1.75s cast]
2 Harms refreshed a hally hit [.75s per]

Add in recovery delay if those spells are not being fast casted ....
.75s recovery delay on UOSA

1 ebolt [1.75s + .75s recovery delay = 2.5s]
2 harms [.75*2 + .75s recovery delay = 2.25s]

But ...

[17:13] <Faust> that's the only reference to the disarm delay
[17:13] <Faust> is the one on stratics
[17:13] <Faust> saying it's 2 seconds

So what is correct?

Stratics that says 2 seconds?
6th Circle spell + delay = 2.5s?
2 harms + delay = 2.25s?

shall we add in a 200ping from dial up ... add another .2s on to that

lets also add in the fact that no one stood toe to toe in t2a and there was a distance to travel to get to someone.

IMO, something isn't correct ... prove me wrong

[RAAAAAAAAAAAAAAAR]

[17:13] <Faust> that's the only reference to the disarm delay
[17:13] <Faust> is the one on stratics
[17:13] <Faust> saying it's 2 seconds

so, what do we know from memory?

A 6th circle spell refreshed a hally hit [1.75s cast]
2 Harms refreshed a hally hit [.75s per]

Add in recovery delay if those spells are not being fast casted ....
.75s recovery delay on UOSA

1 ebolt [1.75s + .75s recovery delay = 2.5s]
2 harms [.75*2 + .75s recovery delay = 2.25s]

But ...

[17:13] <Faust> that's the only reference to the disarm delay
[17:13] <Faust> is the one on stratics
[17:13] <Faust> saying it's 2 seconds

So what is correct?

Stratics that says 2 seconds?
6th Circle spell + delay = 2.5s?
2 harms + delay = 2.25s?

shall we add in a 200ping from dial up ... add another .2s on to that

lets also add in the fact that no one stood toe to toe in t2a and there was a distance to travel to get to someone.

IMO, something isn't correct ... prove me wrong

So you're saying it could of been 2.5 seconds then, but even then we would go with the stratics evidence wouldn't we, anyways you are the ones who need to find evidence to prove it is incorrect since Faust already states enough evidence to deem the refresh a suitable fix and get it implemented, it is certainly better than the default.

I would say it would be unreasonable to doubt it at this point in time

But keep on debating maybe something good will come forth.

[Fwerp]

Heh, I will just say again that I think the halberd timers are way too fast, and that the screen shot proves nothing at all in my mind. I will go so far as to say it is utterly devoid of any significance. I also agree with Loops that stratics is a very questionable source, because of the inconsistencies and such.

What is the hally timer in the demo? This should be pretty easy to figure out, and getting 45 str to use the halberd shouldn't be too cumbersome.

[Faust]

I find it funny how you leave out the rest. How about we feel in some holes?

Who says these spells wasn't fast casted? I did plenty of refreshes with fast casting. The source suggests that the delay is 2 seconds and that's the ONLY source to go by. It works out just fine with the way it's setup to re-create the function.

The comment referring to standing toe to toe is completely pointless...

Your swing timer doesn't advance while moving, so the time spent moving from your opponent after refreshing bares nothing to the timer. Also, if you did happen to elapse le'ts say 1.75s from an ebolt and moved to your opponent equipping a weapon while moving that the delay wouldn't have subsided resulting in the equip delay resetting your timer? The argument in regard to moving has so many holes in it.

The facts remain the same on this topic. It has been proven without a doubt with the mounting evidence that you could skip a hally delay. The only logical explanation for this is the two disarm delay. I guess it's just one BIG coincidence that this feature re-creates this function EXACTLY the way that it works...

The default RunUO code uses a disarm delay that converts your timer, but it uses the weapon's delay instead of a two second delay. Bare in mind that the default code is a replica of modern day UO. Now we have an article in stratics that CLEARLY states that the disarm delay is 2 seconds long.

public override void OnRemoved( object parent )
{
if ( parent is Mobile )
{
Mobile m = (Mobile)parent;
BaseWeapon weapon = m.Weapon as BaseWeapon;

if ( weapon != null )
m.NextCombatTime = DateTime.Now + weapon.GetDelay( m );
}
}

Default code with the highlighted line that shows the disarm delay. Stratics tells you that delay was in fact 2 seconds long as stated above.

Enough said.

[Fwerp]

The facts remain the same on this topic. It has been proven without a doubt with the mounting evidence that you could skip a hally delay. The only logical explanation for this is the two disarm delay. I guess it's just one BIG coincidence that this feature re-creates this function EXACTLY the way that it works...

Faust, your saying that it has been proven doesn't make it so, and that is not the only "logical explanation."

Also, there has not been "enough said." There remains huge disagreement about this, and you've adduced the scantiest of evidence in support of your thesis. Arguing through rhetoric is not at all convincing, sir.

[Faust]

I told Fruit Loops that I am all ears for another "logical explanation".