Vacancy Filled
Freelance Roblox horror work centered on pacing, interaction, and atmosphere.
Connected gameplay systems, tightened interaction flow, and helped turn scattered mechanics into a more cohesive playable build.
role
Gameplay Scripter & Systems Collaborator
team size
Small team
updated
2026-04-07
overview
What the project is and why it mattered.
Vacancy Filled is a Roblox horror experience built around tension, timing, and environmental storytelling. My contribution focused on making the underlying gameplay systems dependable enough to support the atmosphere instead of fighting it.
01
Focus
Tension-driven interaction flow
02
Contribution
Reusable Luau systems
03
Availability
Private case study
problem
Horror projects lose their effect quickly when interactions are inconsistent or progression logic breaks tension. The goal was to support a moody experience with systems that felt stable, reusable, and easy for the team to keep extending.
role
I handled gameplay scripting, systems integration, and technical cleanup across shared mechanics. That included connecting independently built features, standardizing how interactions behaved, and supporting the overall gameplay loop as the project evolved.
build details
Stack, constraints, and decisions.
Stack
Constraints
- The project was collaborative, so new systems had to fit work built by other contributors.
- Roblox performance constraints meant keeping logic lean and predictable.
- Atmosphere-first pacing required interactions to feel deliberate instead of over-scripted.
Decisions Made
01
Modularize repeatable interactions
I favored reusable interaction patterns instead of one-off scripts so doors, prompts, and progression beats could share the same logic foundation.
02
Treat tension as a systems problem
Scares only land when triggers, timing, and state changes stay reliable, so the implementation emphasized stable handoffs between mechanics.
03
Optimize for future content drops
The scripting approach aimed to make follow-up scenes and polish passes easier to add without reworking core systems.
outcome
What came out of it.
Outcome
- Delivered a clearer gameplay flow that better supported the project’s horror pacing.
- Reduced friction between independently built mechanics by integrating them into shared systems.
- Left behind reusable scripting patterns that made future iteration easier for the team.
Lessons
- Atmosphere depends on reliability just as much as art or audio direction.
- Reusable systems are especially valuable on collaborative Roblox projects.
- Playtesting is the fastest way to spot pacing issues that are hard to see in code alone.
Next
- Expand progression QA around edge cases and late-scene transitions.
- Add more tooling for fast playtest iteration and tuning.
- Continue polishing encounter timing, onboarding, and environmental feedback.
keep browsing
Keep moving through the archive or reach out if you want to talk through similar work.