Civcraft2Import:Rules/botting

= Botting and Scripts
=

Main article: Actions defined as cheating

Players sometimes use external programs or mods to automate tasks within the client by writing scripts or macros. Heavily automated ones are often called &quot;bots&quot; by the player base. Unlike simple scripts, bots are banned. Scripts must abide by the following rules:

- Scripts must be very limited in capabilities and may only carry out one or two tasks at a time.

- Scripts may not be linked together in a manner that allows for simultaneous actions.

- Scripts must only carry out activities that would be possible by a human.

- Scripts may not act upon outside information of any kind.

The goal here is that the administration wants human players to actually be playing on Civcraft instead of machines.

If you have any questions as to whether or not your mod or script abides by cheating policy then contact modmail and share the script there.

Examples of Legal Scripts
The following are examples and do not cover all cases, but do represent some examples of legal scripts:

- A script that simply runs forward and holds down the left mouse button to mine.

Examples of Botting
The following are examples and do not cover all cases, but do represent some examples of botting:


 * An autofisher bot that reads the state of the fishing rod to detect if a fish has been caught. A script that can read environmental data is a bot.
 * Mining bot that detects uses block identifiers or id's to detect ores.
 * Farming bot that uses identifiers or id's in its operation.
 * Obsidian mining bot that uses block identifiers or id's to detect the obsidian.
 * Reading item identifiers to move items. Use item slot instead.
 * A script that can read chat information is a bot.