ROBLOX · SYSTEMS · UI · LIGHTING

ROBLOX SYSTEMS

I build the systems a Roblox game runs on: saves that survive a crash, an economy nobody can exploit, combat that feels fair. I also do UI, environment setup and lighting. Priced per package, or by the month.

see the prices ↓

discord is fastest. email works too.

a Roblox avatar in a gold pinstripe admiral suit and orange aviators
roblox.exe — Properties
Status
available · booking october
Packages
from $350
Hourly
$35 / hour
Retainer
$2,400 / month
Mentoring
from $40 / hour
Assets
from $9.99
Reply
within a day, usually less
Timezone
CET · overlaps US mornings
Won't do
3D modelling
01

THE PROOF

what it looks like in a live game
odyssey — adventure RPG tycoon · Roblox
Odyssey dungeon cryptOdyssey tavern interiorOdyssey village
Odyssey underwater zone
Odyssey in Roblox Studio

The character is everything.

Dungeons earn power, relics specialize it, the house amplifies and gates it. Every system answers one question: does this make the character stronger, more unique, or more respected?

  • .LUAU
  • ROBLOX STUDIO
  • IN PRODUCTION
Build progress
systems in · content ongoing

the fun part
↖ this one

ALSO IN MOTION

Beyond Odyssey

Systems from other games, recorded in play. Swipe through them, or pick one off the playlist.

4 clips · 2:12 · jump to the player ↓

kodo media player — combat-showcase.mp4
  1. combat & abilitiesbetter with sound. click the speaker
  2. round loop
  3. sailing ships
  4. everything else
01 / 04now playing

combat & abilitiesconfig-driven abilities, server-side hit validation

playlist4 clips · 2:12

0:37 · loopingswipe, or use ← →
02

HOW I BUILD

the rules first, then the code that follows them
rules.txt — Notepad

  1. the server decides

    clients ask, the server checks. prices, damage, loot and cooldowns are computed and validated on the server. a remote is a request, never a command.

  2. data doesn't get lost

    session-locked saves, retries with backoff, a save on shutdown, versioned schemas with migrations. a lost save is the fastest way to lose a player.

  3. config over code

    every number a designer might tune lives in a config module. balancing a sword shouldn't need a scripter.

  4. everything cleans up

    every connection, instance and thread has an owner that destroys it. no leaks on respawn, no server that gets slower every hour.

  5. strict types

    --!strict Luau and typed module APIs, so mistakes show up in Studio instead of in a live server.

  6. measure, then optimise

    microprofiler before any rewrite, and a budget for every remote. readable code unless the profiler says otherwise.

Ln 6, Col 1 · sorted by what it costs you when it's broken
kodo_systems — Explorer

code samples are being cleared to leave the studio. ask on discord and i'll walk you through them.

03

THE LOOK

UI, environments and lighting · no modelling
tavern_lighting.png
Odyssey tavern interior, lit by a fireplace and sun through a window
  1. fireplace: warm point light, the room's anchor
  2. sun through the window: a cool fill against the warm fire
  3. beam shadows give the flat wall its shape
  4. chandelier: soft top light so the ceiling doesn't go black
4 note(s) · annotated
01 · LIGHTING

light that tells you where to go

lighting is the first thing players notice about a place. warm where they gather, cold where they shouldn't stay long.

how i do it · 5 stepsless
  1. mood and time of day first, from one reference image and one palette.
  2. future lighting, a sun that throws readable shadows, atmosphere for depth.
  3. local lights only where they matter: fire, windows, doorways.
  4. colour correction and bloom last, tuned per zone so each area feels different.
  5. checked at graphics level 1 and on a phone.
village_setup.png
Odyssey village with a windmill, timber houses and a stone bridge
  1. landmark: the windmill is visible from the whole village
  2. the bridge leads the eye, and the player, into town
  3. houses frame the path instead of blocking it
  4. foliage softens the edge and hides the map border
4 note(s) · annotated
02 · ENVIRONMENTS

a map you can read at a glance

i don't model. i take your models or licensed packs and place them so the world makes sense as soon as you spawn.

how i do it · 5 stepsless
  1. blockout first: paths, sightlines, and what the player sees when they spawn.
  2. landmarks you can navigate by, visible from anywhere on the map.
  3. dressing in layers: big shapes, then props, then the small details.
  4. a part and streaming budget, so it still runs on a phone.
  5. collisions and invisible walls tested by actually playing it.
party_ui.png
Odyssey's party screen: the dungeon the crew is sailing to, a server player list with invite buttons, and crew cards with ready states
  1. one next step: the button says what it's waiting on
  2. the server list: level, rank, where they are
  3. every slot has a state and its own action
  4. crew cards: gear, rank and ready at a glance
4 note(s) · annotated
03 · UI

UI nobody needs a tutorial for

built in roblox, scaled for every screen, and wired to the systems behind it, so it never shows a number the server disagrees with.

how i do it · 5 stepsless
  1. layout in scale, not offset, with aspect-ratio constraints, so it works on a phone and on a 4K monitor.
  2. one component per element (button, card, bar), reused everywhere so it stays consistent.
  3. tweens for feedback, so every click gets a response.
  4. the UI is a view: it reads state from the systems and never decides anything itself.
  5. tested in the device emulator at every screen size before it ships.
04

WHAT THEY SAY

in their words, posted with their ok
  • #vouches — Discord
    Azv
    AzvJB
    “Working with Kodo is an absolute breeze. Finding a developer who brings ideas to life with flawless execution and zero hassle is rare. He works exceptionally fast, handles complex logic without breaking a sweat, and keeps communication clear and professional from start to finish. I can't recommend him enough to any team looking for top-tier quality.”
  • #vouches — Discord
    Niki
    NikiAV8R
    “Kodo is one of the best scripters I've worked with. He's really good at what he does, and really fast, everything is done by the deadline or even faster. Also, unlike other scripters, he doesn't complain about the workload and does what needs to be done. I'm glad I have the pleasure of working with him.”
05

PACKAGES & PRICES

fixed price for fixed scope · hourly or monthly for everything else
  • system.pkg

    ONE SYSTEM

    $350 fixed

    one self-contained system, dropped into your game and wired to what's already there

    INCLUDES
    • server-authoritative, validated remotes
    • tuning numbers in a config module
    • saves through your data layer (or a small one)
    • 1 round of revisions
    • 7 days of bug fixes after handoff

    e.g. shop, daily rewards, inventory, codes, quests, round timer, leaderboards

    3–7 days
  • core.pkg

    GAME CORE

    RECOMMENDED

    $1,750 fixed

    the base every game needs before content goes in. it's the part that costs the most to redo later

    INCLUDES
    • session-locked saves with schema migrations
    • economy: currency, shop, dev products done right
    • the main loop: rounds, lobby, or tycoon progression
    • anti-exploit baseline on every remote
    • admin + debug commands for your team
    • 2 rounds of revisions · 14 days of fixes

    e.g. a new game from an empty baseplate, or replacing a core that keeps losing data

    2–4 weeks
  • launch.pkg

    LAUNCH BUILD

    $2,500 / month

    game core plus the gameplay systems, built through to a public launch. it takes months, so it's billed monthly

    INCLUDES
    • everything in game core
    • gameplay: combat & abilities, or your genre's equivalent
    • matchmaking / teleports between places
    • UI designed, built and wired to the systems
    • analytics events for retention + monetisation
    • 30 days of launch support

    e.g. RPGs, fighting games, simulators, round-based games

    billed monthly · usually 2–3 months
rates.exe — ongoing work

MONTHLY RETAINER

$2,400 / month

a scripter on your team without hiring one. the best fit for games that keep shipping updates.

  • ~20 hours a week, booked
  • weekly builds you can play
  • your messages first
  • two weeks' notice to stop

HOURLY

$35 / hour

bug fixes, performance passes, and rescuing a game someone else started.

  • 2 hour minimum
  • billed in 30 min blocks
  • a short audit before any big fix
for work that doesn't fit in a box
  • USD
  • PAYPAL · WISE
  • YOU OWN THE CODE

not sure which one fits? send me the idea on discord and i'll tell you. sometimes none of them do, and that's fine.

06

ASSET SHOP

ready-made, straight into studio · more coming
kodo_assets — Shop
A stylised sailing ship with a blue emblem sail on the water in front of a harbour town
  • SCRIPTED
  • SYSTEM
  • NEW

Sailing Ship System

$9.99

a scripted sailing ship, not just a model. it drives, heaves on the water, and keeps your players standing on the deck.

WHAT YOU GET
  • the ship, script-driven and steered standing at the helm (no VehicleSeat)
  • heave, pitch and roll from layered noise waves, plus lean on acceleration and turns
  • players stick to the moving deck, so they can walk around while it sails
  • crash sensors: raycast hits stop the ship, with sound and camera shake nearby
  • speed, turn rate and wave height tunable as attributes, no code edits
  • engine sound and effects that follow the ship's speed
1 item(s) · use it in as many of your games as you like, commercial ones too. don't resell or re-upload the asset itself.

no checkout yet. the buy button copies a message: send it to me on discord and i'll send the file.

07

HOW IT GOES

from the first message to the handoff

  1. you message me

    the game, the system you need, a deadline and a rough budget. the brief below has the lines.

  2. scope & quote

    within a day: a written list of what's in and what's out, and a fixed price or an hour estimate.

  3. built in your place

    team create or a rojo + git repo. something you can playtest every few days, not a month of silence.

  4. handoff

    clean, typed code, the config explained, short notes for the next scripter, then the bug-fix window.

terms.ini
Payment
50% to start, 50% on handoff
Launch build
billed monthly, up front
Ownership
yours once it's paid in full
NDA
happy to sign yours
08

QUESTIONS

the ones that come up every time
do you do modelling?

no. i do UI, environment setup and lighting with your models or licensed packs, but i don't make the 3D models themselves.

can you work on a game that already exists?

yes. start with a code audit or a few hourly fixes, so you know what's worth fixing and what's worth replacing before bigger money goes in.

team create or rojo?

either. for anything bigger than one system i'd suggest rojo + git, so every change has history and nothing gets overwritten.

what if the scope changes halfway?

small changes get absorbed. bigger ones become a new line in the quote before i build them, so there's no surprise bill.

who owns the code?

you do, once it's paid in full. nothing written for your game ends up in someone else's.

do you teach beginners?

yes, if you've written some Luau already. mentoring works best once you can read a script. if you're starting from zero, go through the free roblox docs first and then come back.

can i pay in robux?

not right now. USD through PayPal or Wise.

09

HIRE ME

discord is the fastest way in
kodo — Discord
STEP 1 · ADD ME

add me on discord and send the brief: copy it, fill in the blanks, paste it. i reply within a day.

tskender_
STEP 2 · SEND THE BRIEF
hey kodo,
game: (name + link, or 'not out yet')
genre: 
what i need: 
package: (one system / game core / launch build / retainer / hourly / UI / lighting / environment / mentoring / audit / not sure)
deadline: 
budget:
tskender_ · online · replies within a day