rules:glitching
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| rules:glitching [2015/08/04 02:37] – created kip | rules:glitching [2017/03/23 01:26] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Glitching ====== | + | //This isn't your typical multiplayer game mod, you're in a co-operative game that emphasizes teamwork within fellow players, and where your enemy is armed with a 3-watt light bulb with no intellect whatsoever to jump over a branch.// - Johao |
| - | Bots have no wit or brain; they just charge at you at the nearest given opportunity and will only be stopped by a wall. Naturally, their lack of intelligence allows them to be abused in unimaginative ways. | + | ===== Glitching |
| - | As a general rule, if it seems like something | + | Bots have no wit or brain; they just charge at you whatever way seems shortest and will only be stopped by a wall. Naturally, their lack of intelligence allows them to be abused in unimaginative ways. |
| - | Here are some more specific guidelines for determining what is a glitch: | + | We define glitching as using a bug in the game to give yourself an unfair advantage or bypass a restriction. |
| - | | + | Here are some examples of glitches: |
| - | * A position | + | |
| - | * A place where only bots with very long weapons can reach you (like pikemen). | + | |
| + | * A place where many bots cannot reach you with melee weapons. (Long pikes don't count.) | ||
| * A place where bots get stuck deliberately and cannot escape. | * A place where bots get stuck deliberately and cannot escape. | ||
| - | * Blocking bots with objects that they will not destroy. | + | * Blocking bots with objects that they cannot or do not destroy. |
| * Standing on barricades and platforms which are stacked or built on a wall or other prop. | * Standing on barricades and platforms which are stacked or built on a wall or other prop. | ||
| * Toming yourself in. | * Toming yourself in. | ||
| - | These are some edge-cases which are not considered a glitch: | + | Stacking deployable items such as barricades and platforms on each other was never intended and is considered glitching. |
| - | * Places reachable by most melee bots (such as a large rock or medium wall). | + | Do not simply ignore people who are glitching. If you are found to have knowingly played while someone was glitching, you might very well be suspected of using the glitch yourself |
| - | * Standing on barricades // | + | |
| - | * Bots suiciding on friendly fire (they do not drop xp). | + | |
| - | * Fence hopping if the bots can access the area on the other side. | + | |
| - | Stacking deployable items such as barricades and platforms on each other was never intended and is considered glitching. Barricades | + | If an admin says you are glitching, the best policy |
| - | The creation of characters just for the purpose of selling their starting gear for gold is considered a glitch. Any player found with an unusually high number of alts with no/low stats will be closely examined and generally banned immediately. | + | ===== False Positives ===== |
| - | Do not simply ignore people who are glitching. If you are found to have knowingly played while someone was glitching, you might very well be suspected of using the glitch yourself and could share in the punishment! | + | Although these might seem like glitches at first, they are not: |
| - | Remember that admins and most players in this mod shun the idea of glitching. Anyone caught glitching will receive | + | * A places reachable by most melee bots (such as a large rock or medium wall). |
| + | * Standing on barricades //which are on the ground// | ||
| + | * Fence hopping if the bots can access | ||
rules/glitching.1438655844.txt.gz · Last modified: 2017/03/23 01:26 (external edit)
