​

Hello! This time, we'll be announcing Wave 4 launch date and changes that will be happening after Wave 4 in regards to gaining Closed Beta access. Let's get started!

Wave 4 is starting on 15th of May 12:00 UTC+0

With the smart watch testing now underway, we found some critical issues & crashes, but for the most part it's been smoother than we expected. The only thing now remaining is fixing these issues, some polishing touches and fixing the inaccuracies in steps graphs.

We expect that we can have all of this done before 15th of May, so that's when we'll open the Wave 4 at 12:00 UTC+0.

The wave will close on 8th of June at 23:59 UTC+0.

Getting guaranteed access to Wave 4

If you want to gain guaranteed access to Wave 4 and start playing immediately when it has opened, you can support us which gives you immediate access. Any new supporters during the Wave 4 will also gain access immediately. We will be accepting people who have applied to the Closed Beta from WalkScape Portal throughout the wave as well.

Changes for new supporters after Wave 4

​​

There will be changes to the benefits and pricing for supporting WalkScape that will come into effect for new supporters after Wave 4. Existing supporters will not be affected by any of these changes.

Changes to new supporters after Wave 4

• All supporters, at any tier, will always be granted immediate access to the Closed Beta without needing to wait until we accept more players.
• Walker price is increased from $3 a month to $4.50 a month.
• Serious Walker price is increased from $6 a month to $7.50 a month.
• One time purchase on Buy Me a Coffee will be increased from $3 to $4.50. One time Beer option will be removed.

Pricing and benefits will stay the same for all current supporters and for any supporter who starts supporting before the end of Wave 4.

Why these changes?

Let's start off by saying that the prices for the Patreon and Buy Me a Coffee have stayed the same since I was still developing this game just on my own all the way from early 2023. At that time, I wasn't thinking that these prices would eventually be something we would run a business with and pay wages to multiple people.

These changes don't come lightly or out of greed, and I want to make it clear. I've tried to apply for government grants (Business Finland) now for four times, because if we would've gotten a grant we wouldn't have needed to touch the pricing. Sadly, my applications for getting a grant for the company have been denied each time, main reason being that we don't have any investors backing the project. And we don't want investors, because that could risk the integrity of the game - investors could start seeking for quick returns, and pressure us to make changes that could ruin the game. We've been offered investments multiple times, but I've turned them down each time because I know that as long as I stay as the sole stakeholder, there will be no risk of enshittification.

With the money that we currently get from Patreon & Buy Me a Coffee, we've been able to pay the wages and all of the other expenses, but we are breaking even. In addition between waves, there are often cancelled or charged back subscriptions, which means our income decreases. Due to this, I often have to cut my own compensation between the Waves.

This has been all good so far, but as everyone has probably noticed, things have gotten increasingly expensive in the last couple years. That hasn't just made it sometimes a struggle to have enough money in personal life to get by, but all of the bills our company pays have also increased.

Our goals with the changes

The goals we aim to achieve with these changes are:

• Gaining immediate access by supporting outside of a wave could stabilize our finances when there is no on-going wave.
• If we could turn a profit each month, we can start saving this money for Open Beta release. We expect that Open Beta launch will burn a lot of money (server scaling, transitioning from Patreon/BMAC to subscription model, marketing, etc.).
• If we could increase revenue significantly (from current $12k-ish per month to around $17k a month, after taxes, currency exchanges & platform fees) we could hire one more developer.

I want to stay fully transparent about anything related to these changes, and any future changes as well if there will be some. I will answer any comments, questions, suggestions or feedback you might have on this in the comments!

Until next time

That's all for today! I will answer any questions, feedback and suggestions in the comments and on our Discord server.

I want to also thank all of our current supporters, beta testers and members in the community for being patient with us. It's been a long road to Wave 4, and finally we're so close to it! I hope everyone new will enjoy the game.

Keep walking, and stay hydrated everyone!

Hello!

Let's begin by saying that this feature has been quite a lot of work to make due to all of the uncertainities and how difficult it has been for us to test. Now we're finally releasing this, and we expect there to be issues. We need your help to properly test out this feature properly, by gathering as many bugs and feedback as possible before we can open Wave 4.

Testing details

• If you find any exploits report them to the development team. Report these bugs either via Discord by direct messaging developers there, or via our contact email address: [email protected]. Players who find exploits and abuse those will be banned, but if you report your findings you'll be fine, as long as you don't try to intentionally abuse the exploits. In extreme cases, we might rollback your character to a previous backup.
• When reporting issues to us, please tell us as many details as possible. What wearable are you using, what applications are you using to sync your steps to Apple Health (in cases when you're using something else than Apple Watch), what steps did you take to encounter the issue. The more in-depth you're with the details, the easier it will be for us to replicate your issue and fix it.
• Feedback is also much appreciated. If you feel something could be better, be it UI, texts or whatever, please give us feedback. Best place to file in feedback is on our Discord server's #wearables forum channel, as then other people can also easily chime in to discuss the feedback. If you don't see the channel, you probably haven't picked up the beta role. You can do that from #roles channel.
• If you're reporting bugs or other issues regarding the steps, please include screenshots of your Apple Health step data entries. This can be found from Apple Health > Steps > Data Sources and Access > (choose your device) > (choose date) > Screenshot of the entries, or of a single sample that might've had an issue.

What we are looking for

• We're also looking for as much information as possible on how the wearable support works on different devices and wearables. Initially, all wearables and health sync apps are allowed. Based on the information we get, we will later on transition to a whitelist system, as we've already found that some wearables and apps report their data in a format that isn't specific enough for having robust anti-cheat.
• If you find that your wearable or apps you're using are having issues working with WalkScape properly, please report this to us as well. Also, if something works really well, we would love to hear that too. This will help us to have a good understanding about what works and what doesn't, and will help us in the future to provide good customer support for users that use wearables.
• For reporting these, we have opened a new forum channel on Discord called #wearables. Please report your findings there.#

When are we releasing this

• The game will go maintenance as soon as the reviews on Apple TestFlight and Google Play are done. We can't know exactly when they'll finish the reviews, but it can be anything from 1 hour to 24 hours. On average, it's lately been around 2 hours.
• Maintenance is expected to take 1-2 hours.

Changelogs for #457

Added

• New achievements
• New PFP option
• New recipe
• New keyword
• New items
• Wearable support on iOS
• New, improved language selection UI
• New translations from Weblate
• Languages with grammatical gender can now choose their preferred grammatical gender. This affects languages such as French, Spanish, Portuguese and Italian.
• Reworked the in-game settings. In-game settings have been reset to default values due to these changes.

Changed

• Adjusted cut opal value
• Adjusted a chest loot table

Fixed

• Fixed some background errors that were happening when changing PFP color options
• Fixed some background errors that happened when starting crafting actions
• Fixed some background errors on iOS when launching the game
• Fixed a bunch of small issues that happened in the background while using a fresh account & install

Thank you

Thank you, and thanks for the patience! I'm hoping this testing goes well, and we can get as much feedback and bugs reported as possible, so starting next week we can fix as many of them as possible.

As long as all critical issues are fixed, the only thing at this point that is missing before launching Wave 4 is fixing the inconsistencies in steps graph. We're hoping to fix after smart watch support related issues are resolved.

Happy walking everyone!

Welcome to another WalkScape devblog! This time, we'll dive into our current progress towards Wave 4 and changes to character customization. Myzozoz has also now worked one full year at Not a Cult, so we also hear from him!

Let's get started!

Wave 4 update

Our initial goal was to have everything needed for Wave 4 update ready around end of the month. While it still seems like we might be able to hit this deadline that we had, we've realized that we want to have the iOS smartwatch support tested not just internally, but in the Closed Beta before starting the wave.

Now that the feature itself is completed, we struggle to properly test it and have feedback on it through internal testing (our internal testers mostly have Android phones, and those on iOS don't all have smart watches). At the office, we only have an Apple Watch and a Garmin. Due to this limitation, our current expectation is that the feature is not stable and will have issues when initially released, which is why we want to release and fix any issues it might have in Closed Beta with our current testers before opening the new wave.

We're aiming to ship the iOS smart watch feature to Closed Beta next week, and we would appreciate any of our current Closed Beta players with iPhones and watches to give it a try and provide us feedback and bug reports. The more detailed feedback and bug reports we can get, the quicker we can work to fix anything weird there might be with this feature, and then begin Wave 4 once it's stable.

The reason why this is important is that a lot of people joining the upcoming wave are specifically interested in iOS smart watch support, and I feel that it would be a really bad experience for new players if this feature wasn't working like it should. This is why I think it's necessary that we ship it, have a round of feedback from our current Closed Beta players, fix & improve it, and then open the wave. If we shipped this at the same time as we opened the new wave, we could easily get overwhelmed as we're often very busy during waves with customer support, marketing, and fixing other issues & scaling our server infrastructure.

New timeline for Wave 4

It's still a bit difficult to lock in a specific date for Wave 4, but this should become much easier once we have iOS smart watch support released and get feedback. Two things are certain however:

• Wave 4 will begin in May
• We will have the release date announcement in the next devblog on May 1st.

I know a lot of people were anticipating for the date announcement here, but with the iOS smart watch feature's stability being uncertain until we test it with current Closed Beta players, we'll need some additional time to make sure it works.

One year of myzozoz

Hey everybody! It has now been a full year since I joined the team at Not a Cult and many many things have happened in that time. We went to a bunch of conventions, won some prizes, spent a lot of late evenings working on the game or just sharing ideas and of course released a bunch of updates for you to play. I just wanted to say a quick hi to everybody and thank you for this past year, hopefully the first of many to come. I typically don't maintain a large online presence (just more of an IRL type of guy), but don't worry, I'm having loads of fun working on the game and reading your comments on Discord, Reddit and the forums. Just keep playing the game and we'll keep on working on it. -myzozoz

Two upcoming art changes

Hello everyone, Maxchill here today with an update about two upcoming changes in our game's art. Both of these changes involve moving away from the use of AI-generated art. Currently, you encounter such art in two places: location views and character profile backgrounds.

The current location art will be replaced with isometric pixel art scenes. These will no longer be static images but will become interactive. For example, if a player wants to perform a mining or foraging activity at a location, they will be able to interact with it directly on the isometric scene. I believe this will add another layer of immersion and depth to the game world.

This change will make the overall look of WalkScape more cohesive and thoughtfully designed. We also plan to utilize the isometric location views for more features in the future, such as combat, farming, quests, and so on. The second change is a direct consequence of the first. Without the AI-generated location screens, we can no longer have the dynamic profile backgrounds that changed based on the character's current location. While I know this was a liked feature by many (myself included), we have tried to replace it with something equally cool. Two new profile character image layers will become available to players: background and ornament. First, players will be able to choose from various backgrounds, both basic and unlockable. These will range from simple color gradients to unlockable faction banners and even country flags. In the future, we may even include custom made guild banners.

The ornament layer will be optional, allowing players to display more of their unlocked rewards if they wish to. These will primarily come from activities and crafting, essentially providing another way to showcase your character's progress and achievements to others when they inspect your profile or view leaderboards. These changes will not be included in the next immediate update, but they will be released as soon as they are ready. We anticipate that the background/ornament profile picture feature will likely be released first, followed by the location view overhaul sometime later.

Until next time

That's all for today! I hope you enjoyed this devblog, and we're certainly getting a lot closer to the start of Wave 4. Let's hope that things will go smoothly with testing & fixing the iOS smart watch feature so we can start the next wave as soon as possible.

Stay hydrated and keep walking!

Hello! This time the devblog is posted a bit later than usual - I just got the first draft of smart watch related UI finished, which I wanted to showcase on this devblog! We would really appreciate any feedback on the UI.

First look into smart watches

Okay, so let's start with an overview of smart watch support!

We've now built the necessary functionality to support smart watches on iOS, and during this past week we've also done a lot more testing to see if there are ways to make it better on iOS. Sadly, it does come with some hard limitations that we can't change - but these shouldn't have too big of an impact in WalkScape.

Now we're in the process of making the UI for selecting your step source device as clear as possible. Each option comes with its own caveats, so we're trying to let the user know what to expect while choosing the step source device.

Above you can see how choosing Phone looks like. For all of our existing players, nothing new here - but for a lot of people starting out the game, it they expect that practically what Apple Health, Google Fit, Garmin or whatever other app they use should correlate directly with what they would see in WalkScape. I'm hoping that this UI, as it will be shown to everyone first time opening WalkScape, clarifies that there is just one source for your steps at a time. Apple Health, Google Fit and other fitness applications all use different methods for calculating step totals for each day - some even use GPS to approximate steps.

Apple Watch

Apple Watch comes with some functionality that other watch manufacturers might not have access to, like updating Apple Health step data in the background. I want to make it clear that we are not advocating for Apple Watches or any other products, but I felt like it's best from user experience stand point that this is listed as its own option. It's the most common watch people use on iOS and the way it functions is same for everyone.

Just to make this a bit more complicated from development standpoint, a recent European Commission ruling might change this. TLDR is that EU is forcing Apple to open their APIs so third party manufacturers can make their watches work as smoothly as Apple Watches on their platform. Apparently Apple might refuse to make this change for US customers, so we might need to have two implementations on how watch support works on iOS... what I've learned is that smart watch support itself isn't complicated at all, but the platforms like to make this really crappy for developers by having all kinds of arbitrary limitations.

One of these limitations that we couldn't find our way around is that there is not way to get live steps data from Apple Watch to WalkScape, as it's reliant on when the watch syncs the steps Apple Health. We didn't find any conclusive answer to when that is. There are several triggers that usually make it happen though:

• When you unlock your phone, Apple Watch often syncs the steps.
• If you open Apple Health, Apple Watch often syncs the steps.
• If you background WalkScape and reopen it, Apple Watch might sync the steps. This didn't feel that reliable.
• If you've been away from your phone for a while and come back to it's bluetooth range, Apple Watch often syncs the steps.

For majority of our players, this isn't really a problem - the way Apple Watch syncs the steps works really nicely as WalkScape doesn't need to be opened often, and when it's opened these triggers should mean that the step count is updated. What I am a little bit afraid of is that when new players come in Wave 4 who choose to use smart watch for input, their expectation is that when they start walking stuff in the game would update. With Apple Watch, this sadly isn't possible and that's why I've tried to make it as clear as possible in device selection UI that this is the case.

Other watches

Using other watches is a bit more complicated. We don't have access to more than a couple of watches, and for instance Garmin (very popular within WalkScape community) will not automatically sync its steps to Apple Health. You will need to install their software (Garmin Connect), and when you have some steps on your watch, you need to open their application and sync your steps to Apple Health manually, and then those will count in WalkScape. I assume this applies to other 3rd party watch manufacturers on iOS as well.

Not really optimal from user experience standpoint, but there's no way around this limitation either.

Permission management & Android support

I've also applied a fresh coat of paint on the permission prompts after you've chosen your step source device. We're still in process for making the listing and connection to your watch as smooth as possible after you press on the "Connect to Apple Health" button. I'm hoping this is a bit more clear for new players than the old one. If you choose Phone as your input device, you don't need to connect to Apple Health.

When it comes to supporting Android devices, we have both good news and bad news. Let's start with the good ones:

• Health Connect seems to be finally fixed. Previous issues we encountered seem all been fixed, so now supporting smart watches on Android should be possible.

And then, the bad news:

• Even though it's now possible based on our testing, building it would take time, and we really want to launch Wave 4 as soon as possible. So likely not going to make it in time for Wave 4.
• Android 16 will include an update to Health Connect, and is releasing around May/June. On surface, it seems like there shouldn't be anything that would affect the way we would use it, but with Google you never know - it might complicate our efforts, or might not affect us at all. More info on that is available here.

Until next time

I hope that this devblog didn't sound too much like a rant. I might be a bit annoyed with how silly some of these limitations are when it comes to simply reading step data from smart watches.

But the great news are that the support for smart watches on iOS has taken some big leaps in its development, and we're hoping to have it ready very soon and then fix the inconsistencies with steps graph. After these two things, we should be mostly ready to begin Wave 4.

Stay hydrated and keep walking everyone!

PS. as an extra, here are the results from our poll we did previously on smart watches:

Hello and welcome to a big new update! We would like some early feedback as we've now started redesigning the UI how people would like this change. I think it's very intuitive.

As you can see here, there's only one menu in the game. If you haven't logged into the game before, you first login through the terminal as well. Character creation and customization options are visualized in ASCII art if you make a new character.

spoiler

happy april fools everyone

Hello and welcome to Devblog #56! We have some great and exciting announcements to make this time.

Just in the last devblog two weeks ago, we announced my development focus shifting towards Devtools 2.0 in order to start shipping new content more rapidly. Now we have the first content update completed and in internal testing - so let's dive in!

10th skill to WalkScape: Trinketry

With the help of the new Devtools 2.0, we've managed to add a 10th skill to WalkScape and a bunch of other new content. So without further ado, let's introduce Trinketry!

In the picture above, Trinketry is shown as the process of making rings and amulets. In the game, players can find both trinkets and rough gems that can be crafted into rings and amulets using the Trinketry skill. Along with these materials, players will also need gold and silver bars to create many of the rings and amulets. We had a lot of fun (= trouble) trying to come up with a name for the skill. The description actually includes three of our other candidates: gemology, gemistry and jewelcrafting. We chose Trinketry as that name was both unique and flexible, as the skill isn't always just about gems and jewellery. You can craft flower necklaces for instance!

The rings and amulets crafted in WalkScape come in the well known system of different qualities, ranging all the way to Eternal. Some of these items are very powerful and can be especially useful in the game, especially at higher qualities. I personally expect that when trading is added, high quality trinkets would be very high in value, as crafting some of them is rather difficult.

Trinketry also introduces a new service known as Trinketry Benches. These benches are found mostly in GDTE and mark the beginning of our content development for this region. From the beginning, there will be four unique Trinketry Benches available, some of which come with their own unique quirks.

In GDTE, players will also come across a new faction called Erdwise, which brings new jobs and rewards to the game. Furthermore, new activities have been included to give players more opportunities for exciting gameplay.

Floursifter's designer notes

Trinketry was one of the three skills I designed post-Syrenthia, and I'm so excited that it is in the game! It was the best candidate to develop as we built and tested the new Devtools environment, which has progressed very rapidly in the last two weeks. Devtools 2.0 has truly revolutionized my relationship with content development. In the past weeks, we’ve gone from sending files back and forth to each other on discord for version control and no operational devtools, to having full version control and many devtools in a workable state! It was particularly useful to spend a lot of time rapidly prototyping and deploying the new devtools live with schamppu over the last two weeks, as he was able to watch me develop content and see where the pain points were in real time.

In terms of Trinketry, although this was the easiest skill for me to implement, it is quite difficult to level up. There were many considerations in the design process:

• The existing landscape of looted rings and necklaces
• How to effectively integrate other pre-existing content and the other skills
• Clear themes on what materials are useful in different parts of the skill

Players should have some decent ideas of the final design from the spoiler. It’ll be really fun to see WalkScapers rush to level up, compete on the leaderboard, and discover new content. And, if you enjoyed crafting one perfect tool before, I know you will really enjoy crafting two perfect rings!

We’re trying some new technology out, and would appreciate special attention and any bug reports on the following:

• Several items in WalkScape were transformed into different items. I tried to preserve your progress where possible, so if you have gems, gold ore, or certain rings and necklaces, please don’t panic if these are now new items. Any items that were changed away from being gear (like some existing jewelry) should delete themselves from your gear sets when you login.
• There are some new attributes in the game, and I’m hoping these provide some nice competition with current attributes for chasing certain content in the game.

Release schedule and details

While the content update is now ready, it will spend at least another week in testing while we make sure all of the features work (the new leaderboard for the skill still has a few issues, for instance, that we need to iron out). We'll be pushing it out when we're confident that it's ready for public release. So, while we will not be setting a release date, I can say that it will be released in the next two weeks - before the next devblog!

We will post a development update a day before its release, so people can fully prepare for when it goes live. It'll be rather interesting to see how a new skill being added works in the game - I'm especially interested to see how people will be competing in the brand new leaderboard.

My secondary goal while is to add a few small quality of life tweaks into the game while the internal testing is going on, so that's another thing to look forward to in this update! We've already fixed some bugs and made a few improvements, and I'm hoping to have a some time to add a couple more things that have been asked for.

Devtools 2.0 progress

It's clear that we've been working hard on getting everything up and running again for content delivery, and I'm pleased to say that we've not only made progress on developing content, but we've also successfully got Devtools 2.0 into a state where they're now functional. While there are still some features that need to be added to fully maximize the potential of the new devtools, I believe that we have made an good start in a short amount of time. Considering that the devtools were not working at all two weeks ago and now we have both the tools ready and a new update, it's been really smooth and fast development so far!

Moving forward, we are excited about the prospect of being able to release new content more quickly. This milestone has given us momentum and drive to continue improving and expanding our content delivery. Thank you for your patience and support!

Here are things that are still missing from our Devtools 2.0 until we consider them to be completed:

• Cloud sync, so when multiple people work on content at the same time, the changes are reflected to everyone simultaneously. We're currently using Git to synchronise changes which works okay, but isn't a tool that is familiar for floursifter and maxchill.
• Content branching, so we can create branches of content updates internally to test out things without changing the "main content".
• Over the air updates. We had this before the engine update, but as it changed so many things it isn't in the game anymore. This is most significant to players, especially as we plan it to include art assets. Then you should be able to get content updates and fixes delivered without needing to update the game from Play Store/AppStore.
• Development QoL, a bunch of smaller things that will help floursifter and maxchill to organize and work on content more easily. One major missing thing is metadata for content (for instance: when things have been edited and by who, is the content a draft or in testing, and so on).
• Automated changelogs. Currently it's hard for us to track what changes have been made in each content update and write those out in the announcements, and with Devtools 2.0 the idea is that the tools would write changelogs automatically based on what has been changed.

Plans before Wave 4

A lot of you are also anticipating for the next Wave, and we're well aware of this!

Before we release Wave 4, there are a few important things we need to address. One key priority is integrating watch support for iOS, a request we've heard loud and clear from both past Wave updates and our player community. Ensuring that step graphs are accurate is another critical issue that needs fixing before we can move forward with the next Wave. It's essential for new players to have a nice initial experience, and inaccurate graphs would be a big obstacle to that.

The to-do list includes:

Must have

• Watch integration for iOS. iOS is our main priority, but while developing it I will do some testing for the Android side to see its current viability. This feature has been on hold now while we worked on Devtools 2.0 and the new content update, but we get back to it after the release of this content update.
• Steps graphs fixed. Steps graphs are now broken and rather complex to correct as steps are being synced between the server and the client very differently compared to how this was in the past, and with smart watches making sure the graphs are correct will be even more complicated.
• Any remaining major bugs or issues fixed. Currently there are not that many, but we're anticipating that Flutter team would release a fix to older GPUs and Android versions so the game would work again for those who have older devices.

Nice to have

• One smaller content update in addition to upcoming Trinketry update.
• Introducing a few more QoL additions to the game to make the overall experience better.

As seen here, the list isn't very long by any means. We anticipate that finishing up our work with watch support for iOS will take some time, and it's hard to estimate exactly how long it will take, as we saw there were a lot of quirks that come with the integration.

We will be working as hard as we can to get these remaining things done and launch the next Wave!

Until next time

That's all for today, and it's going to be very exciting to have a new skill introduced to the game along with a plethora of other content. I hope people find the new skill both fun and useful - it's quite a big introduction with more than 70 new items added to the game.

Stay hydrated and keep walking! ❤️

Hello, and welcome back to the WalkScape DevBlog!

Over the past two weeks, we’ve been primarily focused on fixing critical issues that arose from the WalkScape engine rework, while I’ve been working on what we’re calling DevTools 2.0. Let’s dive in!

Hotfixes

After the engine update, we deployed a total of three hotfixes to address the most critical issues that were identified:

• Hotfix +413
• Hotfix +418
• Hotfix +419

With these updates, we resolved all of the most apparent and critical issues, including the traveling bug, WalkPedia issues, crafting issues, and rendering issues on PowerVR devices, among others. The game should now be stable again. We will still implement at least one or two more of these hotfixes, but the release schedule for those is not as urgent. My focus is now on developing DevTools 2.0 so we can introduce new content updates to the game as soon as possible.

Thank you for your patience. The engine update was substantial, and I'm glad that all of the critical issues that were introduced were things we could address quickly.

For those interested, the traveling bug was quite absurd: it was caused by your character's profile picture (PFP). When the game was loading and you were traveling, whenever you arrived at a new location, the game would update your PFP. I had made an error there, where this part of the code inadvertently replaced your game state with the state before loading steps.

Android 9, Android 10 and older Android GPU issues

One new issue was introduced in the new Flutter version, which is something that has broken the game to some players entirely and is not something we can fix.

People with older Android devices (A9, A10 era) have been experiencing crashes or major rendering issues. I’ve been doing my best to inform the Flutter team about this and push for a fix. You can check the issue I've reported here. It's already under their radar and something they seem to be working on, so no need to comment on that issue unless you've got some information that might help them!

The Flutter team has marked it as P1 priority, their second-highest priority level. I’m quite optimistic that this means they’ll release a fix in the coming weeks, but naturally, I can’t make any promises on their behalf. Once they do, we’ll incorporate it into the game.

DevTools 2.0 progress

Now that the game is stable again, I’ve shifted my focus to DevTools 2.0, while myzozoz continues working on fixing the remaining bugs and issues.

DevTools 2.0 has been mentioned quite a bit in our past dev blogs and communications. It’s basically our name for an improved internal toolset to help with content creation and development.

Working on these tools will take a significant portion of my time in the coming weeks. Our plan is to build DevTools 2.0 as quickly as possible so floursifter and maxchill can start working on our next content update. The more advanced features will come later—our top priority right now is just getting the tools ready so we can start delivering new content ASAP.

It’s still a bit too early to give an estimate on when the next content update will be ready, but all my effort is going into making sure we get it out as soon as possible.

Until next time

That's all for today! I hope you enjoyed the update. I can't say enough how excited I am to finally focus on DevTools 2.0 and what it will bring for all of you. Once it’s ready, content updates and feature development will run as separate pipelines. This should allow us to release content much more frequently than before.

Stay hydrated and keep walking, everyone! 💙

Flutter team today released their hotfix to fix problems that some Oppo device owners (and others with PowerVR GPUs) had, making WalkScape unplayable due to the game failing to render anything. This hotfix implements their new version, you can see their full changelogs here.

0.3.0-beta+419 - 2025-02-13

Fixed

• Updated to new version of Flutter, which fixes the rendering and crash issues on PowerVR devices, like Oppo phones
• A small improvement to error handling logic