Choose your path
A short map of the GankByte ecosystem: games, tools, public projects, contribution rules, and the safest order to begin.
Open developer hub ↗DEVELOPERS // DOCS
Make it clear.
Make it usable.
Practical guides for building, running, debugging, and sharing projects across the platforms GankByte actually talks about. Start with the route that matches what you are making.
Build a resource
Understand resource folders, fxmanifest.lua, client/server/shared scripts, dependencies, commands, permissions, and installation notes.
Open FiveM hub ↗Connect a NUI safely
Keep the browser UI, Lua callbacks, SendNUIMessage actions, manifest files, and asset paths aligned so failures are visible.
Open NUI toolkit ↗Start a Java plugin
Choose a Java version, understand the plugin descriptor, keep dependencies explicit, and prepare a Paper or compatible server build.
Open Resource Bench ↗Start a RuneLite plugin
Use the correct plugin shape, keep configuration and lifecycle code small, and follow RuneLite’s review and publishing rules.
Open Java starters ↗Write maintainable Lua
Use local scope, explicit dependencies, guarded commands, predictable events, and readable configuration instead of hidden globals.
Inspect a Lua resource ↗Build a small utility
Set up a virtual environment, keep configuration outside source, provide a repeatable command, and document the useful path.
Generate a Python starter ↗Use JavaScript well
Keep browser tools local-first, validate user input, show errors clearly, and never claim a browser request can bypass CORS.
Open API Request Builder ↗Change data carefully
Build queries, inspect broad updates, use migrations in order, and protect user data with the correct RLS policies.
Open SQL Builder ↗Prepare a public release
Check documentation, licence, secrets, generated folders, dependencies, and the final file list before sharing a project.
Open release packager ↗Find what is missing
Use the project validator and health scanner to turn vague concerns into file-level findings and practical next actions.
Open health scanner ↗Contribute responsibly
Show what exists, explain ownership, use the right licence, and submit a focused improvement that another person can review.
Read contribution guidance ↗No guide matched that search. Try a platform, language, or tool name.
Need a starting point?
Generate a starter, inspect the result, read the relevant guide, then publish only after you understand every file in the project.
Open Resource Bench ↗