Configurations

The configuration

Common config

At the top of the file, you have some important config :

• log_alerts : Enable or disable the log of alert (in file /Negativity/user/proof/)
• log_alerts_in_console : See (or not) the alert in console
• tps_alert_stop : The minimum of Tick Per Seconds (TPS) needed to send alert. A server work perfectly at 20 TPS.
• time_between_report : The time (in milliseconds) between 2 report (to prevent command spam)
• time_between_alert : The time (in milliseconds) between 2 message of alert. If more than one message have to be sent, they will be assemble in one. (So, 'X seem to use Y' but 'X seem to use Y nb time')

Manage command

You can disable commands in "commands" section, specially to remove conflict. The alias are called AFTER real command. So, if another plugin use a command like /report, it will call it and not the /report negativity's alias.

• report : Allow the /nreport (Alias: /report)
• ban : Allow the /nban (Alias: /ban)
• unban : Allow the /nunban (Alias: /unban)
• kick : Allow the /nkick (Alias: /kick)
• mod : Allow the /nmod (Alias: /mod)
• lang : Allow the /nlang (Alias: /lang)

Database

You have a database ? You can use it. How ? There is a Database section. Set "isActive" in the section to "true".

The URL is like : 1.2.3.4/myDb where 'myDb' is a schema which already exist (Negativity DON'T create it).

User: the database user. Can be root or what ever you want. He just need permission to create table. Password: the user password.

Where use it ? We will see it after.

Inventory config

Negativity have custom GUI. There is some option :

• 'inv_freeze_active' : To see (or not) the Freeze inventory when a mod freeze you. If enabled, you cannot quit it.
• 'no_started_verif_cheat' : If true, you will see alert of cheat which are not in verification (so, with 'autoVerif: false', check below)
• 'only_cheat_active' : If true, you will only see alert of active cheat.

Items bypass

You have specific effect when someone right click with a paper ? No problem. You can add an item like that:

MY_ITEM:
   when: WHEN
   cheats: aCheat

Replace MY_ITEM by the bukkit name like COOKED_BEEF. Warn: On 1.12 and lower, you cannot add durability to make, for example, red wool.

Since 1.12.2 and for issue #322, you can add new field that will be checked. They are optional (not working on sponge for free)

• name: Check for exact name of item
• unbreakable: Boolean if the item has the same unbreakability state
• enchants: List of all enchants (1.8, 1.19) like enchants: [ "THORNS", "RIPTIDE" ]

When available:

• always : All the time that the player hold the item
• right_click : Each right click
• left_click : Each left click
• looking : The player is looking the specified block
• wearing : Armor on the player (since v1.12.2)
• below : The block below the player
• Need more ? Open new issue

Finally, there is 'cheats'. You can separate them by ',' to disable multiple cheat.

Permission

More informations about it here

Translation

Here, you can edit the language. There is 2 ways :

1. All player are in the same language. For this, you just have to change the default lang "default".
2. Each player can config they own lang. For this, set "active" to true. Now, by default, all player will see the plugin in the default lang, but if you do /nlang you can see and change your lang.

The provider is here to allow to developer to use their own custom system thanks to call: TranslatedMessages.registerTranslationProviderFactory(String id, TranslationProviderFactory factory); Then by setting "platform" to the specified ID.

Alert config

If you can to run command when someone get alert, you want just to set command.active to true, then edit the command. We will run all command include in the list.

The 'reliability_need' correspond to the reliability in the alert. The detection calcul the porcent of the reliability of the alert, and so you can make it high to be sure that the player is cheating.

Ban config

Such as permission, there is a config which explain everything about the bans here.

Account storage

You can save account data thanks to 3 ways:

1. file: used by default. All data will be in /Negativity/user/
2. database: You have to enable it. We create the table for the account, and made sure that you have the latest version.
3. void: Don't save account (not recommended).

Proof storage

You can save account data thanks to 2 ways:

1. file: used by default. All data will be in /Negativity/user/proof/
2. database: You have to enable it. We create the table for the proofs, and made sure that you have the latest version.
3. void: Don't save proof file.

Cheat config

Here, you can find the explaining of what are doing which cheat.

• ping : The max player latency required to send alert. If he has a higher ping, the alert will be disabled.
• exact_name : The display name of the cheat
• isActive : Enable or disable the detection. We suggest to you to disable useless detection to keep ressources.
• reliability_alert : The minimum of reliability needed to create alert
• setBack : If true, we cancel the player action. For example, if the player get alert for Fly, we will teleport him on ground.
• kick : If true, we will kick the player when he get alert.
• alert_to_kick : The number of alert needed to be kicked.
• check_in_verif : If true, we will check the cheat in verification. Else, it will not be showed (and calculated) in summary.

Since Negativity 2.6.1, you can have some config in the general config file :

# This apply to absolutly ALL checks: cheats and special
config_all:
  # Config for bedrock users
  bedrock:
    disabled: false
  # Config for java users
  java:
    disabled: false

  # Options only available for cheats
  cheats:
    kick:
      active: false
    set_back:
      active: false

Bedrock config

If you are using floodgate & geyser to support bedrock user, you have few options (actually one). In the bedrock section (not always in file), you can use:

• disabled: Disabling all check for bedrock users

Java config

As bedrock config, you can do the opposite for java users (since Negativity 2.6.1):

• disabled: Disabling all check for java users

Some specific configuration, according to the cheat:

Forcefield

The 'reach' is the distance, in block, before getting alert. Yes, the Reach cheat is include in Forcefield. ghost_disabled (if on false) make appear invisible fake player behind someone. If he hit us, it will get alert.

NoFall

When you fall and the setback option is enabled, you cannot be killed. But, you can enable it thanks to the 'kill' option. You can always edit the reliability need to kill him. Warn: the player will take the damage that we have to take. And we will edit the amount of damage according to the option. It's not automatic.

FastPlace

You can edit the time between 2 block placed thanks to the 'time_2_place' option (default: 50). It's in milliseconds.

Chat

The chat have an anti-insult. You can add every message that you want in the 'insults' section, and we will search it in the player message. You can add what you want, according to your country ! Try to don't set message like 'ez' because they can be include in another word.

Special

MCLeak

McLeak is a free service that give minecraft account, mostly use to cheat. When you do /negativity , there is a wool (red or green) which represent if the player account is an MCLeak or not. You can kick them by setting "kick" to true.

Server Crash

(Spigot only) We detect when someone try to crash your server. Even if it doesn't work (because sometimes it's fixed in the spigot update), you can kick or ban him. By default, we kick him but not ban. The 'ban_time' correspond to the time (in milliseconds) while the player will be banned. (Obvisouly, ou want to enable ban before)

Invalid Name

Some people can have invalid name thanks to crack client. They can crash other client when they try to run command with invalid character. Invalid name example: §cElikill58. The "§" is not allowed. The 'ban_time' correspond to the time (in milliseconds) while the player will be banned. (Obvisouly, ou want to enable ban before)

Max player/IP

To prevent multiple account from same IP, you can kick people when there is too many player on same IP. By default, the third account will be kicked.