Management tool for the community of a horse-breeding browser game

Origin story

The EquinePassion Manager grew out of the EquinePassion Calculator. More precisely, out of a need that only became clear through using the Calculator.

The Calculator itself was built for quick, individual decisions: evaluating single horses, comparing values, analyzing pairings. Over time, though, players built up larger and larger breeding herds and had to re-enter the same data every time they used it. That's exactly where a new need appeared: how do you organize a larger horse herd permanently instead of re-entering it every single time?

That's what I built the EquinePassion Manager for.

Features

Unlike the Calculator, the Manager had a database connection and user accounts. Users could permanently save and reuse their horses instead of starting from zero with every evaluation.

Technically, I built the Manager entirely in PHP and JavaScript without a framework, with its own database connection for user accounts and horse data. AI wasn't part of the picture yet at the time.

The Manager could:

• Manage user accounts and login
• Permanently save horses
• Organize larger horse herds
• Compare saved horses against each other
• Take interior and exterior values into account
• Factor in additional abilities
• Support long-term breeding planning

At its core, the Manager was therefore less an analysis tool like the Calculator, and more a management tool for larger amounts of data.

Current status

The EquinePassion Manager will be discontinued in the medium term. It was used fairly steadily, though not daily, since there was already a lighter, login-free alternative back then for a quick check: the EquinePassion Calculator. I've since renamed it and keep actively developing it, partly because it accounts for most of my website's visitors.

The Manager itself still runs on the PHP codebase from my student days and hasn't been updated since. From today's perspective, that makes it an insecure system, which is why I'm discontinuing it rather than leaving it running. I'm keeping it in my references regardless, since it shows what I've worked on over the years.