Roblox Scripter Portfolio: What to Include (With Examples)

A Roblox scripter portfolio needs exactly four things: named systems per game, not a vague "worked on it" credit; links to the live games where those systems actually run; one or two code samples a reviewer can actually read; and a visible rate. That's the whole list. Everything else — banner design, testimonial quotes, a long bio — is decoration that doesn't move a hiring decision one way or the other. A studio lead skimming a Discord portfolio channel is deciding in seconds whether you're worth a reply, and those four things are what that decision actually runs on.

Name the systems, not the game

"Scripted [Game Name]" tells a hirer nothing, because it could mean anything from a full backend to a single tweak to an existing script. The version that actually works names the system: "built the wave-spawning and pathfinding for [Game Name]" tells a reviewer exactly what you can do and gives them something specific to verify against the game itself. This is the scripter-specific version of the same principle that applies to every Roblox portfolio — systems, not vibes — but it matters more here, because "scripting" covers everything from combat logic to DataStore persistence to UI wiring, and a hirer filtering for one of those needs to know which one you mean without asking.

Compare the two directly:

Weak:"Scripted a tower defense game."
Strong:"Built the wave-spawning, enemy pathfinding, and tower-targeting system for a tower defense game with 40,000+ visits."

The strong version is checkable. A reviewer can open the game, watch the waves spawn and the enemies path around towers, and confirm the claim in under a minute. The weak version asks for trust with nothing to verify it against, and most reviewers will simply move to the next link in the scroll rather than ask you to clarify.

Code samples that help instead of hurt

One small, complete, commented module beats a folder of a dozen half-finished snippets. A reviewer who opens your code isn't trying to read your whole project — they're trying to answer one question in under a minute: does this person write code a team could actually work with? A single module that solves one real problem end to end answers that question. Ten disconnected fragments, each missing the context that would make them make sense, don't.

What reviewers actually look for is narrower than most scripters expect. They check naming — do variables and functions describe what they hold and do, or are they abbreviated to the point of requiring guesswork? They check structure — is the module organized into functions with a clear responsibility each, or is it one long block that does everything in sequence? And they check for obvious leaks — unbounded tables that grow forever, connections that are never disconnected, loops with no exit condition. None of this requires your best-ever code. It requires code that shows you understand the difference between a script that works once on your machine and one that survives being read by someone else.

Host it somewhere a link can point straight to the code: a public GitHub repository if you have more than one sample worth sharing, or a single Gist if it's just one module. Either way, link it directly from your portfolio rather than describing it in prose — "I write clean code" is a claim, a linked file is proof.

Proof beats claims

The same rule that applies to every part of a Roblox portfolio applies hardest to scripting, because scripting work is the least visible from the outside: a linked live game with a real, current visit count is something a hirer can go check themselves in seconds. A claimed number with no link attached is not, and a careful hirer will treat the unlinked claim as worth nothing rather than take it on faith.

Verified contribution attestations raise the bar past even a linked game. An attestation is a named teammate — someone who was actually on the project with you — confirming that you built the specific system you say you built. That single confirmation changes the trust calculus completely, because it's no longer just you describing your own work; it's a second person, whose name is also on the line, backing the exact claim. See the full portfolio guide for how proof-over-polish plays out across a whole profile, not just the code section.

Rates on the page

Hirers filter by budget before they filter by anything else. A visible "from $X/hr" — or a flat range for common request types — does the prefiltering for you: someone with a $50 budget and someone with a $3,000 budget can each decide whether to message you before either one sends a DM, instead of after. Leaving rates off the page doesn't get you more inquiries, it gets you more mismatched ones, and every one of those costs you a round of back-and-forth that ends in a no.

For what scripters actually charge by seniority and request type, see the commission pricing guide — use it to set a number you can defend rather than guessing at one.

A worked example

Picture a strong scripter profile on Roport, top to bottom. The headline reads "Scripter — combat systems, backend, and DataStore persistence," stating the role in the first line, not buried in a paragraph. Below it are three games, each with a named system: "built the matchmaking and round logic" on one, "built the inventory and trading system with server-side item validation" on another, "built the boss AI and phase transitions" on the third — each game linked, each showing a real visit count pulled live rather than typed in by hand. One of the three has a teammate attestation confirming the claim next to their own name. Below the games sits one pinned code sample link — a single commented module, not a dump of files — and a rate card reading "from $25/hr" with a short note on typical turnaround. A hirer scrolling past this profile has everything they need to decide whether to reach out before they've spent thirty seconds on it, which is exactly the point.

Build that same structure on your own profile at Roport — named systems, linked games, one code sample, and a rate on the page.