The short version

Takaro v0.5.0 adds three big things.

  • Shop Actions so a purchase can trigger logic, not just deliver items
  • Inventory change events so hooks can react when a player’s inventory actually changes
  • ClickHouse event storage so event-heavy setups have a stronger path for faster querying

We also shipped a batch of fixes that make the platform easier to run day to day.

Shop Actions turn the shop into an automation tool

Until now, a shop listing mostly meant one thing. Deliver an item.

With v0.5.0, a listing can do more. A purchase can now grant a role, send a message, execute a command, give an item, or run custom logic through the same module system that already powers hooks and cronjobs.

That matters if you use the shop for perks, donor rewards, access control, or one-off server actions.

Some examples:

  • sell a VIP perk that grants a Takaro role
  • trigger a command when someone buys a package
  • send a thank-you message after purchase
  • build your own custom shop action in a module

This release ships with four built-in Shop Actions:

  • grantRole
  • sendMessage
  • giveItem
  • executeCommand

If you need something more specific, you can create your own and expose it through a module version.

Inventory hooks can now react right away

We also added player-inventory-changed events.

Before this, inventory-driven automation often meant polling on a schedule and comparing state after the fact. That works, but it is noisy and slower than it needs to be.

Now Takaro emits an event when items are added, removed, or changed. That means you can write hooks that respond right away.

This is especially useful for:

  • quest or progression systems
  • anti-abuse checks
  • automation that reacts to item gain or loss
  • modules that used cronjobs only because there was no event to hook into

ClickHouse gives event-heavy setups a better base

Takaro now dual-writes events to ClickHouse alongside PostgreSQL.

For smaller communities, that mostly means the platform is getting a better foundation.

For larger setups, it is a practical step toward faster event queries and better scaling for event-heavy workflows.

If you rely on logs, automation history, or analytics across multiple servers, this work matters even if it stays behind the scenes.

Smaller changes that still matter

v0.5.0 also includes a few changes that make the product smoother to use:

  • view players and users assigned to a role directly in the UI
  • support CSMM shop import format
  • return clearer errors when shop listing imports are invalid
  • improve cronjob reliability under load
  • fix the midnight database connection pool issue
  • show the full version string in the frontend
  • restore the shop quantity tooltip on hover

None of those are flashy on their own. Together, they remove a lot of friction.

Why this release matters

This release pushes Takaro in a direction that feels right.

The shop becomes more useful. Hooks get more reactive. Event storage gets stronger. The platform gets more predictable under load.

That is the kind of progress we want. Less glue code. Less polling. More control.

Try it

If you are already using Takaro, update to v0.5.0 and try Shop Actions on a test server first.

If you are new here, start with the pricing page, then check the docs and changelog for the details.