TaleSpire Dev Log 466

Heya folks,

It looks like I forgot to post my last dev log, so I’ve posted both today. Here is the previous one.

These last few days have been great. Lots going on.

We shipped the box ruler yesterday. That was a nice one to get out. The box ruler had been subject to “analysis paralysis” for a long time as there are many valid kinds of box rulers. Every time, we’d consider doing it as a quick project, but we’d run into cases we couldn’t solve with one tool and end up putting it back on the shelf. In the end, we just said, “screw it,” and implemented one of them. We wrote the bulk of it a while back, but sadly, I don’t have the shader skills to get it over the line. Ree stepped in to make it shippable.

Chairmander has been taking the lead for tagging, updating TaleWeaverLite to support direct upload to mod.io, and preparing that code for tags[0].

Also, regarding tagging, we’ve been in touch with Mod.IO for help with a few things we need to support tag search. They are super helpful, and we are currently working out the details.

Backend work is going well thanks to Borodust. Yesterday I joined him to debug some code related to 3rd party miniature providers. Gotta squash them bugs!

Ree and I also discussed UX design for the community mod browser. We decided that the language around subscriptions is misleading, especially as we introduce the option of subscribing to version changes. We also want to split some sections into a different in-game window/tool so we can make it a better experience. I mushed a bunch of concepts together down there and it’s not ideal.

I had done a bunch of work trying to unify the 3rd party provider UI with the community browser. I got something working, but with some play testing I had to accept that it wasn’t a step forward. That means scrapping a lot of that work. Painful, but it’s the correct decision. Holding on to mistakes just because they took time makes software crap, fast.

That’s all for me for now. Let’s see what today brings.

Disclaimer: This DevLog is from the perspective of one developer. It doesn’t reflect everything going on with the team

[0] There is more to the story, but he’s the best one to relay that in a future dev-log