Shattered Kingdoms

I tried this and you cannot throw because you are already firimg message is given

However, you can simultaneously reload two weapons.

That's pretty juggly.

http://www.youtube.com/watch?v=q3t_VaE32cQ

Like this.

Out of curiosity, does the staff expect for the "kip up" skill to cause any sort of abuse through triggers, and/or are there any tools or methods the staff is intending to use to detect triggers? Obviously players should report anyone that they feel is using triggers, I was just wondering if there were any other thoughts on the matter for this skill in particular, as it seems to arguably probably be the biggest skill that would gain a benefit from triggering.

If you were using any skills before you got bashed / proned, and your trigger tried to kip up for you, you still have to resolve the prone lag from everything else before you kip up.

That said, yes, we're always watching for triggers / bots, they will be dealt with accordingly.

By the way, dual-wielding crossbows? You're welcome.

Other than randomly testing people with pattern echoes, there is no conclusive way to know. If someone is clever with their script, pattern echoes and other tests won't be effective. I don't see this being problematic, unless there is no lag associated with using the skill.

Testing for triggers is exceedingly easy, but the reliability comes with a grain of salt. Here's the general idea:

Set part of your prompt to be a line that will never occur in the MUD otherwise.

Create a trigger. Every time you see that line, set the "last" time to the timestamp in memory. Compare to the "current" timestamp, saving it in memory. Use the highly accurate clock for microseconds. You wind up with the "time delay" between prompts.

If that time delay is ever below the average human reaction time, around 200 milliseconds, display a notification. Whatever came before that prompt was possible not reacted to by a human, though it may have been a stacked or lagged command.

Immortals could have a better version of this command if each pulse had a sequential count available in the prompt, so that they could see if there were any pulses (which seem to be around 150 milliseconds) between prompts. That would take lag problems out of the equation, too.

That method is both unsound and unreliable.

I have experimented with triggers on my mortals and gotten pretty good at utilizing them in ways that would be considered cheating. I have only done so to enlarge my understanding of how to catch people using them. There are methods to catch these things and I certainly won't go into them, but yes, botting is definitely something we watch for. I am not going to say that its really going to catch people off guard who know how to really script a good trigger. If you're the kind of effort in to develop a this kind of trigger, yes, I won't likely catch it. On the other hand, there's always random things that happen and can send an immediate flag to us if you've done so.

Bottom line, don't use bots. Trigger to notify and pay attention to your character.

I like the idea behind kip-up, but the implementation is problematic since there is no lag associated with using the skill. The novices will get caught and deleted. However, you aren't going to catch a sophisticated cheater that wants to abuse kip-up. You know it, I know it and they (the cheaters) know it.