I make RuneLite plugins, browser games, public player profiles, and live dashboards for OSRS communities. The bar is simple: software players actually adopt, defend, and keep using after week one. Trust, identity, and adoption are the product.
I do the whole loop solo: idea, design, build, launch, community response, live ops, iteration. No handoffs, no waiting on another team.
Right now that looks like Kill Clog (6,500+ installs in its first week on the RuneLite Plugin Hub) feeding public player and clan pages at killclog.com, Clan Clog bringing collection logs to whole clans, Rigour Hero (a browser arcade with 7,400+ plays and an original soundtrack), and a live dashboard tracking adoption across all of it.
Available for remote contract work, short-term builds, and small-team engineering or product roles.
A RuneLite HiScores overhaul that grew into the foundation of a public PvM identity layer. Trust-sensitive community software with live adoption and product ops attached.
Kill Clog brings boss kill counts, Collection Log progress, player lookup context, account-type rendering, and PvM flex data into a cleaner, more useful HiScores experience. It was designed around a simple product insight: OSRS players do not just want stats. They want context, progression, identity, and proof of the grind. The public killclog.com profile surface turns those captures into shareable player and clan pages.
Mine end to end: concept, UX, RuneLite implementation, public launch, community response, and every release since.
product work: player research · feature prioritization · UX writing · launch · community feedback · release management
technical work: Java · RuneLite SDK · TempleOSRS API · OSRS cache · async Collection Log capture · ironman badge rendering · custom RuneLite UI · local caching · account-type detection · tooltip systems · Plugin Hub release flow
Collection logs for whole clans. A RuneLite plugin and public web surface that turn a clan roster into aggregate boss, clue, and rare-drop proof, with pages any member can share.
Runs on the same identity rails as Kill Clog: a Node aggregate-profile API merges provider data behind the public pages, and the plugin stays the source of truth for what renders.
technical work: Java · RuneLite SDK · Node.js aggregate API · provider adapters (TempleOSRS, Wise Old Man) · roster sync · public profile rendering
A real-time OSRS-inspired prayer flicking arcade with raids, collectible pets, original music, public leaderboards, and server-validated scoring.
Rigour Hero was built as a complete browser game and live-service web product: deterministic combat, seeded RNG, replay validation, anti-cheat checks, account profiles, public scores, WebSocket presence, channel chat, and a security page written for skeptical OSRS players.
The project required more than game logic. It required product design, trust-building, player onboarding, community expectations, abuse prevention, progression tuning, and enough polish for players to understand it immediately without a manual.
product work: game loop design · onboarding · difficulty tuning · leaderboard integrity · security communication
technical work: JavaScript · HTML5 Canvas · Node.js · WebSocket · seeded RNG · deterministic replay · server-authoritative combat · anti-cheat validation · scrypt auth · pm2 · nginx
A live analytics dashboard for tracking Kill Clog adoption across the RuneLite Plugin Hub ecosystem.
Built to turn a plugin launch into a readable public growth story: install counts, adoption trends, milestone markers, rank comparisons, UTC roll-off explanations, creator-coverage markers, and a daily refreshed Gravity Index comparing plugin momentum across the RuneLite ecosystem.
It exists to answer the questions a launch actually raises: what happened, why, whether retention is holding, and where the next wave might come from.
product work: growth analytics · launch reporting · data storytelling · adoption analysis · dashboard UX
technical work: Vanilla JS · Chart.js · Node.js cron · static JSON pipelines · auto-regenerated summaries · GitHub Actions deploy · Cloudflare DNS · localStorage
Currently open to remote contract work, short-term builds, and small-team engineering or product roles.
Best fit:
builds where the community is the product. Public surfaces players will defend. Identity and profile layers, gaming tools, live dashboards, real-time web, and the integration work that ties a community to its tools.