LegionExploit 2.6 DEV
Before purchasing the product, I encourage you to read everything it includes and what it may offer in the future. We will not be held responsible if you buy the product without reading the instructions or guidelines.
When purchasing the plugin, you need to request the activation license by clicking here or by joining the Discord group shown on the side.
WARNING: If you attempt to run /katapin, an error will occur because this command can only be executed when an account is under investigation. It cannot be used just like that.
Block access for players with /op permissions.
If it detects that a player has joined the server and verifies that they have Operator status, a total account lock will automatically be applied until they enter the correct PIN that was sent to their linked account using the command /katapin
They will have a 1-minute timeframe to verify, so they will need to open their email, find the code that was sent, and then re-execute the command with the PIN, for example, /katapin 312312321. Once they enter the correct PIN, they will temporarily gain full access to the server.
If the player disconnects during the verification process, the permission will be automatically revoked.
Account lock for those with LuckPerms access and permission (*).
There are several current exploits, such as CMI or PLHIDE, that force a permission (*) through LuckPerms. Therefore, this system was created to mitigate unauthorized access. If an account with this special permission joins, it will automatically be placed under surveillance without access to anything and will be kicked. The only way to gain access is to be whitelisted in the plugin's config.yml.
If the player disconnects during the verification process, the permission will be automatically revoked.
Gmail Notification and PIN Verification
A system was created from scratch to send an email to your account with the PIN for verification to gain access with operator permissions. Similarly, if a player joins with Operator permissions or access to the (*) permission from LuckPerms, a real-time alert will be sent. This was designed to allow faster server management to know when someone connects with illegal permissions. It will display the server they connected to, the player’s name, the current IP address, and whether they logged in with an active PIN.
How to Set Up the Gmail AutoBot
TUTORIAL ON HOW TO CREATE A PASSWORD AND ACCOUNT FOR THE GMAIL BOT
Go to the URL https://myaccount.google.com/apppasswords and log in with the email you will use to create the AUTO BOT system. I recommend using a different account that you don’t actively use, as you can’t use the same email on both sides. Once you’ve logged into the page, assign a name to the app, for example, LegionExploit APP. Click the create button, and a menu will open with your password, for example, *dpvl rotv **** *****. Copy that key and paste it into the password field above. After copying the key, paste it into the password field and use the email you used to create the key in the . It will look something like this: gmail_setup
gmail_setup: "[email protected]" # I recommend using an unused email or creating a new one.
password: "epsl ndjr nahw qkql"And that's it! In the option, add the email where you want to receive the server emails. Use your most important email, for example, , and you're all set! Now go ahead and try it out! receiver: [email protected]
How to Obtain the License
There are two types of licenses: subscription and permanent. When purchasing the plugin, you can request your license through the purchase verification bot, which will be linked when you acquire your plan, or by joining the Support Discord mentioned earlier in this post and requesting your license from the bot.
Please note that the delivery process may vary from 5-15 minutes to 24 hours, but the usual time is 5-10 minutes.
How to Get (*) Access from LuckPerms
To be able to join with the (*) permission from LuckPerms, you need to add your username in the under the option. Simply replace the username SrCodexDevs with your own. You can add more names to the list in the same format. I recommend editing this while the server is turned off to ensure that the changes are fully applied.
config.yml - luckperms-whitelist
How to Detect an Account
When an account logs in cleanly and is granted administrative permissions, such as OP or the (*) permission in LuckPerms, a total restriction will be applied to the account. If the block is due to having OP status, the user will need to verify by entering the PIN that will be sent via email. If the block is due to having (*) permissions in LuckPerms, the account will be completely restricted, as I have disabled that option for security reasons. The only way to access (*) permissions is if you're on the whitelist in the config.yml file. Once you are inside the server, you can then grant yourself the permission—but not before. For security, any connection with prior access to these permissions is blocked. So, first, log into the server, and only then should you give yourself OP or (*) permissions in LuckPerms.
Config.yml
################################
# LegionExploit License #
# & #
# Server Name & Gmail #
################################
license: "" # License example: "xxx-xxx-xxx-xxx"
server-name: "" # Server name/modality
receiver: "[email protected]" # Gmail where you will receive notifications
############################
# Command only via console #
############################
console-only-commands:
- restart
- stop
- op
- deop
- lpb
- cmi
- lpv
- plugin
- pl
- ver
- lp
- execute
- fill
- killall
- eco
- clear
- kill
- ept
#####################################################
# Bypass for accounts that will have * in LuckPerms #
#####################################################
luckperms-whitelist:
- SrCodexDevs
#########################
# Verification spawn #
########################
verification-waiting:
world: ""
x:
y:
z:
# example #
#verification-waiting:
#world: "spawn-antiluckperms"
#x: 319.3213
#y: 69.231
#z: -331.3213
#################
# DO NOT MODIFY #
#################
host: "smtp.gmail.com"
port: "587"
debug-mode: false
#########################
# Install Gmail Bot #
#########################
gmail_setup: "" # Here you enter the email that you will use as an auto bot to send messages.
password: "" # Example ttrt wmwa **** ****
# TUTORIAL ON HOW TO CREATE A PASSWORD AND ACCOUNT FOR THE GMAIL BOT
#
# Go to the URL https://myaccount.google.com/apppasswords and log in with the email you will use to create the AUTO BOT system
# I recommend using a different account that you don't use, as you cannot use the same email on both sides.
# Once you enter the page and log in, give the app a name, for example, LegionExploit APP. Click the create button, and a menu will open with your password,
# for example, dpvl rotv **** ****. Copy that key and paste it in the password field above.
# After copying the key, paste it in the password field and use the email with which you created the key in gmail_setup. It will look something like this:
#
# gmail_setup: "[email protected]" # I recommend using an unused email or creating a new one.
# password: "epsl ndjr nahw qkql"
#
# And that's it!!! In the option receiver:, add the email where you want to receive the server emails. Put your most important email,
# for example, receiver: [email protected], and you're done! Now go ahead and test it!
Refund Policy
If you want a refund for the product, please note that I reserve the right to reject your request if your reason is unreasonable, such as server closure, no longer liking the plugin, or not knowing how to configure something. None of these are valid reasons for requesting a refund. Only valid reasons have a 24-hour period after purchase to request a refund.
LegionExploit Policy
I reserve the right to cancel your license at any time if you violate any of the terms of service. Any form of distribution, copying code, leaking with malware to damage the reputation, etc., is prohibited. For any of these reasons, your license may be canceled, and you may be reported to the website and blacklisted from our system. A direct refund will also be prohibited.
