Anime Aura RNG
RNG progression, aura-style collection, inventory handling, and live-game iteration.
Open Roblox pageApplication portfolio / Roblox scripter program
Backend systems live Roblox games depend on.
I build server-first Luau systems for combat, boss AI, abilities, RNG progression, ProfileStore/DataStore layers, economy, reactive UI, live events, and messy codebase cleanup.
Studios
Sam Studios, SyndicatedBuilders, Exchange Creator, DT Studios
Owned projects
2 commercially sold Roblox games
Availability
Full-time or scoped weekly updates
Specialty
Turning unstable systems into maintainable ones
What I actually do
I join where Roblox projects usually get painful.
Live games rarely arrive clean. I can pick up unfinished or messy code quickly, trace the real gameplay path, fix unstable systems, and leave the code easier to extend.
My strongest area is backend development, but I also wire the frontend when the player experience depends on server state, cooldowns, rewards, inventory, quests, shops, or live events.
Case files
Published games, framed by what they prove.
The point is not just that the games exist. The point is that the work covers real production surfaces: data, state, UI, economy, combat, progression, and weekly shipping.
Featured live game
Open Roblox page
Ultimate Card Battle
Card RNG, duel flow, raids, progression, inventory, limited-time surfaces, backend state, and UI connected to gameplay systems.
Role
Backend / gameplay systems
Proof
RNG, raids, duel requests, live panels
Risk handled
Client/server state and reward correctness
An Average Tycoon Anniversary
Tycoon support, update work, retention systems, and production scripting.
Open Roblox pagePush a Car
Progression, player loops, rewards, and live update scripting for simulator gameplay.
Open Roblox page+1 Muscle to Push Cars
Progression tuning, reward flows, pets, UI hooks, and game-loop polish.
Open Roblox page
Private / unreleased
I have also contributed to unreleased studio projects, including backend systems, combat support, gameplay architecture, and cleanup work that cannot be shown publicly. References, buyer context, or deeper attribution can be shared after an intro call.
Technical receipts
How the work usually breaks down.
These are the system surfaces I expect to own, debug, or clean up when joining a Roblox project.
Combat, boss AI, NPC logic
Cooldowns, targeting, animation support, VFX/SFX hooks, validation, and tuning surfaces.
client intent -> server validate -> replicate result
Gacha, RNG, unlock paths
Roll loops, pity-style logic, rewards, inventory grants, retention hooks, and player feedback.
roll -> reward resolve -> inventory grant -> UI sync
Data, inventories, economy
ProfileStore/DataStore layers, item ownership, currencies, safe save boundaries, and recovery-minded design.
profile load -> mutate safely -> reconcile -> save
Cross-server events and updates
MessagingService and MemoryStore patterns for events, announcements, timed content, and coordination.
publish event -> memory lock -> server fanout
Footage deck
Short proof clips with clean thumbnails.
Duel / UI
Duel flow and reactive state
Request handling, multiplayer state, roll flow, UI feedback, and backend responses.
RNG / onboarding
Roll prompt and raid navigation
Quest prompts, roll actions, raid entry points, and client presentation around server state.
Combat sandbox
Boss ability testing
Ability tuning, cooldown state, animation/VFX support, and debug surfaces for boss work.
Simulator loop
Progression and rewards
Currency, upgrade, roll, inventory, and reward feedback inside a live game loop.
Retention
Daily login panel
Timed claims, reward locking, UI state, and returning-player retention support.
Update work
Weekly update workflow
Fast Studio iteration, progression tuning, pet/reward surfaces, and commission delivery.
UI surfaces
Player-facing systems need reliable state underneath.
The assets are visual, but the important part is what feeds them: cooldowns, rewards, boss health, quest progress, roll state, and player inventory.
Toolchain
Comfortable in external workflows.
I normally work through VS Code and can adapt quickly to studio-specific toolchains.
- Typed Luau and --!strict
- Clean module boundaries
- Debuggable architecture
- Roblox APIs and server boundaries
- ProfileStore / DataStore layers
- Inventory, economy, rewards
- VS Code, Git and Rojo
- Darklua, Selene, Rokit
- Pesde, Just and Zune
- Blink-style networking patterns
- MessagingService
- MemoryStore coordination
Currently ramping on Charm state and ByteNet. I learn new frameworks quickly when the project needs them.
Work modes
Clear ways to hire me.
USD pricing for remote Roblox systems work. Best fit: serious long-term projects, live games, update pipelines, and backend-heavy ownership.
Monthly systems work with a small percentage of the game.
- Systems ownership
- Live-game support
- Long-term maintainability
- Best for shared upside
Monthly work without percentage.
- Fixed monthly cost
- Backend and gameplay systems
- Update pipeline support
- Best for predictable budget
Scoped commission work for weekly live-game updates.
- One scoped update
- Bugfix pass
- Integration support
- Best for live content cadence
Commission menu
Scoped systems starting points.
These are example starting prices for defined systems. Final scope depends on requirements, integration depth, existing code quality, and how much UI/backend support is included.
Final checkpoint
Ready to ship systems for live Roblox games.
Available for full-time studio work, backend-heavy game systems, codebase rescue, and weekly update commissions.
Roblox
Yahito0
Open profile search
Working context
Remote / full-time / weekly updates
English and Portuguese, Europe/Paris timezone