The reliable way to connect Discord to a RedM server is to treat the bot as two parts of one system: a Discord application with a protected token and intents, plus a RedM resource (or txAdmin) configured with the same guild, role, channel and permission data. For status displays and basic player administration, txAdmin may already be enough because it is included with FXServer. Use a separate resource when you need custom slash commands, Discord-role whitelists, staff-chat forwarding, role-to-ACE mappings or event webhooks.
This guide covers the setup from an empty Discord application to a tested RedM deployment, including least-privilege permissions, role mapping, txAdmin status embeds and recovery steps.
As an Amazon Associate I earn from qualifying purchases.
If you need hosted infrastructure for a RedM server, Godlike.Host provides game-server hosting with its own game panel, SFTP/FTP access, up to three free backups a day with restore, and server management through a Discord bot. It is not on Cfx.re’s list of authorized RedM hosts (redm.net, 10 Oct 2026).
Choose the right integration before installing anything
There are two practical designs. The first uses txAdmin’s built-in Discord integration. The second adds a dedicated RedM resource such as CAS AdminBot. They overlap, but they are not interchangeable.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
| Requirement | txAdmin integration | Dedicated RedM resource |
|---|---|---|
| Server status in Discord | Built-in persistent status embed; configured from txAdmin | Possible when the resource provides status placeholders or messages |
| Basic player administration | Player whitelist and player-information commands are listed as supported | Depends on the resource’s documented commands |
| Custom slash commands | Limited to the commands supplied by txAdmin | Designed for resource-specific commands and moderation workflows |
| Discord-role whitelist | Not the primary txAdmin use case | Can be configured when the resource supports role checks |
| Discord roles mapped to RedM permissions | Requires a separate permissions design | Can automate Discord-role to CFX ACE mappings |
| Staff-chat forwarding and event webhooks | Not the main documented feature set | Available in resources that document staff channels and webhook categories |
| Operational burden | Less software to install, but still requires Discord permissions and txAdmin configuration | Additional token, resource updates, configuration and troubleshooting |
| Deployment risk | Lower when using an existing txAdmin installation | Depends on the resource’s dependencies and configuration quality |
Start with txAdmin if your requirement is a status panel, whitelist command or basic player information. Choose a dedicated resource when the Discord server must drive RedM permissions or when you need custom commands, staff chat, placeholders and event-specific webhooks. You can run both, but document which system owns each command and permission so administrators do not create conflicting rules.
Prepare the RedM and Discord environments
Confirm the FXServer and txAdmin installation
txAdmin is already included with FXServer; it is not installed as a separate resource. The normal getting-started flow is to launch FXServer, link a Cfx.re account, and deploy or select the appropriate server through txAdmin. Identify the actual server-data directory and the server.cfg file before changing anything.
Use an isolated folder for recipe deployments
If you use a txAdmin recipe, match the recipe to RedM rather than assuming a FiveM recipe is suitable. Read the recipe source and every task it performs, check its database and minimum-version requirements, and deploy it to a new or empty target folder first. Keep the production resources, configuration files and databases backed up. A recipe that overwrites an existing deployment can leave a working server unable to start; an isolated test target lets you inspect the result without risking live data.
Collect the identifiers you will need
- The Discord guild (server) ID.
- The ID of any staff-chat or log channel.
- Role IDs for moderators, administrators, founders or whitelist groups.
- The RedM resource folder name and its documented startup entry.
- The CFX ACE group names that should receive mapped permissions.
- Webhook URLs, if your chosen resource supports event logging.
Turn on Discord Developer Mode to copy guild, channel and role IDs. Treat these IDs as configuration data, not as secret credentials; the bot token is the secret that must never be published.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Create the Discord application and bot
1. Create an application
- Open the Discord Developer Portal and choose New Application.
- Give the application a recognizable name, such as the name of your RedM community, and create it.
- Open the application’s Bot page and select Add Bot.
- Copy the bot token once it is generated. Store it in the RedM resource configuration or a protected server convar; do not put it in a public repository, screenshot, support ticket or chat message.
2. Enable only the intents the resource requires
On the bot page, find Privileged Gateway Intents. Enable Server Members Intent and Message Content Intent when the resource documentation requires them. A role whitelist normally needs member and role information; a resource that reads message text needs message-content access. Enabling an intent in the portal is only half of the job: the RedM resource must also request or configure the matching intent. An intent mismatch commonly appears as missing members, empty role data or unavailable message content.
3. Build a least-privilege OAuth2 invite
- Open the application’s OAuth2 URL generator.
- Select the
botscope and theapplications.commandsscope. The second scope is required for slash commands to register. - Select only the guild permissions that the resource actually needs.
- Generate the invite URL, open it while logged into the intended Discord account, and select the correct guild.
- Confirm the bot’s role is placed high enough in the Discord role hierarchy to perform the actions you configured, but not higher than necessary.
Some example instructions use the Administrator permission because it avoids individual permission failures. Administrator grants broad control over the guild and should be treated as a temporary diagnostic shortcut, not a default. Remove it after identifying the specific permissions required, such as viewing channels, sending messages, embedding links, reading message history, managing messages or connecting to voice channels.
4. Protect and rotate the token
Limit access to the configuration file or convar to server administrators and the account that runs FXServer. If the token appears in a repository, log, screenshot or chat, regenerate it immediately in the Developer Portal and update the RedM configuration. A token is equivalent to the bot’s password; changing Discord roles does not invalidate a leaked token.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Install and start the RedM resource
1. Place the resource correctly
Download the resource from its official distribution and place its complete folder in the RedM resources directory. Keep the folder name exactly as the resource instructions specify; the name used in the startup line must match the directory name. Do not remove manifest, configuration, dependency or language files unless the resource documentation explicitly says they are optional.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
2. Add the startup entry
Add the resource’s required startup line to server.cfg, using the documented resource name. If the resource requires a dependency, start that dependency first. Restart FXServer and watch the console for a successful initialization message, missing-file error, malformed configuration error or authentication failure. This article does not claim that any particular third-party resource has been independently tested, so treat the resource’s own release notes and configuration reference as authoritative for version-specific syntax.
3. Configure the core connection values
A resource such as CAS AdminBot documents settings for the Discord bot token and guild ID. Enter the token exactly as issued, without quotation marks unless the configuration format requires them, and enter the numeric guild ID copied from Developer Mode. Restart after editing; many resources read these values only during startup.
Configure Discord features in the resource
The exact key names vary by resource, but the following settings describe the capabilities documented for CAS AdminBot. Use the names and capitalization in your resource’s own configuration file.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Feature | Values to configure | What to verify |
|---|---|---|
| Bot connection | DiscordBotToken and DiscordGuildId |
The process starts without an authentication error and the bot appears online in the intended guild. |
| Staff chat | Enable forwarding and provide the Discord staff-channel ID | A permitted staff message reaches the intended in-game or Discord destination without exposing public chat. |
| Role whitelist | Enable role checking and list the allowed Discord role IDs | A member with an approved role passes the check; a member without it is denied. |
| Slash commands | Enable commands and set moderator, administrator and founder role IDs | Commands appear in the guild and only the intended roles can run privileged actions. |
| Status messages | Set the server name, player-count and invite placeholders provided by the resource | Rendered messages show current values rather than literal placeholder text. |
| ACE mappings | Map Discord role IDs to CFX ACE group names | Joining, leaving or changing a role produces the expected RedM permission result. |
| Webhook logging | Provide category-specific webhook URLs, such as bank, admin or death events | Test events arrive in the intended private log channels and do not contain secrets. |
Keep a written map of each role ID, its purpose and the RedM group it grants. If several roles can grant the same group, record whether that is intentional. Remove stale role IDs when your Discord hierarchy changes.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Map Discord roles to RedM permissions with CFX ACE
CFX ACE supports Discord identifiers as principals. A basic rule has this form:
add_principal identifier.discord:xxxx group.adminReplace xxxx with the identifier format expected by your authentication and replace group.admin with the smallest useful ACE group. Put the rule in the permissions configuration used by your server, commonly server.cfg or an included permissions file, according to your existing layout.
Build the mapping safely
- List the Discord roles that should grant RedM access, from least to most powerful.
- Identify the exact role IDs and the exact ACE group names; spelling and punctuation must match.
- Add one mapping at a time and restart or reload the permission configuration using your server’s normal process.
- Test with an account that has only the intended role. Verify both an allowed action and a denied action.
- Back up the permissions file and record who approved each mapping.
Do not give a general community role an administrative ACE group. Discord membership changes are permission changes in RedM, so audit role membership whenever staff leave, change jobs or lose access. If a resource automatically creates ACE mappings, compare its generated rules with your manually maintained rules to avoid duplicate or contradictory grants.
Use txAdmin for a built-in Discord status embed
For a status panel, txAdmin may remove the need for a custom bot resource. Its documented Discord integration includes a configurable persistent status embed, player whitelist commands and player-information commands.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
- Ensure the txAdmin Discord bot is in the intended guild and can access the target channel.
- Give that bot Send Message permission in the channel where the status should appear.
- In that channel, run
/status add. - Open txAdmin > Settings > Discord Bot and edit the embed’s content and appearance.
- Wait for the scheduled update and confirm the message refreshes every minute.
The status message is a persistent Discord embed that txAdmin updates every minute. If the command is run in the wrong channel, the message is created somewhere administrators are not watching; remove it and repeat the command in the intended channel.
Test the integration before opening it to players
Use a private test channel and a non-production server or maintenance window. Work through this sequence:
- Start FXServer and confirm the resource or txAdmin integration initializes without configuration errors.
- Check the Discord guild member list for the bot’s online status.
- Run a harmless slash command and confirm it appears to authorized staff.
- Test the same command with a role that should not have access.
- Use a test account with an approved whitelist role and one without it.
- Change a test account’s Discord role, reconnect it to RedM and verify the permission change follows the documented refresh behavior.
- Send a staff-chat test and confirm it reaches only the configured staff destination.
- Trigger one safe event for each enabled webhook category and inspect the resulting log.
- For txAdmin, edit the status settings and confirm the embed changes on its next update.
Record the expected result and the observed result for every test. This turns later troubleshooting into a configuration comparison instead of guesswork.
Recommended Free Tools
Troubleshoot common failures
The bot is offline
- Regenerate and re-enter the token if it may be wrong or exposed.
- Confirm the bot application still exists and is enabled in the Developer Portal.
- Check that the resource startup line is present, the folder name matches and dependencies start first.
- Read the FXServer console for a malformed configuration or authentication message.
Slash commands do not appear
- Reinvite the bot with both
botandapplications.commandsscopes. - Confirm the bot is in the target guild and can view the channel where you are testing.
- Restart the resource after changing command settings.
- Check that command registration is restricted to the guild you are testing rather than another guild.
Members or message content are missing
- Enable the required privileged intents under Bot > Privileged Gateway Intents.
- Enable the same intents in the resource configuration when it exposes those switches.
- Restart after changing intents and test with a member whose role data is known.
Whitelist checks or ACE mappings fail
- Verify the guild ID and every role ID; copying a channel ID or a role’s display name will not work.
- Check the Discord identifier prefix and format expected by CFX ACE.
- Check the ACE group spelling and ensure the rule is loaded by the active
server.cfg. - Confirm the test account actually holds the role in the same guild configured for the bot.
- Look for another rule that grants or denies the same permission.
The txAdmin status embed fails
- Confirm the txAdmin bot has Send Message permission in the selected channel.
- Run
/status addin that channel rather than relying on an embed created elsewhere. - Verify the bot can view the channel and that the command is available to your account.
- Open txAdmin > Settings > Discord Bot and confirm the integration is configured for the correct guild.
A recipe damages an existing server
Stop the affected deployment, preserve its logs, restore the last known-good backup and do not rerun the recipe against production. Review every recipe task, satisfy its database and version requirements, and deploy it to a new isolated folder before attempting a migration.
Security and maintenance checklist
- Keep the bot token out of source control, screenshots, paste sites and public logs.
- Use the smallest Discord permission set that supports the resource; avoid leaving Administrator enabled.
- Limit who can edit
server.cfg, resource configuration and permission files. - Back up configuration files and databases before resource, recipe or permission changes.
- Review Discord role membership and role-to-ACE mappings whenever staff responsibilities change.
- Keep webhook URLs private; anyone with a webhook URL may be able to post to that channel.
- Review resource and txAdmin release notes before updating, especially when command registration or intents change.
- Retest whitelist, staff-chat, slash-command, status and webhook paths after every update.
When a custom bot is unnecessary
If the only requested feature is a server status message plus basic whitelist or player-information administration, begin with txAdmin’s built-in integration. It reduces the number of moving parts and avoids maintaining a second RedM resource. Add a dedicated resource only when its additional behavior—custom slash commands, staff-chat forwarding, Discord-role checks, ACE automation, placeholders or event webhooks—solves a requirement that txAdmin does not cover. Keep the two permission models documented separately, and test them together if both are enabled.
