We’re back with our first update of 2024. We’ve set ourselves some big goals for the year, and are introducing some of those with this update.

Public roadmap

Our first big goal for 2024 is to better listen to our community when it comes to what they want to see added in Kanka. Our yearly survey gives us a big picture idea, but doesn’t give us a consensus of what to work on. As Kanka matures and becomes more complicated, it is important that we focus on features that add value to a large number of users.

For this, we’re introducing our public roadmap, where all users can submit ideas on how to improve Kanka. Ideas that add value to Kanka and fit in the product’s vision will then be visible to all to see. Our amazing subscribers can then vote on any number of ideas from the roadmap.

Ideas with lots of upvotes will then eventually get worked on, with their status also visible on this new page.

This will completely replace the Discord’s #feature-request channel, as well as the subscriber community votes. We believe that with this change, we can work on high impact features and ship them faster, rather than have great ideas sleep dormant in the backlog for years.

Lightning fast v2

We made Kanka faster with the last update, and found even more ways to make it faster! Some users were already secretly using these new speed improvements since the beginning of the year, and with 2.2 we’re enabling them for everyone. We have a few more tricks up our sleeves to increase Kanka’s speed again over the next few months.

Family trees for boosted campaigns

For our subscribers still on the legacy boosted campaign system, family trees are now also available for you. We’ve also fixed a few bugs that resulted in the tree saving but not rendering.

General improvements

Creatures get a new “extinct” flag, the same way organisations have a “defunct” and characters a “dead” flag.

The campaign “system” field has been replaced from a free-text to a list of multiple values. This means that it is now possible to properly filter on public campaigns, but requires campaigns to reset their systems. This list is now hardcoded and includes systems that were popular in the old system.

Dashboard widgets set to recent entities of a specific type now have their widget title link to the entities. This link also includes any filters set up. Behind the scenes, we’ve also replaced the code that renders these lists to use a neat little framework called livewire.

Entity assets now accept .csv files.

The rowspan property of tables is now whitelisted.

When transforming an entity from one type to another, the entity log will keep track of that change.

Premium campaigns can now set their public campaigns as being “discreet”, which prevents them from showing up in the public campaigns.

Bug changes

The replace attribute mentions option when copying an entity works again.

It is no longer possible to bulk-edit entities and set an entity as it’s own parent.

A character with a pinned birth that was in the past no longer crashes the page.

When an element is set to “Self + Admins” visibility and edited by another admin, the visibility no longer changes to All. Instead, the visibility is locked and not editable.

Fixed an issue with family trees showing the death year before the birth. The edit permission on the family is now required to edit the family tree too.

---

That’s it for the overview of this 2.2 release. We’re still hard at work on the new campaign import feature teased in our last update, which we hope to release to our Wyverns and Elementals before the end of the quarter.

As always, thanks to our amazing subscribers for making this huge updates possible! Come join us on our Discord to get early sneak peaks of future updates.