|
|
|
|
|
|
|
Client abuse (Rules and Policies)Every so often, it comes to our attention that people have decided
that an edge can be gained in this game by creating increasingly complex
scripts in their clients. While we welcome fair use of clients, and
fully realize how much they improve the gaming experience, there are
some limits as to how far client-side scripting can go before crossing
the line.
The two primary ways that clients can be abused are as follows:
- When Player A intentionally abuses/misuses Player B's client scripts
to exploit/hijack Player B in some way that Player B does not wish to
happen. We feel that both players share blame in such cases: Player A
for obviously attempting to abuse someone's client, and Player B for
allowing (even unintentionally) his or her client to be abused, by
setting up insecure scripts/triggers.
- When Player A configures his or her client in such a way that it
crosses the line into botting. There are two main subitems here:
- "Classic" botting, where a client runs through a series of
commands, performing actions such as killing mons, healing,
selling gear and banking gold, all without requiring any input
from the typist. See "help botting" for more on this.
- "Call-and-Response" botting, where a player configures his or
her client to respond to stimuli from another player (such as
a tell), perform an action based on that stimuli, and perform
some further action with the results, such as (but not limited
to) sending back a response with the results of whatever action
was performed. This would be your "find bots" where Player A
sends a tell to Player B of "find bob", and Player B's client
fires a script to run the find, and send Player A back a tell
with the results of the find.
Both of these scenarios provide what we consider to be an unfair
client-based advantage, and both will be treated as botting if detected.
The punishments for botting are usually severe, and generally involve
forfeiting any involved characters, so great care should be given to
staying within the rules. Intentionally attempting to find loopholes
and gray areas, or relying on a "well you didn't explicitly say this
was wrong" defense, is strongly discouraged.
|
|
|
|
|