I did some checking on reported issues with SkyTemple sent via the built-in error reporting (thanks to everyone that opted-in to that!).

I need some help reproducing some of these issues. If you have a hint, let me know by mentioning @skytemple@blog.skytemple.org, @capypara@guild.pmdcollab.org or replying to the GitHub issues:

• https://github.com/SkyTemple/skytemple/issues/579
• https://github.com/SkyTemple/skytemple/issues/580
• https://github.com/SkyTemple/skytemple/issues/581
• https://github.com/SkyTemple/skytemple/issues/582
• https://github.com/SkyTemple/skytemple/issues/583
• https://github.com/SkyTemple/skytemple/issues/584
• https://github.com/SkyTemple/skytemple/issues/585

The SkyTemple Podcast is back! This time it's hosted by TheSmingle and is all about the hacks submitted to the recent Hack Jam. You can find the first episode here: https://www.youtube.com/watch?v=lqIofwJOoGA - Three episodes are already up.

Hey!

Here's another hotfix release:

• SkyTemple 1.5.4

• SkyTemple Randomizer 1.5.4

This release fixes an error when SkyTemple was trying to decompile scripts.

The reason for this error is that something in the dependency igraph changed. At the moment SkyTemple is configured to optimistaically pull in new versions of its dependencies. This has the disadvantage of breaking unrelated things even in minor bugfix releases like the last one, but has the advantage that SkyTemple doesn't stick around using ancient versions of it's dependencies for years.

In the next version I still want to define what new versions SkyTemple can pull it's dependencies from though. Sadly in this case it would not have helped, since the version jump in igraph was from version 0.10.4 to 0.10.5, so on "patch" level. I would have configured SkyTemple to pull in patches like this anyway.

For more information, see the issue about this on skytemple-files.

We are aware of a regression in SkyTemple 1.5.3 that prevents users from decompiling scripts (https://github.com/SkyTemple/skytemple-files/issues/378) - we are working on fixing this and will release an update soon!

Hey!

New releases of SkyTemple and the Randomizer have been published.

The release fixes an issue with the "UnusedDungeonChance" patch. Previously it was possible for the game to crash while attempting to generate a room with mazes in it.

To update and for changelogs, see the download pages:

• SkyTemple 1.5.3

• SkyTemple Randomizer 1.5.3

For more information:

• You can find the Pull Request by End here: skytemple-files#34

• You can find the commit in End's patch repository here: EoS-asm-hacks

There's going to be a new bugfix release for SkyTemple and the Randomizer soon, however at the moment the Windows build pipeline is not working, due to issues outside of our control. As soon as it's available again, we'll try to get that update out. It'll fix issues related to crashes when applying the "UnusedDungeonChance" patch.

Hi! For updates, see the "Articles" tab above. I'll post smaller updates as notes, but in general, the "Articles" section will contain important information, such as new release announcement, etc.

Hey readers!

You are reading the first post on https://blog.skytemple.org - this is now the new place for new announcements for the SkyTemple project, most notably the app itself and the Randomizer.

I will announce new versions here, including pre-releases and some general updates I and other contributors are working on. And I'm always happy to hear your general feedback.

You can subscribe to this microblog via RSS or any Fediverse (eg. Mastodon account). You can also react and reply using any Fediverse account.

Thanks everyone for using SkyTemple!

Current versions

The current versions as of posting this are:

• SkyTemple 1.5.2
• SkyTemple Randomizer 1.5.2

You can see the current changelogs and downloads by clicking the links.

Current beta

There's currently a beta for a new and improved emulator integeration for the debugger. If you want to help test this one out, you can find that one here. You can let me know of feedback you have by using the comments of this post, or by joining our community Discord server.