Community chat is starting with a small beta. The idea is simple: ask about a script, get a second opinion on something you're building, or catch up with a creator without leaving Rscripts.
It uses your existing account, so your profile and creator badges come with you. No separate signup.
Public channels and guides are open to read. Posting is invite-only for now. If you have beta access, confirm your email and accept the short chat rules before your first message. Being verified or having a creator badge does not automatically give you beta access.
Look for Community chat in the bottom-right while you're browsing scripts or profiles, or go straight to the chat page. You can look around even if posting hasn't opened for your account yet.
A place to ask, share and hang out
Here's where to start:
- #general for the everyday scripting talk. Say hi, ask what people are working on, that kind of thing.
- #help when a script or executor isn't doing what it should. Include the error and what you're using so people have something to work with.
- #showcase for something you made. Drop your script page and explain what it does.
- #requests when you're looking for a script for a particular game. Be specific about what you want it to do.
- #guides for useful explanations you can come back to. Anyone can read them; approved contributors handle publishing.
You don't need an account to read the public channels. The message box tells you whether posting is available for your account.
The little chat button can preview a recent public message and show new activity. You can hide the message previews if you'd rather keep browsing quietly.
Less guessing about which game you mean
There's a controller button beside the message box. Use it to tag the game you're talking about. People can then narrow the messages on screen to that game, which helps when several conversations are happening at once.
For help and requests, you can also attach the script and your platform. Replies stay with the question, and a resolved question can be marked answered. That makes an answer easier to find after the conversation has moved on.
You can reply to a specific message and use @mentions too. Click someone's name or avatar to visit their profile. If you're using the popup, it closes as you leave, so it won't sit over the profile you just opened.
Keep it small, or give it a whole page
The popup is handy when you're looking at a script and want to ask something about it. You can open it, check the conversation, and get back to browsing.
For a longer conversation, hit the expand icon in the chat header. It opens /chat with the same channel or hub selected, with more room to read and write.
The page keeps your selected channel or hub in the URL. Refreshing stays in the same place, and you can send someone that link to point them to the conversation. Browser Back works between channels as well.
Your script team can have a hub
If you build with other people, a hub puts your team in one place: a public page, a member list, your team's linked scripts and its own chat channels.
You'll find hubs in the chat sidebar. Open one to look around, check its scripts, or follow its updates.
Follow hub is for keeping up with a creator. Apply to team is for people who want to work with them. Following does not make you a team member, and you don't need to apply just to read a hub or hear its news. The owner and hub admins review team applications.
If you have beta posting access and at least one public script on Rscripts, you can open your own hub from chat. Give it a name, add a description, and set up the channels your team needs.
Hub owners and admins can also change its logo. Pick one of the built-in designs or upload your own image.
Orbit
Prism
Signal
Nexus
Vertex
ShiftHub channels are readable by visitors, even when posting is limited to team members. Keep that in mind when deciding what to share there.
Follow the updates you care about
Hub owners and admins with posting access can share announcements and pin a short creator status. Something like "Investigating Android reports after today's update" gives people useful context before they ask the same question again.
Every status shows who posted it and when. After seven days it gets a Not recently checked label, so an old note doesn't look like a fresh confirmation.
Following a hub adds it to your sidebar and turns on creator update notifications. You can mute those updates while keeping the follow, or unfollow whenever you want.
Your badges come with you
Verified, Popular Creator and Mythic Creator badges show beside your name in chat. If you've earned one, people can see it when you join a conversation.
Community Officers get their badge with a Helper label. Hover it to see their rank and XP. That's separate from the Staff label used by site admins, and from hub owner or hub admin roles.
Those badges show what someone has earned on Rscripts. They don't make someone a chat moderator or guarantee that a linked script or download is safe.
A few controls when you need them
Open the menu beside a message or creator update to report it or mute the person. Muting hides their messages and creator updates for you. You can undo it in chat settings.
Reports go to a moderation queue. A message can be hidden while it's reviewed, and the author can ask for a review if it was hidden or removed. Reporting something does not automatically ban its author. Hub owners cannot review reports about their own messages.
The beta also has posting limits and checks for repeated messages, excessive mentions and certain links. If a post is blocked, you'll get a reason and keep your draft. Posting can be slowed or paused while moderators catch up.
Have a look around
Open community chat, read a guide or have a look through the hubs. If you're in the posting beta, share what you're working on or help someone with an error you've seen before.
If something feels awkward to use, tell me in chat or on the Discord. I'm keeping the beta small while we see what works and what needs fixing.