Simple Custom Chat Command Handler

Resources Community Resources
#1

Hey Devs!

I’ve been playing around with the Roblox chat system and built a simple custom command handler to spice up player interactions. It’s a lightweight way to add commands like /wave or /info without needing a full admin system. Sharing it here for anyone who wants to adapt it for their game!

local Players = game:GetService("Players")
local ChatService = game:GetService("Chat")

local Commands = {
    ["wave"] = function(player)
        return player.Name .. " waves at everyone!"
    end,
    ["info"] = function(player)
        return "Player: " .. player.Name .. " | Level: " .. (player:FindFirstChild("leaderstats") and player.leaderstats.Level.Value or "N/A")
    end
}

local function onChatted(player, message)
    if message:sub(1, 1) == "/" then
        local command = message:lower():sub(2):split(" ")[1]
        if Commands[command] then
            local response = Commands[command](player)
            ChatService:Chat(player.Character.Head, response, Enum.ChatColor.Blue)
        else
            ChatService:Chat(player.Character.Head, "Unknown command!", Enum.ChatColor.Red)
        end
    end
end

Players.PlayerAdded:Connect(function(player)
    player.Chatted:Connect(function(message)
        onChatted(player, message)
    end)
end)

This script checks for messages starting with /, grabs the command, and runs a function from the Commands table. For example, /wave broadcasts a wave message, and /info shows player details (assuming a leaderstats setup). It uses the built-in chat system to display responses above the player’s head.

What do you think? I’m considering adding argument parsing (e.g., /give playername item) or cooldowns. Any cool command ideas to share?

How to Use

  • Drop this script into ServerScriptService.
  • Add your own commands to the Commands table.
  • Test with /wave or /info in-game.

Potential Enhancements

  • Add permissions so only certain players can use specific commands.
  • Include command arguments for more complex actions.
  • Log commands to a server console for moderation.
3 Likes
#2

With the new TextChatService, Player.Chatted is not fired on the client for messages sent by said client (but fired for messages by other players?)
dunno if it’s a bug, but if it is, it’s fair to assume it wont ever get fixed at this rate
Now this doesn’t affect your script, since it is server sided, but I’m saying this because, it can easily be modified to work on the client (or it might work without any modifications on the client), and it is very useful to make client sided chat commands. So if you want to improve your resource, that would be a suggestion

Another thing is that ChatService (aka Chat) is deprecated, the new method is TextChatService:DisplayBubble(). Although it is a bit weird to display a bubble for a command responce

Overall, your resource nice, however, I will say it’s not very significative work, I personally don’t care, but some people might criticize your resource because of that>

Looking at your other topics, you posted 5 topics in #resources:community-resources, all in the same hour, all with a very similar format, …
This is quite odd, and I would suggest against doing that

#3

Would it not be better to make this system with the build in command feature from roblox? TextChatCommand | Dokumentation - Roblox Creator Hub

#4

Hey, thanks for the detailed feedback! You’ve brought up some great points, and I appreciate the chance to dig into this a bit more.

You’re totally right about Player.Chatted behaving differently with TextChatService on the client—messages from the local player not firing is a quirky thing, and whether it’s a bug or intended, it’s definitely something to consider. Since my script is server-sided, it sidesteps that issue, but I love your suggestion about adapting it for client-side use. I’ll tweak it below to show how it could work on the client with TextChatService, since client-side commands can be super handy for instant feedback without server round-trips. Good call!

On the ChatService deprecation, yeah, I should’ve flagged that—it’s old news now with TextChatService taking over. Using Chat:Chat() was more of a quick-and-dirty choice for simplicity, but TextChatService:DisplayBubble() is the modern way to go. I agree it feels a bit odd for command responses (bubbles are more NPC-ish), so I’ll update it to use the chat channel instead, which might fit better. Thanks for the nudge!

About the resource’s significance—fair point! It’s a small utility, not a game-changer, and I get how some might see it as lightweight. My goal was just to share a starting point for folks newer to scripting or looking for a quick chat tweak. I’ll beef it up a bit with an extra feature (like argument parsing) to give it more meat—hope that helps it feel less “eh” to critics.

As for the posting spree… oof, you caught me there! I got a bit excited sharing a bunch of ideas at once, and I can see how that looks spammy. I’ll pace myself better going forward—quality over quantity, right? Appreciate the heads-up; I don’t want to come off as flooding the forum.

Here’s an updated client-side version with TextChatService to reflect your input:

local TextChatService = game:GetService("TextChatService")
local Players = game:GetService("Players")

local Commands = {
    ["wave"] = function(player)
        return player.Name .. " waves at everyone!"
    end,
    ["info"] = function(player)
        return "Player: " .. player.Name .. " | Level: " .. (player:FindFirstChild("leaderstats") and player.leaderstats.Level.Value or "N/A")
    end
}

-- Client-side: LocalScript in StarterPlayerScripts
local player = Players.LocalPlayer
local textChannel = TextChatService:WaitForChild("TextChannels").RBXGeneral -- Adjust channel as needed

player.Chatted:Connect(function(message)
    if message:sub(1, 1) == "/" then
        local command = message:lower():sub(2):split(" ")[1]
        if Commands[command] then
            local response = Commands[command](player)
            textChannel:DisplaySystemMessage(response) -- Sends to chat, not a bubble
        else
            textChannel:DisplaySystemMessage("Unknown command!")
        end
    end
end)

This runs on the client, uses TextChatService properly, and skips bubbles for a cleaner chat output. For the server version, I’d stick with the original but swap Chat:Chat() for something like firing a RemoteEvent to the client’s chat channel.

Thanks again for the constructive critique—it’s helped me refine this a ton! Any other ideas for commands or features you’d toss in?

1 Like
#5

Hey, good point! Using TextChatCommand could definitely streamline this—Roblox’s built-in system handles command triggering cleanly with Triggered events and aliases. I went with a manual approach here for simplicity and flexibility (no setup in Studio needed), but you’re right that TextChatCommand would be more robust, especially for bigger projects. I might rework it to use that instead—thanks for the suggestion!

#6

Did you use ai to write your ressources? I wont bash against the use of ai, but the updated code has a lot of very ai like comments, and for some reason it uses LocalPlayer, a client only thing, and now it sends a system message rather than displaying a bubble

Ai creates code that has doubtful quality at best, and so I would discourage posting code written mostly by ai in #resources:community-resources. I would say these topics are spam if they were just made through an ai prompt

1 Like
#7

sos bro i wanna be famous on the forums