What is rem-aio?

REM All In One Bot is a single Discord bot meant to replace several separate bots at once. It bundles moderation, security, music, tickets, welcome messages, games, and general utilities into one package, and everything is controlled through soft pastel visual panels using Discord's newer Components V2 interface, so setup and everyday use stay in one clean place instead of spread across many bots. Getting started means installing the Python dependencies, copying the example environment file to your own .env file, adding your Discord bot token, and running the main script. The bot needs the Message Content and Server Members intents turned on in the Discord Developer Portal, plus a token, an owner user ID, and an optional command prefix in the environment file. On the security and moderation side, it offers an anti nuke system meant to block mass destructive actions before they spread, automatic moderation for spam, all caps messages, links, and invite links, a night mode and emergency lockdown for dangerous permissions, and standard actions like ban, kick, timeout, warn, jail, purge, and message snipe, along with whitelist, blacklist, and ignore lists. For music, it plays audio through a Lavalink server accessed via the Wavelink library, with player, search, and queue displays, plus loop, shuffle, autoplay, and volume controls, all through simple text commands like play, search, nowplaying, and queue. Lavalink connection details are optional environment settings, and the bot needs a full restart after changing them. Beyond that, it covers server management tools such as tickets, giveaways, logging, welcome messages, automatic roles, vanity roles, an invite tracker, and reaction roles, plus fun features like chess, Wordle, 2048, rock paper scissors, blackjack, an optional AI chat feature that needs its own API key, translation, QR codes, maps, and stats. Running it requires Python 3.11 or newer, a Discord bot token, and the two intents mentioned above, with Lavalink only needed if you want music. Giving the bot Administrator permission is the simplest option, though you can instead grant only the specific permissions each feature needs. The most sensitive security commands are restricted to the bot owner, admins, or specifically trusted bypass users. The project is released under the MIT License.