The wiki is an invaluable community resource, full of useful and indeed essential information and documentation. However, like what happens to most wikis over time, a lot of this content has become hard to find. Therefore, we are embarking on a simple initiative to help our entire developer community find and access the best and most important resources available to them. We will do this by creating a new page on the wiki that aggregates in one place the most useful links our community relies upon. This will help beginners build their expertise faster, and our more experienced developers navigate to key resources more efficiently.
We need your help
You can help by sharing what resources you feel are the most important and useful to Roblox developers. Consider sharing what pages and resources you have saved as bookmarks in your browser. Share with us not only what pages on the wiki you like, but what pages produced and managed by the community are useful as well.
To help get the ideas flowing, below is a list that contains some of the frequently viewed resources, or that some Roblox Staff members have recommended we add to this page.
I can’t wait to see what people share!
Sincerely,
Byrne Reese
Head of Information Experience
I always use the search function to directly go to the API reference so I can learn more about the methods, events and classes. It’s the most direct way to learn more. Unfortunately, a lot of API reference pages are missing documentation or examples.
I find Extra Credits to be essential when learning game development. Learning how to do stuff is great, but learning when and why to use it is just as important.
The Roblox namespace page is pretty helpful.
It tells you about the Roblox-native Lua APIs and functions that you can directly access from scripts.
When I was an editor on the wiki, I worked really hard to make the API Class Reference a helpful tool for people who are looking for quick information about objects.
It’s not perfect by any means; examples are a bit scarce and it requires some trial and error to make things work right, but I did my best to provide a general idea of what each member does, and to provide some more contextual metadata for organization.
