[imported_MadMan]

I never used to either, people do have autocut by the way.

Autocut here? And working without auto kill?

doubt it =/

[imported_Taran]

I've spent a number of hours trying to fix this now, but it's not really possible due to the fact that ctrl+shift works with the client and not the server.

One solution to this would simply be to disallow cutting for let's say 1 second after the player has been killed. That means noone would be able to cut before 1 second has passed, not even if you try it manually.

This would actually fix a number of bugs. Like the corpse name displaying a random name when you use ctrl+shift, a bug where the corpse has no robe and sometimes display the wrong itemid and most important of all it will fix a crash bug that sometimes happens if you use ctrl+shift at the moment the player dies.

But I'm not really sure if the PvPers want this since you won't be able to cut players fast, thoughts?

[imported_Hate]

I've spent a number of hours trying to fix this now, but it's not really possible due to the fact that ctrl+shift works with the client and not the server.

One solution to this would simply be to disallow cutting for let's say 1 second after the player has been killed. That means noone would be able to cut before 1 second has passed, not even if you try it manually.

This would actually fix a number of bugs. Like the corpse name displaying a random name when you use ctrl+shift, a bug where the corpse has no robe and sometimes display the wrong itemid and most important of all it will fix a crash bug that sometimes happens if you use ctrl+shift at the moment the player dies.

But I'm not really sure if the PvPers want this since you won't be able to cut players fast, thoughts?

A nice lil solution is for everybody to change their way of cutting, and instead cut by dclicking the weapon and hitting the corpse on the ground. Yes I'm sure some of you will be like "but.. then I can't cut if somebody dies behind a house!" , well think again, I've never used CTRL + SHIFT and I cut quite fast if I may say so myself. Make it a habbit to have circle of transparacy enabled and you will be able to cut people if they die behind houses as well.

I think that ctrl + shift-cutting is something that most people never used back in the old days, and we were able to have fun and cut fast anyways, it just requires a little more skill, but that's what's fun about it, it's no fun if u can cut people too easy.

Stop using ctrl + shift and u won't be killed by the autocut bug, that's my "fix" to this problem :]

Regards,
Hate

[imported_Ryuuku]

I saw Lederoil saying he dies from auto cut on CTF even doiing Dbclick on bard and targeting corpse.

On that thread: http://www.in-x.org/forums/showthread.ph...light=Anti

[imported_Gang-Bang]

Well I dunno how it could happen... I used to cut even when body didn't hit the ground yet, but still I never was autokilled. Even tho I never used CTRL+SHIFT either. And yeah, I would be absolutely againest setting delay like 1 second before cut. Cos decent enemies will ress eachother in less than 0.5sec:/

[imported_Taran]

You will only get killed if you use ctrl+shift or a script. If you dont use either of those you can cut as fast as you want to.

The delay doesn't have to be 1 second, it could be 0.8 or even 0.5 seconds. But the lower the delay is the more advantage players with autucut scripts have.

[imported_MadMan]

I've spent a number of hours trying to fix this now, but it's not really possible due to the fact that ctrl+shift works with the client and not the server.

One solution to this would simply be to disallow cutting for let's say 1 second after the player has been killed. That means noone would be able to cut before 1 second has passed, not even if you try it manually.

This would actually fix a number of bugs. Like the corpse name displaying a random name when you use ctrl+shift, a bug where the corpse has no robe and sometimes display the wrong itemid and most important of all it will fix a crash bug that sometimes happens if you use ctrl+shift at the moment the player dies.

But I'm not really sure if the PvPers want this since you won't be able to cut players fast, thoughts?

Having to wait 1 second to cut would suck.

I agree with hate.. just dont use ctr shift

[smoke]

yeah don't make a delay on cutting.. pretty lame though that the script is like that..

[imported_Ginz]

I agree with hate no delay. And the reason it wasent used in the old days were because the old clients didnt have that feature.

[Eighty Swords]

I don't see how .5-1 second delay on cutting someone is such a big thing, especially if it fixes the problem you're all so concerned about. First of all .5 seconds is barely enough time for the dead guy to press tab to go into war mode and how often are you standing RIGHT next to your gank partner when he dies? In most cases it would take you 2-3 seconds to run to them.

A .5 second delay is a very small compromise if it means getting rid of the problem where you die for 'auto-cutting' someone...

The people new to pvp won't be able to cut as fast as some other people who have been pvping for so long so if anything a .5 second delay evens it out a bit and gives the newer people that one small chance to get back into the fight if their partner is fast enough to res them in .5 seconds...

That's just my thoughts on it and maybe a way to try and get more people to pvp if they think there's a chance they can come back to life...

[imported_MadMan]

I don't see how .5-1 second delay on cutting someone is such a big thing, especially if it fixes the problem you're all so concerned about. First of all .5 seconds is barely enough time for the dead guy to press tab to go into war mode and how often are you standing RIGHT next to your gank partner when he dies? In most cases it would take you 2-3 seconds to run to them.

A .5 second delay is a very small compromise if it means getting rid of the problem where you die for 'auto-cutting' someone...

The people new to pvp won't be able to cut as fast as some other people who have been pvping for so long so if anything a .5 second delay evens it out a bit and gives the newer people that one small chance to get back into the fight if their partner is fast enough to res them in .5 seconds...

That's just my thoughts on it and maybe a way to try and get more people to pvp if they think there's a chance they can come back to life...

I dont have anything against you but.. Exactly you dont see how a delay on cutting is such a big deal. But it is and to give new players a chance to res? Ressing shouldnt even be considered easy.. its beyond that thats how easy it is.. So your taking the ppl who cuts fast skill away from them just so someone who sucks can have a chance to res =/

[Eighty Swords]

Good point when you put it that way MadMan

But this could serve two purposes at not that much of a penalty to the super skilled players who can cut in .001 seconds;

1) Might get more people to pvp
2) Stops the chance that you get killed for 'auto-cutting' when you just did ctrl+shift, which is a client/uo feature and not even a razor or inject feature!