Attack last and tabbing

[Hemperor]

As always Valerhu, you are incorrect. The current system now is anything but accurate, no one will dispute this, the system on the demo is accurate until proven otherwise...which will not happen of course.

[Faust]

Hemperor does make one good point about the demo...

It is a more reliable source than the core distro package that comes with RunUO until proven otherwise. However, his "research" has been quite flawed by far at this point involving this game mechanic. I openly admit that the demo does have "lesser" restrictions than the current shard, but to the extent that he has suggested is simply preposterous. The packet throttle involving war mode change on the demo should be made certain before rushing and implementing the "claimed" inaccurate suggestion that has been made already by Hemperor.

He has also made many remarks that has been flat out untrue too.

The only reason Hemp is vetting this change is based on his ulterior motive from his last "pick and choosing" thread that apparently got deleted because of me(another lie). He is trying to make a point that since the "implementation" of the packet throttle on this server was chosen over accuracy that it should either be corrected or allow other inaccuracies to fall through that he prefers. However, his problem as I pointed out earlier is that this "packet throttle" for tab has existed since day one.. There was never no "implementation" or "patching" for this game mechanic in the first place...

[Hemperor]

Hemperor does make one good point about the demo...

It is a more reliable source than the core distro package that comes with RunUO until proven otherwise. However, his "research" has been quite flawed by far at this point involving this game mechanic. I openly admit that the demo does have "lesser" restrictions than the current shard, but to the extent that he has suggested is simply preposterous. The packet throttle involving war mode change on the demo should be made certain before rushing and implementing the "claimed" inaccurate suggestion that has been made already by Hemperor.

He has also made many remarks that has been flat out untrue too.

The only reason Hemp is vetting this change is based on his ulterior motive from his last "pick and choosing" thread that apparently got deleted because of me(another lie). He is trying to make a point that since the "implementation" of the packet throttle on this server was chosen over accuracy that it should either be corrected or allow other inaccuracies to fall through that he prefers. However, his problem as I pointed out earlier is that this "packet throttle" for tab has existed since day one.. There was never no "implementation" or "patching" for this game mechanic in the first place...

I suggest you read the topic I linked on the main page. ALL of the pvpers back in January remember this, there was a 5 page topic begging "PLEASE FIX THIS AUTO TABBING LOOP BS DERRICK" and he did. Read it. I specifically remember all of TW and major pvpers looping tab macros etc, it looked absolutely ridciulous. Derrick answered.

Read the topic, search your memory, whatever you have to do to stop denying the past.

[Faust]

Show me the patch note for this change.

[valheru]

I dont feel like searching for the patch notes, but Derrick did "fix" auto looping etc. I say fix, because while it's much more limited now, it still works for the most part.

[Faust]

I have already listed the patch notes and I know exactly what he did...

First Patch - Attacking and Tabbing pauses your swing delay just like the movement restriction.
Second Patch - Packet throttle change/add for attacking and item/drag lift functions.

That has been the only additions that were implemented/added on this server that stopped the effectiveness of a looping macro. The tab throttle is inside the RunUO default code and was never "removed" and "added" back here at all. Derrick has already confirmed this too...

[Redbeard72]

omg my head hurts, Why can i not fast cast? that is era accurate ! and the gay delay on my recasting? and hitting my halberd? is all NOT accurate. fuck the mechanics none of this is accurate.

[valheru]

As always Valerhu, you are incorrect. The current system now is anything but accurate, no one will dispute this, the system on the demo is accurate until proven otherwise...which will not happen of course.

Hemperor, your pop-shot, degrading comments, are neither permitted, nor welcomed in this forum. Degrading comments such as those are only used to incite hateful responses which ignite a conflagration of hate. Please keep those type of comments to the trash talk forum, or, risk being BANNED from the suggestion forum.

always wrong? i think YOUR T2A CHANGE thread cites my arguement, and proven fact, that stablemasters should be INVULNERABLE.

INVULNERABLE.

INVULNERABLE.

lol.

cakes

[Hemperor]

When can this be implemented?

There is nothing saying it's incorrect, it's pretty well known what we have now to be inaccurate.

[Faust]

When the correct nature of the function is confirmed.

There is no need to implement something incorrect over something believed to be incorrect.

I am highly confident that the majority of everyone would agree with this including the staff.

[Hemperor]

Faust, we both know what I have stated is correct.

It's EXTREMELY simple, Kaivan knows this as well and we have both confirmed it.

Fact is, what we have now is inaccurate and was put into place for nothing other than due to complaints.. I have documented this many, many times, the older pvpers here know this as well.

Something inaccurate was done on purpose, I know the accurate fix, let's do this.

[Faust]

I don't recall any definitive evidence in regard to this topic at all...

The last time that I checked this function on the demo it worked quite similar to the demo with the weird packet throttle that times out that prevents another tab for a specified time period. I can't be certain "what" that time period was but it was definitely longer than 0.25s in my opinion.

Derrick has already stated that the packet throttle for tab is unique and not a standard delay as you are suggesting.

Also, this function was never removed and re-implemented as you claimed in the past. I don't know if you still hold this true to your heart or not. However, the facts still remain that the current tab throttle is the same one that has existed from day one here on the shard. You can believe whatever you want to believe though for this notion...

[Hemperor]

I don't recall any definitive evidence in regard to this topic at all...

The last time that I checked this function on the demo it worked quite similar to the demo with the weird packet throttle that times out that prevents another tab for a specified time period. I can't be certain "what" that time period was but it was definitely longer than 0.25s in my opinion.

Derrick has already stated that the packet throttle for tab is unique and not a standard delay as you are suggesting.

Also, this function was never removed and re-implemented as you claimed in the past. I don't know if you still hold this true to your heart or not. However, the facts still remain that the current tab throttle is the same one that has existed from day one here on the shard. You can believe whatever you want to believe though for this notion...

I'll get Derrick to confirm it or any other pvper that was around then, you are certianly wrong on that one and I don't feel like linking the topic again.

Let's bash it out in this topic then, I am definitive on what I"ve said about tabbing and attack last, but let's do the whole 8 page thing so we can be for sure.

[Faust]

If you end up being right about this function it wouldn't bother me one bit... All that really matters is the correct way that this function works. However, from my perspective while testing this it did in fact time out while tabbing. I don't know what you may or may not be doing wrong but it did happen. You even sent a PM in irc telling me that it happened for you but was hard to pull off compared to UOSA's version of it... This was before you started talking about this topic prior to the current one today. I have no idea what changed since that PM...

Do you want me to pull up the log?

[Hemperor]

If you end up being right about this function it wouldn't bother me one bit... All that really matters is the correct way that this function works. However, from my perspective while testing this it did in fact time out while tabbing. I don't know what you may or may not be doing wrong but it did happen. You even sent a PM in irc telling me that it happened for you but was hard to pull off... This was before you started talking about this topic prior to the current one. I have no idea what changed since that PM...

Hopefully Kaivan will log on for once and confirm this, the only delays that may have appeared to happen were on the users side, the other client would still see the tabbing (or attack last) and it would still have the same effect.