Using StudPilot
Citations and sources
How the agent searches the official Roblox documentation and cites what it used.
Roblox changes. APIs are added, deprecated and renamed, and a model's memory of them goes stale. So rather than relying on what it remembers, the StudPilot agent looks things up while it works, in the official Roblox Creator Documentation, and tells you what it read.
When the agent searches#
The agent searches when a request depends on how a Roblox API, service or feature behaves: the arguments of a function, the limits of a service, the right way to save data, how a property interacts with another. It does not search for things it does not need, so a small change often has no searches at all.
Each search shows in the chat as it happens, with the query and the pages it opened.
How citations appear#
When the summary says something that came from the documentation, it carries a numbered citation like [1]. The numbers link to the exact pages the agent read, listed under the reply. Open them to check the source yourself.
Coins are saved with DataStoreService when the player leaves and on a
60 second autosave, which stays well under the per-key write limit [1].
[1] Data stores, create.roblox.com/docs/cloud-services/data-storesWhy it matters#
- You can check the work. A claim with a source is one you can verify in a click.
- Fewer outdated patterns. The agent builds against the documentation as it is today.
- You learn as you go. The citations are a reading list for the parts of Roblox your game uses.
What it searches#
The agent's searches go to the official Roblox Creator Documentation. It does not cite forums, videos or random websites as sources. When it adapts a model or asset from the Creator Store, the asset's page is linked the same way.