Minecraft Plugins
- 3 plugins: JartonAunctionsDiscord, JartonLink, and JartonChat.
- Paper/Spigot systems built around modular architecture.
- Performance-aware event handling and data access patterns.
Specialties
Builds Across Three Pillars
Each pillar is designed around long-term operation, not short-term hacks.
Discord Bots
- 2 bots: Swifty and JartonBot.
- Automation pipelines with auditable actions and clear ownership.
- Integration to and from Minecraft.
Websites
- 2 websites: Swifty and JartonMC Website.
- Fast, accessible interfaces with maintainable component systems.
- Production-minded architecture and deployment-ready structure.
Featured
Selected Work
Examples of production-minded systems built for communities and operators.
MinecraftFeatured
JartonChat
A modular chat control plugin with formatting, filtering, channels, and Discord relay support.
- Supports staff/admin/public channels with permission-aware routing.
- Includes anti-spam, mute handling, and rule-based content filtering.
- Relays announcements and selected chat streams to Discord.
JavaPaper APIAdventureRedis
Discord BotsFeatured
JartonBot
A Discord bot built for server management with tickets, utilities, and moderation controls.
- Handles support workflows with structured ticket channels.
- Includes moderation command sets with safety checks and logging.
- Automates repetitive server tasks through configurable actions.
Node.jsTypeScriptDiscord APISQLite
WebFeatured
Swifty (Website)
The web presence for Swifty, designed for product clarity, trust, and conversion.
- Presents features, documentation entry points, and contact workflows.
- Uses responsive layouts for mobile and desktop viewing.
- Maintains clean visual hierarchy for faster visitor comprehension.
Next.jsTypeScriptTailwind CSS
How I Build
Principles Behind Every Build
Predictable architecture and practical execution for long-term reliability.
Integration-first
I design around real ecosystems, not isolated demos. Every system is planned to connect cleanly with what you already run.
Maintainability
Modules, naming, and docs are structured so future changes are predictable and low-risk instead of patchwork.
Production mindset
I optimize for reliability in live environments: observability, sane defaults, and behavior that holds up under load.
Have something in mind?
Share your scope and I'll map a build path that holds up in production.