CaptchasX - Extremely Configurable! [Recoded]

Added: Support for nLogin. This is untested, if not working please submit a bug report! (Requested by Nadif)

Fixed: Errors in version 1.21 and above. Please use the legacy jar for versions 1.20.6 and below, and the normal jar for versions 1.21 and above. Support for versions 1.20.6 and below will cease from this point onwards. Blame spigot dev team for it, it was not my choice to drop support since I do love supporting more versions where possible as long as it only takes 1 jar file.

Fixed: Error when opped player gets captcha triggered on them for first time.

Fixed: Error when using /captchas help

Fixed: Minor fix for /captchas.help message Changed: Simplified command matching logic.

Added: help command messages for /captchas open and /captchas close commands Do pop me a review if you like the plugin (or not)!

Added: /captchas open (player) command to force open a captcha Added: /captchas close (player) command to force close a captcha Fixed: Miscellaneous AuthMe integration edge case bugs

Fixed: All triggers count as FirstJoin triggers.

Fixed: All issues hopefully. Changed: Config files all need to be regenerated and are easier to understand. More features are also supported. To be added: - captcha open/close commands - Suggest more features! The plugin is much easier to work on with the complete rewrite and should also work more smoothly, just throw your suggestions in the discussions

Added: Support for LockLogin. Enable support for this using the "UseAuthMe" option in Config.yml. After enabling UseAuthMe, the plugin will detect if you have LockLogin or Authme and enable support for whichever one is needed. After the player has successfully registered their account under LockLogin, they will then be made to do their FirstLogin captcha. If this support doesn't work, there's not much I can do since the plugin itself doesn't have a completed API. If it doesn't work we just have to wait for the API to catch up I guess.

This update contains changes to the Config.yml file. Please edit accordingly based on instructions below. Added: Option to only activate captchas on spawner spawned mobs or named mobs. (Suggested by @DuckWeedVN) Add this under EntityDamageByEntityEvent: .SpoilerTarget">Spoiler: Config.yml insert Code (YAML): #Only trigger captcha on spawner spawned mobs and named mobs (such as mob stacks). Spawner : True

This update contains OPTIONAL Config.yml changes. Only add them to your config if you want to use the new feature Added: Config options to make the correct item look different (custom name, lore and glowing effect) to make it slightly easier for players to solve the captcha. (Requested by @PhoebePower) Fixed: Error when plugin is being disabled. Fixed: Error when loading config sometimes. Add this below Delay: .SpoilerTarget">Spoiler: Config.yml insert Code (YAML): ####################### # Picked Item Options # ####################### #Settings for changing the look of the item to be clicked. #Delete this section if you don't want the item to look different. #You can delete any part of this that you don't want changed too. Picked : #Special name for the item to be clicked. Name : "&6&lCLICK ME!" #Special lore for the item to be clicked. Lore : - "&aThe right answer" - "&ais right here." #Whether to make the item to be clicked glow. Glowing : False

Added: /captchas close (player) command to close the open captcha for the specified player. (Requested by @drood) Fixed: Captchas not closing when plugin is reloaded/server is restarted, and thus allowing players to take the items out of them. Add this below Grace: .SpoilerTarget">Spoiler: Messages.yml insert Code (YAML): #Message sent to the player when you use the /captcha close command on them. Close : "&aBy the grace of the Gods (your admins), the captcha has been closed!" #Message sent to you when you successfully use the /captcha close command. Closed : "&aCaptcha successfully closed."

Added: Support for AuthMe so players are only checked after they have logged into AuthMe. (Fixes authme related errors and bugs) Added: some comments into Config.yml and Items.yml for new users who may be using Minecraft 1.12 or below. Add this below FirstLogin: .SpoilerTarget">Spoiler: Config.yml insert Code (YAML): #Whether to integrate with authme and only check players after they have logged in. UseAuthMe : False

Fixed: Error saving player when they go offline. (Reported by @drood) Fixed: Player not being saved if no players are saved.

This update is just to revert downloaded file to v1.2.7a. The plugin page didn't do it itself.

This update has OPTIONAL config changes. If you want the option for players to get rewarded when they get the captchas correct, please add the insert below to the config file. Added: Option to reward players if they answer captchas correctly. Add this below Commands: .SpoilerTarget">Spoiler: Config.yml insert Code (YAML): #Commands to run when player answers captcha correctly. These HAVE to be console commands! #Comment the whole block out or delete the block to disable. Bonus : - 'eco give %player% 100'

Fixed: Plugin erroring when setting border item type as (type) data) in versions under 1.13. Changed: /cap (player) command now ignores cooldown.

This update contains changes to the Config.yml. Please read carefully before updating and loading in this update. The new settings if enabled should help reduce the impact of player bots on your server, especially if you give players a short amount of time to complete the captchas and kick them as punishment. (Hmu SalC1 if you got the info on how your players bypass the captchas man I don't use hacked clients so I'll never know) Fixed: First login captchas not triggering. Fixed: First login captchas not saving triggered players properly. Changed: /captchas reload now regenerates plugins files for you if they have been deleted instead of simply throwing errors and being a crybaby about it. Added: New option in Config.yml FirstPunish for you to decide whether you want to punish players immediately if they fail their first captcha. (This only punishes them immediately for the first captcha if you have FirstLogin enabled.) Added: New option in Config.yml Freeze for you to decide whether you want to freeze players in place before they complete their first captcha. (This only freeze the players if you have FirstLogin enabled.) Add this below FirstLogin: .SpoilerTarget"> Spoiler: Config.yml insert Code (YAML): #Whether to immediately punish a player if they get their first login captcha wrong. FirstPunish : True #Whether to freeze a player if they have not completed their first login captcha. #Frozen players will be unable to speak or interact with their surroundings. Freeze : True

Fixed: BlockBreakEvent only working on legacy mode. (Reported by @Scarllium )

This update has config file changes. Please make sure you make the amendments for the plugin to keep working. I'm also considering adding the ability to freeze players (cancel all events relating to the player) before they complete the captcha when joining the server for the first time. If you are interested in this feature and want it to be added, please either tell me in the threads or like this update. Thanks! Changed: Made the chance of captchas triggering discrete for each event. Added: Ability to toggle the block filter between blacklisting and whitelisting. Add the following lines under PlayerFishEvent and EntityDamageByEntityEvent: .SpoilerTarget"> Spoiler: Config.yml insert 1 Code (YAML): Enable : True Chance : 1000 Add the following line under Block Filter Options: .SpoilerTarget"> Spoiler: Config.yml insert 2 Code (YAML): #Whether to turn the filter into a whitelist. Invert : False Remove the following lines: .SpoilerTarget"> Spoiler: Config.yml remove Code (YAML): #Chance for captcha to open. 1000 chance would be a 1/1000 chance for captcha to open. Chance : 1000

Fixed: Left some debug code in. (Reported by @luffy1025 )

Fixed: Error when clicking on any empty slot in any inventory. (Reported by @BakedLock ) Fixed: Error when opening captcha without border set. (Reported by @Scarllium )

Added: Wrong item name checker for version 1.12 and below. Fixed: Possible errors from deleting borders.

Added: Option to set border items for the Captchas GUI that does nothing when clicked. (Suggested by @BakedLock ) Changed: Added some lines to Config.yml. Add this under GUIName: .SpoilerTarget"> Spoiler: Config.yml insert Code (YAML): #Settings for the border item. #When the border is clicked, players are not punished. Border : #Material the border item is made of. ItemType : "GRAY_STAINED_GLASS_PANE" #Name of the border item. Name : "&7&lBorder" #Lore of the border item. Lore : - "&7This is the border." - "&7It does nothing." #Slots to place the border item in. #Just delete this whole list to disable. Slots : - "1" - "2" - "3" - "4" - "5" - "6" - "7" - "8" - "9" - "10" - "18" - "19" - "27" - "28" - "36" - "37" - "38" - "39" - "40" - "41" - "42" - "43" - "44" - "45"

Note: I have updated the plugin to be in api version 1.13. This means that old item names will not work if you are running spigot 1.13 and above. Anyone running versions below 1.13 DO NOT delete your Items.yml file as the default one would not work for lower versions. Fixed: Cooldown not working properly. (Reported by @Gethelp ) Fixed: Cooldown not being started properly. Fixed: Cooldown being overridden by "still doing captcha" state. Fixed: Players not being taken out of "still doing captcha" state after they have completed the captcha. Added: Code to tell you which item is causing the errors when making the captchas GUI. Changed: Item names in the Items.yml file. If you are using spigot version 1.13 or above, please use the code that tells you the errors to find the wrong item names, or simply let the plugin generate the update set of item names for you by deleting Items.yml. Servers running 1.12 and below can keep their old files.

Fixed: Error when running /captchas (player)

Added: Missing permissions support for Captchas.Bypass permission.

This update includes minor changes to the config.yml and messages.yml files. Please make the necessary changes to avoid errors. Added: Command /captchas reload to reload config files without reloading plugin. Added: Command /captchas (player) to open the captcha for a specified player. (Suggested by @lattyhelp ) Added: Grace period option in Config.yml to allow players a period of time where clicking the wrong answer does not punish them. This is an alternative or addition to the warning feature previously added. (Suggested by @Gethelp ) Changed: Additional lines added to Config.yml and Messages.yml as shown below. Insert under FirstLogin: .SpoilerTarget"> Spoiler: Config.yml insert Code (YAML): #Time in seconds that captchas ignore wrong answers when they're first opened. #Set to 0 to disable. Grace : 2 Insert under Warning: .SpoilerTarget"> Spoiler: Messages.yml insert Code (YAML): #Message sent when a player tries to click during the grace period. Grace : "&7Grace period! Please click the correct answer!"

Fixed: Cooldown being called before a player does a captcha, rather than after. (Reported by @luffy1025 ) Added: Ability to open a captcha for players on first joining the server. (Suggested by @Musicalist ) Changed: Added 1 line to Config.yml. Insert this under general options: .SpoilerTarget"> Spoiler: Insert Code (YAML): #Whether to check a player when they first login. FirstLogin : false Changed: Added Players.yml to track new players. Changed: Captcha opening message now sends after the warning delay, not before.

Fixed: Captcha not opening if a player has chat open when they are on captcha opening delay. (Reported by @Gethelp )

Fixed: Captchas never triggering if a player continues clicking on warning. (Reported by @Gethelp ) Fixed: Plugin sending messages to player for every time they trigger something. Fixed: Plugin sending messages to player even if they are on cooldown.

Fixed: Ability to keep interacting with the world and possibly having multiple captchas going on at once. Now you can only have 1 captcha queued at one time. Hopefully this fixes your issues @Mythanh

Pretty big update here guys, please backup your config files and let the plugin regenerate them for you. Then you can throw your stuff back in after Any questions on the new config options can be left in the plugin thread Added: Block blacklist for BlockBreakEvent. Now you can decide which blocks you don't want the captcha to trigger on. (Suggested by @PieHater25 ) Added: A grace period for players who answer the captcha correctly. Reduces player annoyance from unlucky RNG. (Suggested by @PieHater25 ) Added: An option to delay the appearance of the captcha and warn the player in chat, so that they don't accidently click on the captcha. Added: Some new messages. (For the new features)

Added: Ability to change the name of the item displayed under %item%. (Suggested by @luffy1025 ) Added: A "Cooldown" option under Config.yml to let you set a cooldown before players get checked for captchas again after they have completed a captcha successfully. (Suggested by @luffy1025 ) Changed: Renamed the file config.yml to Config.yml. Just backup and delete your old config file, and let the plugin regenerate it for you. Changed: The Items.yml file. Please let the plugin regenerate it for you. Since the ability to decide what goes into the %items% placeholder allows you to use any language you want, if anyone translates the file to other languages and would like to share your translated file, please PM me a pastebin of your Items.yml file and I'll put it in the next update as a locale file

Fixed: Error when block breaking captcha tries to trigger.

Added: Support for Minecraft versions 1.14 and 1.15. Fixed: Plugin throwing errors on startup.

Added: Support for 1.12.2 through 1.13.2 (Spigot/Vanilla changed the way they handle durability now, it's not stored in the same place anymore)

Basically a small recode to make the code neater because I lost the progress due to a hard disk wipe and incomplete backup to github.

NOTE: THIS UPDATE REQUIRES A REGENERATION OF THE CONFIG. BACKUP YOUR OLD ONE AND UPDATE YOUR SETTINGS. Added: Options to use PlayerFishEvent or BlockBreakEvent. Added: Timeout option to automatically log a player's response as wrong if time runs out.