From the Burrow
Heya folks!
In preparation for creature modding feature shipping, we are making the tool available so you can try it out, and we can fix any egregious bugs you find.
You can find a guide on how to get the tool and how to use it over here:
https://talespire.com/taleweaverlite-guide
NOTE: You cannot load the mods into TaleSpire today. This is simply a build of the tooling used to make the mods.
What is this (and what is it not)
TaleSpire is going to have a couple of ways for you to add new creatures to the game:
- In-game creature creator: A way of building creatures out of a palette of configurable parts
- Mods: mod-files are composed of pre-made assets outside of TaleSpire
TaleWeaverLite is for the second approach. It is a very minimal tool for composing pre-made assets into a creature mod that is ready to be used by TaleSpire.
It is not a modeling or posing tool. It expects content in specific formats and with specific layouts.
The expected usage is that the mesh and textures are prepared in other tools, such as Blender, and using TaleWeaverLite is the final step in making a mod.
The good
Once you are producing meshes and textures in the correct format, it’s trivial to turn them into a mod. Simply drag them into the Unity project, set the fields in the creature panel, and save.
The meh
We’ve been using Unity for our asset tools for a long time. It handled processing assets for us and gave us a UI we could use to make tools.
This means that to use TaleWeaverLite, you need to install the free version of Unity.
We have mixed feelings about this, as packaging this stuff for public use has not been as easy as we had hoped. Your feedback will help us decide whether to stick with this in the long term or to start moving to a more standalone tool.
The future
We are busy working on the backend changes needed to support the new creatures. Once we have that done, we’ll wrap up the needed changes in TaleSpire and get ready to ship. We are pushing hard for this and hope we can get this in your hands very soon.
By getting TaleWeaverLite out now, there might even be some new creature mods ready to ship the moment that TaleSpire gets the feature!
Until then, thanks for stopping by.
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 522
Hi folks,
Today we got group teleport, and this evening I did this:

So it’s getting close. I’ve still got a bug with prop-creatures, but not anything I’m worried about.
Hopefully I can finish a v1 of this tomorrow (as I promised on the banter it would be this week). Then I’ll be right back into other features.
The new font is being reviewed, and I’m looking forward to us getting that out to you all. Then I can finally resurrect all the internationalization work we did last year. Exciting stuff!
I didn’t get the symbiotes audio working right yet. I made some dumb mistake in the ring buffer. It’s ok though, I’ve made a functionally equivalent (but not performance equivalent) version using locks and that works, so I’ll be able to use that to help me work out the issue.
Have a good one folks, I hope you are enjoying the group teleport.
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 521
Heya.
The last few days have been dotted across various projects. Fonts, group-spawn, notes, and inventories.
Work on the inventory has centered on backend and (rough) UI design. We understand what we want for the frontend and have nailed down the backend api. So we’ll be moving ahead on that asap. I’ll share screenshots as that progresses.
For notes, I’ve done enough testing to show we can take markdown text and produce some UI to display it, along with embedded content like images and tokens. As I only needed to prove to myself that it was feasible, it currently looks like hot garbage and isn’t even part of the main TS codebase. I’m still stoked, however, as I’m not aware of anything that should slow me down when I get back to this feature.
Font work goes well. The current version needs final review, and then we should be able to merge it. It could be released fairly soon. Here’s hoping!
And lastly, we have group spawn.
At first, I quickly tried retrofitting the current creature spawning tool for groups. But I felt it wasn’t getting towards something good quickly enough. I had suspected this might happen, so switched to building the feature around the teleport tool instead.
The nice side effect of that is that we get group teleport.

I’ll now take the layout work I did in the first experiment, combine it with the above, and add some UI so we can spawn an entire folder of unqiue-creatures in two clicks.
See you in the release notes!
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 520 - Font'a'thon & Symbiotes
Hi again!
The hackathon to update the main font we use in TaleSpire is going great. We have made a full pass of everything, and so next up is testing out the font refactors and playing-test everything. Gotta find the things that need fine-tuning.
I’m really happy with how this week has gone so far, even with the Unity issues I mentioned in the last post.
We’ve currently got a build going through our server containing both creator-search and some fixes for Symbiotes.
The improvement I finished today is that the debug button now lives on the nav-bar and opens the dev-tools connected directly to that symbiote. This is a nice step up from before, where it opened a page with a list of all the symbiotes, and you had to click your one.
That looks like this:
Hah, I just spotted a typo in the notification. Ah well, on the todo list it goes :P
Gonna get this out asap.
Seeya in the next post.
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 519 - Font-a-thon
Over the last couple of days, we have been going through TaleSpire, replacing the old font with our new one, which supports many more languages and simply works better!
TaleSpire predates Unity’s nested-prefab feature, which means we have a lot of copies of similar UI elements that, if we were starting fresh, would definitely be made of reusable prefabs.
One big pain is that we are on an old version of Unity’s TextMeshPro library, and we can’t upgrade until we reach Unity 2023.x, and that version doesn’t support GPOS kerning tables in fonts. SO, we did a ton of work, and now we have to tweak the font to get proper kerning. GAH.
Luckily, our font guy is a star and is on it.
All our existing work should still be basically correct, so it’s not a disaster.
One big gotcha, though, is that swapping out the font file in the Unity project doesn’t actually update the TMP-font-asset, EVEN IF you right-click and “reimport” the font file and the TMP-font-asset.
Instead, I had to make a new TMP-font-asset from the font file. This’ll mean swapping out the asset on font files, but swapping out the guid in all files is trivial, so that’ll be fine.
On the symbiote side of things, I’ve started work on putting the audio from symbiotes through the Unity audio system. This will allow master volume to work across Symbiotes and also give opportunities for post-processing work to work consistently across all things in TaleSpire. Exciting! The plugin gives us most of what we need, but I want a more efficient version of the cross-thread communication[0], so I have a little work to do there (just a ring-buffer, nothing fancy).
I’m also doing some testing of markdown->tmp-text for the notes feature. Looking forward to getting those in the game.
Things are really on a tear right now. Chat with you all again soon!
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
[0] We force some specific details that the Vuplex plugin can’t assume, such as channel count and audio rate. So we get to make some simplifications. Also we can use Burst, which Vuplex currently doesn’t depend on, so we can do sample interleaving much faster they they could.
TaleSpire Dev Log 517
The last few days, I’ve been working on the connection issues we mentioned in recent posts.
After reaching out to various ISPs, we’ve managed to get most folks back playing. However, one of our players in Switzerland still had an issue because DNS requests for our subdomains were returning incorrect addresses.
It’s very odd, especially since it started so close to the other ISP issues. However, the folks at Sunrise GmbH claim they don’t have anything affecting DNS lookups, so I’ve taken another route to resolve the issue.
I’ve added a fallback to our DNS lookups that uses Cloudflare’s public DNS over HTTPS service if the default lookup fails. We could technically use it as the primary system, but we don’t want to risk affecting anything that already works, so this seems like the safest option.
I’ll be testing this tomorrow, and if all goes well, it should ship on Monday.
At that point, I’ll be getting back to work on shadows, where I’m currently reworking our frustum-culling compute-shaders as I prepare to move shadow culling to the GPU as well.
Ciao.
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 516
Heya folks,
We’re on a bit of bug-fix week over here in the Bouncyrock lair.
My original goal was quick fixes, but I was instead drawn into a chain of issues with the vision-limit tools.
In short, given certain chains of actions, TaleSpire gets into a tangle where it isn’t enabling or disabling the vision-limit views correctly.
I started with small patches to mitigate the problems, but they felt unsatisfying. So instead, this week became a proper cleanup of that code.
The code now achieves the same as before while being smaller, faster, and much more stable. It needs some playtesting, but I’m confident it will be shipping very soon.
Those fixes won’t be alone, of course. Ree has been working away on issues you folks found in the status effects, and Chairmander has some tag ui fixes (amongst other small internal improvements). Also, Borodust has been digging into some server-side issues that have been spoiling our fun recently.
Until next time, Ciao!
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 511
Hey folks,
For the last day or so, I’ve been working on a command-line tool for creating TaleSpire content-packs. This is a community-requested feature, but it has the additional benefit of helping folks like TitanCraft who want to export from their pipelines directly to TaleSpire packs. It’s basically a command-line complement to TaleWeaverLite.
It currently only supports creatures, but when we add support for community-made tiles and props, we’ll expand this tool to support those too.
The plan is to ship the tool in a subdirectory of TaleSpire, with versions built for Linux, Mac, and Windows from the get-go.
Other than that, my work on shadows is going ok so far. I’m hoping I don’t find any horrors as I get deeper into it.
Peace.
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 510
Heya folks!
We’ve found a bug with creature tags where they were only working in the community browser and not the library. That fix is in the works and will be shipped as soon as it passes the tests.
It also seems that mod.io has a bug (or has changed it’s api) so that tag searches now return results for things that match any of the tags, rather than all of them. This breaks the expected behavior in TaleSpire, as you can’t refine searches properly now. We’ve reported the issue and will keep you posted.
I’ve got a build of TaleSpire with the new physics and batching performance improvements. It needs final testing, but then it’ll be on its way to you. We’ll probably keep it in public Beta for one week, just in case anything else has slipped through the cracks.
The batching changes have finally put us in a good place to look at replacing the shadow implementation, which has been blocking us from upgrading Unity and getting some of the fixes and improvements we could really benefit from. I’m currently investigating how difficult it will be. Hopefully, it doesn’t put up too much of a fight.
Whatever happens there, my attention will return to the internal systems upgrade as soon as possible. That’s a very vague-sounding task, but it should make it much easier to fix a long-standing bug if I can get the code in the shape I want.
More news soon.
Peace.
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team
TaleSpire Dev Log 509
G’morning folks.
While I wait to see if there are bug reports from the hide-volume improvements Beta, my focus is back on Physics optimization.
It’s very important to us that TaleSpire runs well on lower-end machines. Not least because the cost of upgrading is, for now, so much higher than normal.
I’m currently working on the Physics front-end. The code that the game interacts with to use the physics engine. The changes allow more of the physics code to run concurrently with other tasks and to replace code compiled using Mono with code that can be Burst-compiled.
On a board with a lot of creatures, a significant amount of time was spent simply writing data into and out of the system because the GameObjects we were using stopped us from using the Burst compiler. I’ve rewritten all of that code, and I’m confident that those steps will not be an issue in future.
I’ll keep on plugging away at this. I’m not loving my old spider’y code, but untangling it is letting me find better ways to get performance out of it.
See ya in the next log!
Disclaimer: This DevLog is from the perspective of one developer. So it doesn’t reflect everything going on with the team