Cheating

Cheating

Cheating is a serious rule break in CIT.

It covers gaining an unfair advantage through external tools, unfair technical abuse, or other dishonest methods that are not part of normal gameplay.

What counts as cheating

Cheating includes the use of outside tools or methods that give unfair advantages.

Examples include:

• using cheat software
• hacking
• using network disruption software
• using macro software

These are not allowed in any normal gameplay situation.

Cheating and exploiting

Cheating and exploiting are closely related, but they are not exactly the same.

`Cheating` is mainly about unfair outside tools or dishonest methods.

`Exploiting` is about abusing bugs, flaws, or game systems in ways they are not meant to be used.

Server-related bug abuse is also treated seriously, and exploiting server features in ways they are not meant to be used is punishable.

Severity

Cheating is one of the most serious offences in CIT.

Reasonable punishments can be given for cheating, and in very clear cases it may result in:

• a heavy punishment
• an unappealable ban

This depends on how clear and strong the evidence is.

Reporting suspected cheaters

If you suspect a player is using an aimbot, use:

/aimbotsuspect <player>

This command is used to report a suspected aimbot user.

You can also report players on the forum through the `Complaints` board if you have proper evidence.

Evidence for cheating reports

Cheating reports should have strong evidence.

Useful evidence can include:

• clear videos
• clear screenshots when appropriate
• proper damage and network information when relevant
• complaint details with time and explanation

If the case is about abnormal damage, lag abuse, or similar suspicious behaviour, strong video proof is much better than a weak screenshot.

For some combat-related suspicious cases, it is important to record useful extra information such as:

• /debugplayerdamage
• /shownetstat
• /ping player

If you are reporting someone in `LV` for abnormal damage, those details are especially important.

Health bug and suspicious damage

Not every strange combat situation automatically proves cheating.

For example, if someone appears bugged or does not lose health, a screenshot alone is usually not enough to prove what happened.

A clear video is the better proof in those cases.

If a player realizes they are bugged and stops, that is different from knowingly continuing to abuse it.

LV cheating and exploit notes

There are extra notes for `LV` complaints.

In `LV`:

• bind-related desync and bugs are not automatically counted as cheating
• if it is proven that the bug is related to an `MTA` flaw, such as a fake-jump exploit, it can still lead to punishment for cheating or exploiting

If you report an `LV` case:

• your video must not be recorded with /uav
• your video must clearly show the reported player
• your video must clearly show the relevant proof
• your video must clearly show the pings involved
• your video must show your own ping and FPS
• you must use /debugplayerdamage when reporting abnormal damage

Forum complaints for cheating

If you report cheating on the forum, make sure your complaint includes:

• the correct complaint format
• the player's name
• the account name if known
• the time and date
• a detailed explanation
• proper evidence

Weak, edited, or unclear evidence can make a complaint invalid.

Important notes

• Cheating is not limited to one specific hack.
• Cheat software, hacking, network disruption software, and macro software are all prohibited.
• Very clear cheating cases can lead to very severe punishments.
• /aimbotsuspect <player> is the direct command for reporting a suspected aimbot user.
• Strong video proof is usually the best evidence in suspicious combat cases.

See also

• Complaints
• Rules
• Punishment Appeal
• Las Venturas
• Aimbot