Config GUI Editor ↗
Validated settings forms instead of raw configuration editing.
Client work / Addonate
I developed every addon for Addonate, implementing the product interfaces and the backend behaviour behind them.

Server operators need controls that fit inside the panel they already use. Billing, configuration, permissions, and player management each need their own interface and backend integration.
My work for Addonate covers every addon. The examples below link directly to the published products so you can inspect their functionality and documentation.
Validated settings forms instead of raw configuration editing.
An AI assistant integrated into the Pterodactyl panel.
Coin-based billing and server deployment inside the panel.
Reusable roles for managing panel access.
Player management without sharing full console access.
Embeddable server status, player counts, and activity.

I developed a configuration interface that turns server files into validated controls. It includes a change preview, revision history, and a raw-text fallback for cases outside the form interface.
Field validation and a diff make proposed changes inspectable before saving.
Structure-preserving writes retain comments, ordering, and formatting.
Revision history provides a path back to an earlier configuration.
Client and Application APIs use the panel’s permission system. This product installs standalone.
The key tradeoff is coverage: structured forms make common edits easier, while the raw-text fallback keeps less familiar files usable.
Inspect the feature list and screenshots ↗Public releases provide a dated record of the work. These are publication dates, not the start dates of my engagement.
The public listings include product documentation, screenshots, compatibility details, and release history.
Available for freelance work
Tell me what it needs to do, what exists already, and where you need help.