C:›Users›Eclipted›portfolio›index.tsx

workspace online · building & operating digital projects

Developer focused on systems that work.

I design and build game-server systems, automation, web tooling, and infrastructure — from the first prototype through real-world operation.

View selected work ↘ What I work on

Game SystemsCustom mechanics, plugins, events and server logic

AutomationBots, workflows, integrations and moderation tooling

Web ToolsDashboards, control panels and practical interfaces

InfrastructureDomains, proxies, deployment and service operations

src/projects

Projects built around real use.

A selection of the kinds of systems I build and operate. Details stay intentionally high-level so the portfolio remains public without exposing private infrastructure or personal information.

‹ ›

C#GameRuntime.cs×

— □ ×

1
2
3
4
5
6
7

public sealed class GameRuntime
{
    public void Initialize()
    {
        Roles.Register();
        Abilities.Initialize();
    }
}

⌘ mainLn 4, Col 5Spaces: 4C#UTF-8

Custom game-server experiences

Server-side gameplay systems including custom roles, abilities, events, moderation features, player utilities, permissions, and integrations designed for active communities.

‹ ›

Luaserver.lua×

— □ ×

1
2
3
4
5
6

local services = { "api", "panel" }

for _, service in ipairs(services) do
    print(service .. " online")
end
-- operational tooling

⌘ mainLn 3, Col 1Spaces: 4LuaUTF-8

Server control tooling

Purpose-built browser interfaces for configuration, player information, service management, and operational visibility.

‹ ›

Pysync.py×

— □ ×

1
2
3
4
5
6

async def sync_community():
    await roles.sync()
    await accounts.verify_links()
    return {
        "status": "complete"
    }

⌘ mainLn 2, Col 5Spaces: 4PythonUTF-8

Community automation

Discord tooling for role synchronization, account linking, staff workflows, moderation, announcements, permissions, and repetitive operational tasks.

‹ ›

{ }services.json×

— □ ×

1
2
3
4
5
6
7

{
  "proxy": "healthy",
  "tls": true,
  "services": [
    "web", "api", "panel"
  ]
}

⌘ mainLn 3, Col 10Spaces: 2JSONUTF-8

Infrastructure behind the interface

Deployment, reverse proxies, HTTPS, domains, service routing, application hosting, and the operational pieces that turn a project into something people can reliably use.

src/capabilities

From idea to operation.

I prefer projects where building is only part of the job. The interesting part is making the system understandable, maintainable, and useful once real users touch it.

Build

Turn rough ideas into working systems with practical architecture and a focus on the feature people actually need.

Integrate

Connect game servers, bots, APIs, web dashboards, roles, identities, and hosted services into one usable workflow.

Operate

Deploy, debug, monitor, maintain, and improve projects based on how they behave in a real environment.

config/tooling

A practical technical stack.

Tools change depending on the project. I use whatever keeps the system understandable and gets the job done without adding unnecessary complexity.

Core technologies

Common tools and environments used across current projects.

C# / .NETserver logic & tooling

JavaScript / TypeScriptweb interfaces

Reactcontrol panels & dashboards

REST APIsservice integration

Discord APIsbots & automation

Caddy / Cloudflarerouting & delivery

Working style

Simple principles I use when deciding what to build and how far to take it.

Useful

Solve the actual problem.

A smaller feature that works well is more valuable than a complicated system nobody wants to operate.

Clear

Keep the system understandable.

Configuration, deployment, and maintenance should make sense later — not only while the project is fresh.

Iterative

Test it where it will be used.

Build a working version, use it under real conditions, fix the weak points, and improve from evidence.

contact.md

Keep the identity public. Keep the personal details private.

This site is intentionally designed around a pseudonym. Add a public Discord, GitHub, community link, or other handle here only when you want it associated with the portfolio.

game-systems.cs server.lua sync.py services.json

portfolio›src›projects

Selected projects.

Dedicated project routes and sublinks so the portfolio can grow beyond one long scrolling page.

Game systems

C# server-side mechanics, custom roles, abilities, events, permissions, moderation features, and runtime tooling.

Server tooling

Operational interfaces and utilities for services, configuration, players, and live environments.

Automation

Python and bot workflows for synchronization, linking, permissions, staff tasks, and repetitive operations.

Infrastructure

Domains, HTTPS, reverse proxies, deployment, service routing, and systems behind the interface.

build()integrate()operate()

portfolio›src›about.ts

How I build.

I like projects that go from rough idea to something people can actually use and operate.

Build

Turn ideas into working systems with practical architecture and useful features.

Integrate

Connect servers, bots, APIs, dashboards, identities, roles, and hosted services.

Operate

Deploy, debug, maintain, monitor, and improve projects under real use.

languages web ops

portfolio›config›tooling.json

Technical stack.

A practical set of tools selected around the project.

Languages

C#, JavaScript / TypeScript, Python, Lua, JSON and configuration formats.

Web

React, REST APIs, dashboards, admin interfaces, and browser tooling.

Operations

Caddy, Cloudflare, Windows services, domains, routing, TLS, and deployment.

Integrations

Discord APIs, game-server APIs, identity linking, bots, and service automation.

contact.md

Public identity, private personal details.

Add only public handles and project links you want associated with Eclipted.