A Discord bot that automates NGL message spamming with real-time status tracking and proxy support.
- Auto-spam NGL messages to specified usernames
- Multi-threaded message sending (default: 10 threads)
- Real-time status dashboard with live updates
- Configurable duration in minutes (max 5 minutes)
- Maximum 5 concurrent spam tasks per user
- Proxy support with automatic type detection
- Automatic error handling and rate limit management
- Guild-based access control
- Admin controls to enable/disable bot and proxy
- Random message selection from 3 variants
- Bot invite link command
- Detailed statistics: send rate, errors, proxy status
-
Install Node.js (version 16.9.0 or higher)
-
Install dependencies:
npm install-
Create a Discord Bot:
- Go to https://discord.com/developers/applications
- Click "New Application"
- Go to "Bot" section and click "Add Bot"
- Enable "Message Content Intent" under Privileged Gateway Intents
- Enable "Server Members Intent" under Privileged Gateway Intents
- Copy the bot token
-
Configure the bot:
- Open
index.js - Replace
YOUR_BOT_TOKEN_HEREwith your actual bot token
- Open
-
Configure proxies (optional):
- Proxies are automatically loaded from GitHub when you use
.setproxy on - Or manually create
proxies.txtin formatip:port(one per line) - Example:
124.248.168.90:1080 192.168.1.1:9050 - Proxies are automatically loaded from GitHub when you use
-
Configure custom messages (optional):
- Create
messages.txtto customize spam messages - Add one message per line
- Bot will randomly select from your messages
- Example:
Targetted by Hycron You got boomed by Hycron Hycron always on top! - Create
-
Invite the bot to your server:
- Go to OAuth2 > URL Generator
- Select scopes:
bot - Select permissions:
Send Messages,Embed Links,Read Message History - Copy the generated URL and open it in your browser
-
Start the bot:
npm startUsers must be members of the required guild (ID: 1452999261972201637) to use the bot commands.
Admin ID: 986240868761632819 has full access regardless of guild membership.
Display all available commands and usage information.
Start NGL spam.
Parameters:
username: Target NGL usernameduration: Duration in minutes (maximum 5 minutes)
Default threads: 10 Max concurrent tasks: 5 per user
Example:
.ngl john123 3
This will spam the NGL user "john123" for 3 minutes using 10 threads.
Get the bot invite link to add Hycron to other servers.
Admin only command to enable or disable the bot.
Parameters:
on: Enable the botoff: Disable the bot
Example:
.setstatus off
When disabled, all users will see "Hycron bot is now disabled by the owner" message.
Admin only command to enable or disable proxy usage.
When enabled, automatically loads proxies from GitHub (SOCKS4 + SOCKS5 mixed).
Parameters:
on: Enable proxy and load from GitHuboff: Disable proxy (use direct connection)
Example:
.setproxy on
The bot will fetch fresh proxies from:
- https://github.com/monosans/proxy-list (SOCKS4 + SOCKS5)
Admin only command to reload custom messages from messages.txt.
Example:
.reloadmsg
After editing messages.txt, use this command to reload without restarting the bot.
You can customize the messages sent by creating a messages.txt file:
- One message per line
- Bot will randomly select from your custom messages
- Empty lines are ignored
Example messages.txt:
Targetted by Hycron
You got boomed by Hycron
Hycron always on top!
Hycron never stops
You just got Hycron'd
If messages.txt doesn't exist or is empty, the bot uses these default messages:
- "Targetted by Hycron"
- "You got boomed by Hycron"
- "Hycron always on top!"
Use .reloadmsg command (admin only) to reload messages.txt without restarting the bot.
When you run the .ngl command, the bot will reply with a real-time status dashboard showing:
- Target: The username being targeted
- Duration: Total duration in minutes
- Threads: Number of concurrent threads (10)
- Sent: Number of successfully sent messages
- Errors: Number of failed attempts
- Remaining: Time remaining in the session
- Rate: Messages sent per minute
- Proxy: Proxy status (Enabled/Disabled with count)
- Status: Current status (Spamming/Completed)
- Last Error: Most recent error (if any)
The dashboard updates every 2 seconds until the duration expires.
When you use .setproxy on, the bot automatically fetches proxies from GitHub:
- SOCKS5: https://github.com/monosans/proxy-list/raw/refs/heads/main/proxies/socks5.txt
- SOCKS4: https://github.com/monosans/proxy-list/raw/refs/heads/main/proxies/socks4.txt
The bot will:
- Download both SOCKS4 and SOCKS5 proxy lists
- Mix them together randomly
- Use the combined pool for spam sessions
You can also add proxies manually to proxies.txt in the format:
ip:port
Example:
124.248.168.90:1080
192.168.1.1:9050
45.76.123.45:1080
- Automatic SOCKS4/SOCKS5 detection from GitHub
- Round-robin proxy rotation
- Proxy status displayed in dashboard
- Enable/disable via
.setproxycommand - Fallback to direct connection if proxy fails
- Mixed SOCKS4 + SOCKS5 for better success rate
- Uses Discord.js v14
- SOCKS proxy support via socks-proxy-agent
- Implements proper rate limit handling
- 25 second delay on rate limits
- 5 second delay on errors
- Automatic session cleanup
- Multi-threaded concurrent sending
- Guild membership verification
- Admin-only bot control
- Per-user concurrent task limiting
1452999261972201637
986240868761632819
1454157889836028148
- Maximum duration: 5 minutes
- Default threads: 10
- Max concurrent tasks per user: 5
Make sure the following intents are enabled in Discord Developer Portal:
- Message Content Intent
- Server Members Intent
- This bot is for educational purposes only
- Use responsibly and respect NGL's terms of service
- The bot requires Message Content Intent and Server Members Intent to be enabled
- Sessions are tracked per user to prevent conflicts
- Only users in the required guild can use the bot
- Admin can enable/disable the bot and proxy at any time
- Each user can run maximum 5 spam tasks simultaneously
If the bot is not responding to commands:
- Ensure Message Content Intent and Server Members Intent are enabled in Discord Developer Portal
- Verify the bot has proper permissions in your server
- Check that the bot token is correctly set
- Make sure Node.js version is 16.9.0 or higher
- Verify you are a member of the required guild
- Check if the bot is enabled using .setstatus command
- For proxy issues, verify proxies.txt format and proxy availability
ISC