DiscordDevelop the skills. Bring a working project.
Frontrunners connects developers, scripters, project owners and creators preparing for the opportunity around GTA VI. You can start with existing FiveM tools, web software and community workflows. A working demo and a clear explanation make your introduction useful today.
Updated October 13, 2026. This is a learning and collaboration guide. It does not announce a GTA VI scripting API, supported RP platform, creator payouts or available jobs.
Can you start GTA 6 scripting now?
The practical route is to learn transferable skills using documented platforms available now. GTA V/FiveM resources are not GTA VI resources, and compatibility is not established merely because a language is the same. Check official announcements before promising a buyer a GTA VI integration.
Read Rockstar's GTA VI page for game announcements and FiveM's scripting introduction for the existing FiveM platform. The FiveM runtimes documentation explains current scripting options.
Choose one useful first build
- A FiveM learning resource: in your own test environment, make one small server-validated interaction. Document setup, permissions and the acceptance check. Don't call a chat command a finished commercial resource.
- A creator review tool: use a video you own to test timestamped edit feedback. Start with two reviewers and one clip. Verify that private work stays private.
- A community workflow: prototype an event intake or onboarding checklist using test data. Handle errors and document what still needs a human.
- A project interface: turn an owner's confusing brief into a working, accessible mockup. Show both the normal path and a failure state.
Select a problem you can observe. Ask who experiences it, what they currently do and how they will decide your work helps. Start small enough to finish and explain.
Use AI as a technical partner
Give the model a written task, relevant documentation, a small set of files and a definition of finished. Ask for the assumptions before the patch. Run the result yourself and inspect errors rather than accepting a confident explanation.
- Define inputs, outputs, permissions and failure behavior.
- Ask for a small change you can inspect. Keep a versioned checkpoint.
- Run meaningful tests, including invalid input and unauthorized actions.
- Explain the code back without the model. If you cannot, revisit that part.
- Record model-generated dependencies and verify the real package and documentation before installation.
For game resources, clients can send incorrect or hostile values. Learn why important state and permission checks belong on the server. For web tools, learn authentication, authorization, input validation and deployment basics before handling customer data.
What to put in your portfolio
Show the problem, a short working demonstration, the code or an appropriate explanation, what you personally built, how it was tested and what remains unfinished. Use your own or permitted material. A learning project is useful evidence when it is honestly labelled.
An owner should be able to tell which platform runs it today, how to try it, what breaks it and what support you are offering. Don't publish credentials, private customer information or code you do not have permission to share.
Find people through the work
Introduce your work, share one specific request and read the community's rules before posting. Offer a reproducible answer or a useful demonstration in the relevant forum. Do not mass-DM unrelated owners.
If you need a developer, write a project brief. If you are still learning, label it as a learning experiment. Membership is free; it does not guarantee employment or a match.