Security comes first
Discord permissions, server checks, event handling, and private data are reviewed before a feature is considered finished.
R&J Development is a FiveM and Discord development studio started by two friends who got tired of jumping from server to server. We learned by fixing our own problems and building the tools we wanted to use.
Everything we make starts with a real problem. We care about reliable code, clear support, safer systems, and fixes that people can actually follow.
We work with QBCore, QBOX, ESX, and standalone resources.
We do more than add features. We test our work, look for weak spots, and write down the fixes so the same problem is easier to solve next time.
Right now we work on:
Tickets, applications, server information, and staff tools organized into one system for our community.
The steps that fixed a twenty to thirty minute startup delay, high resource use, and a broken menu.
Open roles and verified applications, connected directly to Discord.
Useful fixes and walkthroughs, written in plain language and available without a required login.
Good work should solve the problem, be safe to use, and make sense when you need help with it later.
Discord permissions, server checks, event handling, and private data are reviewed before a feature is considered finished.
Our bots, FiveM work, and guides come from problems we have dealt with in real communities and real client setups.
We explain what caused a bug, what changed, and what to check next instead of handing over a mystery fix.
Questions stay clear and practical. If something is outside our experience, we would rather say that than waste your time.
Quick answers about our Discord bots, FiveM client fixes, security work, and support.
We build Discord bots and community tools, work on FiveM resources, investigate FiveM client bugs, and publish fixes for problems we have confirmed ourselves.
Yes. We can plan a bot around the way your community works, including tickets, applications, staff tools, moderation, logging, and other server features. Access checks and private actions are handled on the server.
We focus on problems we can reproduce and test, such as startup delays, broken menus, configuration problems, high resource use, crashes, and resource compatibility issues.
We treat browser input, Discord interactions, forms, links, and API requests as untrusted. Sensitive actions are checked again on the server, secrets stay out of public files, and access is limited to the people who need it.
We work with QBCore, QBOX, ESX, and standalone resources. Exact support depends on the resource and the problem, so we confirm compatibility before making promises.
Those are our main areas right now, but we also work on websites, documentation, dashboards, and practical tools that support the same communities.
Start with the available guide or application page and include the exact problem, what you already tried, and any safe error details. Never send passwords, bot tokens, tunnel tokens, or other secrets in a support message.
We keep improving active projects when we find bugs, security issues, compatibility problems, or useful changes. Update details depend on the project.
“Build the thing. Test it properly. Write down what worked.”
Built from real needs, improved through real use.