XaiJu
Shattered Pixel
Shattered Pixel

patreon


Adjusting v3.3 Release Plans | Patreon Weekly #334

Hey Patrons! In this weekly I’m going to go over some changes I’m making to how I’ll be releasing the upcoming city quest. There’s also an audio Q&A this week, you can find timestamps for all the questions below.

Some of you might remember that the caves quest was released fairly incrementally. I first created a ‘tester area’ that players could muck around in as a patch for v2.1. v2.2 had a long beta that initially just expanded that area and didn’t even start with a playable quest. The first variant of the quest came a month into v2.2’s beta, and then the second variant came in v2.3.

While I don’t plan to copy this exactly, I think a more incremental approach is best here too, rather than trying to release the whole thing in one huge v3.3 release. A big part of this decision is also that some users have started reporting a fairly serious bug that I don’t want to wait months to release a fix for.

The bug is a race condition that results in a complete game freeze when brutes die over time while thrown weapons are stuck to them. I’ll spare you the full tech details, but a race condition essentially means that the bug is dependent on two sequences of code happening to execute in a certain order relative to each other, This is often dependent on a particular processor, which means most users never see this bug, but for some it happens every time!

So, my current plan is to adjust v3.3 to be a much smaller update that includes lots of small tweaks and fixes that I’ve already done, as well as an incomplete skeleton for the new city quest. This will be similar to the ‘tester’ area that was released in patches for v2.1.

If I do this right it won’t substantially delay the eventual full release of the city quest, and it does mean that v3.3 can release relatively soon, probably around mid November, instead of almost certainly releasing in 2026.

Audio Timestamps

This month there were 12 questions from 6 different Patrons.

Comments

Thanks! I'm already on lineageOS so that my OnePlus 7 Pro isn't running on Android 12. I would like to upgrade but most other phones feels like a downgrade (as discussed prior, I despise display cutouts). I'm definitely at a point where lack of bootloader unlock support is a dealbreaker for future devices as well. My plan atm is to experiment with magisk and rooting while I'm still on Android 15, and then fully move to lineage + microG (with magisk spoofing if I feel like it) when I update to Android 16. I will likely keep Google Play around either directly or via Aurora, but do want to try and migrate to Apps available through F-Droid or Obtanium wherever reasonable. If you're avoiding API 35+ due to things like edge to edge enforcement, I do think it's worth noting that the edge to edge enforcement is only being forced due to Google Play and it's minimum target API requirements. The latest Android versions themselves have no such requirement for target API levels.

Shattered Pixel

BIG kudos for your Google answer! I wish you courage for the move. Myself, I buy my hardware according to the Lineageos / microG support lists and have been on that track since it was named CyanogenMod... The only compromise I do is - I need org.thoughtcrime.securesms aka Signal, and for that Aurora and enabling GSM (microG's - no Google app installed)... I'll probably also keep avoiding API level 35 due to its insulting aspects (for devs), and once that is unsustainable I'll consider going offline entirely... From mobile devices that is.

Robert Heinig


More Creators