- 🔋 Battery optimization kills processes frequently
- 📱 Background restrictions prevent 24/7 operation
- 📶 Unstable connections due to mobile network switching
- 🐌 Performance issues on lower-end devices
- ❌ Cannot run 24/7 reliably
- 🧪 Testing and development only
- 🕒 Temporary/short-term usage
- 📚 Learning and experimentation
- VPS Hosting (DigitalOcean, Vultr, Linode) - $3-8/month
- Cloud Servers (AWS, Google Cloud) - Pay-as-you-use
- Dedicated PC/Server - Always-on reliability
Bottom Line: Use Android for testing, get VPS for serious protection!
- Android 7.0+ (Android 9+ recommended)
- 2GB RAM (4GB+ for better performance)
- 3GB free storage
- Stable internet (WiFi strongly preferred)
- Termux app (terminal emulator)
- Android 11+
- 4GB+ RAM
- Fast processor
- Always plugged in
-
F-Droid (Safest Option):
- Download F-Droid: https://f-droid.org/
- Search for "Termux" in F-Droid
- Install Termux
-
GitHub (Alternative):
- Visit: https://github.com/termux/termux-app/releases
- Download latest APK (arm64-v8a for most devices)
- Install the APK
-
⚠️ Avoid Google Play Store:- Play Store version is outdated
- Missing many features
- Use F-Droid or GitHub instead
- Open Termux after installation
- Grant storage permissions when prompted
- Allow notifications access
pkg update && pkg upgrade -ypkg install -y git nodejs npm python curl wgettermux-setup-storagenode --version && npm --versioncd ~ && git clone https://github.com/faiz4sure/vantrix.git && cd vantrixls -lanpm install# Clear cache and retry
npm cache clean --force
npm install --no-optionalnpm list --depth=0nano config.ymlselfbot:
token: "YOUR_DISCORD_TOKEN_HERE" # Get from docs/Get_Token.md
server1_id: "YOUR_SERVER_ID" # Right-click server > Copy ID
owner1_id: "YOUR_USER_ID" # Right-click profile > Copy ID
antinuke_settings:
punishment: "ban" # ban, kick, or none
auto_recovery: true # Enable recovery features
vanity_reversion:
password: "YOUR_DISCORD_PASSWORD" # Required for vanity protection
fallback_vanity: "yourserver" # Backup vanity code# Reduce resource usage for mobile
antinuke_settings:
auto_recovery: false # Disable to save resources
recover_channels: false
recover_roles: false
logs:
log_level: "error" # Reduce log verbosity
log_owner_dm: false # Disable DM notifications- Press
Ctrl + X - Press
Yto confirm - Press
Enterto save
node index.js- Try changing a role in your server
- The bot should detect and respond
- Check logs for activity
pkg install -y screen && screen -S vantrixnode index.js(Detach: Ctrl + A, then D | Reattach: screen -r vantrix)
nohup node index.js > bot.log 2>&1 &ps aux | grep nodetail -f bot.log# Basic background (less reliable)
node index.js &- Android Settings → Apps → Termux
- Battery → Don't optimize
- Background app refresh → Allow
- Data usage → Unrestricted
# Prevent sleep (use carefully)
termux-wake-lock
# Release when done
termux-wake-unlock# Check memory usage
free -h
# Monitor processes
top
# Check CPU usage
ps aux# Reinstall dependencies
rm -rf node_modules package-lock.json
npm install- Double-check your token in config.yml
- Get fresh token using docs/Get_Token.md
- Ensure no extra spaces
# Fix permissions
chmod +x index.js
termux-setup-storage- Use
screenornohupfor background - Disable battery optimization
- Keep device plugged in
- Use WiFi instead of mobile data
- Reduce logging level to "error"
- Disable auto-recovery features
- Close other apps
- Switch to WiFi
- Check internet connection
- Restart Termux
# In config.yml, use these settings:
antinuke_settings:
auto_recovery: false # Saves memory
recover_channels: false # Reduces operations
recover_roles: false # Less processing
member_update_limit: 3 # Lower threshold
logs:
log_level: "error" # Less logging
log_owner_dm: false # No DM spam# Check system resources
termux-info
# Battery status
termux-battery-status
# Network info
termux-telephony-deviceinfo- 1GB RAM, 1 vCPU, 25GB SSD
- Global data centers
- One-click Node.js setup
- 512MB RAM, 1 vCPU, 10GB SSD
- High-performance SSD
- Multiple locations
- 1GB RAM, 1 vCPU, 25GB SSD
- Excellent support
- Easy scaling
- 2GB RAM, 1 vCPU, 20GB SSD
- Great value for money
- Reliable performance
- 2 AMD-based VMs, 1GB RAM each
- Limited but sufficient for light usage
- $300 credit for 90 days
- Full access to powerful infrastructure
# Check running processes
ps aux | grep node
# Kill bot process
pkill -f "node index.js"
# Restart bot
cd ~/vantrix && node index.js
# Check disk usage
df -h
# Check memory
free -h
# Send notification
termux-notification -t "Vantrix" -c "Bot is running"# Edit config
nano config.yml
# View logs
tail -f logs.txt
# Backup config
cp config.yml config.backup.yml- Never share config.yml
- Use environment variables:
export DISCORD_TOKEN="your_token_here"
# Then modify index.js to use process.env.DISCORD_TOKEN- Use WiFi for sensitive operations
- Avoid public WiFi
- Consider VPN for extra security
- Support Server: https://discord.gg/NUPbGzY8Be
- GitHub Issues: https://github.com/faiz4sure/vantrix/issues
- Developer:
faiz4sure
- Check this guide thoroughly
- Try troubleshooting steps above
- Provide error logs when asking
- Mention you're using Android/Termux
- Selfbots violate Discord's Terms of Service
- Account termination is possible
- Use alternate accounts only
- Android will interrupt the bot frequently
- Battery drain will be significant
- Network issues are common
- Not suitable for critical protection
- ✅ Testing new configurations
- ✅ Learning how Vantrix works
- ✅ Temporary protection (few hours)
- ✅ Development and debugging
- ❌ 24/7 server protection
- ❌ Critical security operations
- ❌ Production environments
- ❌ Important Discord servers
- Choose a VPS provider (see recommendations above)
- Install Ubuntu/Node.js on your VPS
- Copy your config.yml to the VPS
- Run:
npm install && node index.js - Enjoy 24/7 protection!
Remember: Android = Testing, VPS = Production! 🛡️