thiliestu

I design systems around independent ModuleScripts, registries, packages, and clear entry points. I usually think through how a system should work architecturally before I start implementing it.

A lot of my code is server heavy. I keep gameplay state and important logic on the server whenever possible. Client communication is mainly used to deliver state, events, and presentation data to the client.

Comfortable with typed Luau, ModuleScripts, exported types, metatables, object oriented patterns, and reusable abstractions. I also enjoy building small libraries and wrappers when a project benefits from them.

I use a ProfileStore wrapper as a starting point for my projects and am very comfortable building around persistent player data, profiles, inventories, and other saved state.

I use QuickNet with a centralized NetworkRegistry instead of scattering network instances and identifiers throughout a project. For input, I use my own UserInputService wrapper with filtered signals, bindings, and combo detection.

I am comfortable building systems such as round logic, spectating, (to some extent) combat, dialogue, camera behaviour, and other game specific mechanics. I care about keeping these systems isolated so they remain easier to extend and debug.