AzaharPlus 2124.3-A is the same as Azahar 2124.3 except for this:

• Compatibility with all game files. If a file works with any Citra fork, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.
• Compatibility with older CPUs (no SSE4.2 required)
• Compatibility with Android 9

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2123.3-A is the same as Azahar 2123.3 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

Changelog specific to AzaharPlus:

• Fixed recurrent crashes in certain games with hardware shaders enabled

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2123.2-A is the same as Azahar 2123.2 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2123-A is the same as Azahar 2123 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

About compression and encrypted games:

• The "Compress installed CIA content" feature works as intended with encrypted CIA files.
• Compressing an encrypted CIA will save no space, so it is pointless.
• Compressing an encrypted 3ds/cci file will save as much as a trim would. If the file is already trimmed it will save nothing.
• I will look into adding a decryption step before the compression but I don't consider it a priority so don't expect anything in the short term.

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2122-A is the same as Azahar 2122 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2121.2-A is the same as Azahar 2121.2 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

Changelog specific to AzaharPlus:

• Fixed a crash that would happen when launching CTGP-7
• AzaharPlus can now use files coming from the "set up system files" feature of Azahar
• Possibility to remove the encryption from files coming from the "set up system files" feature of Azahar and make them usable with any other Citra fork (Window an Linux, file > remove azahar encryption)

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2121.1-A is the same as Azahar 2121.1 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

⚠️⚠️⚠️ THIS VERSION INTRODUCES A COMPATIBILITY BREAK FOR SAVE STATES ⚠️⚠️⚠️

Save states created in versions 2121 and earlier will no longer be loadable in versions 2121.1 and later.
You need to use a game's actual save system to cross over.
This is a reminder that save states are brittle by nature and should never be your main saving method.

⚠️⚠️⚠️ THIS VERSION INTRODUCES A COMPATIBILITY BREAK FOR SAVESTATES ⚠️⚠️⚠️

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2121-A is the same as Azahar 2121 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2120.2-C is the same as Azahar 2120.2 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

Changelog compared to AzaharPlus 2120.2-B:

• Logo attribution added to the about section
• fixed crash that would happen when a SecureInfo_A file is used
• fixed multi-language support on linux and windows
• the windows release is now a zip with everything it needs inside
• the linux release is now an appimage

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

AzaharPlus 2120.2-B is the same as Azahar 2120.2 except for these features:

• Support of 3DS files. If a file works with earlier Citra forks, it works with AzaharPlus.
• Ability to download system files from official servers. No need for an actual 3DS.

The windows build only contains the executable.

You need to already have Azahar 2120.2 (MSYS2 version) and put the AzaharPlus executable next to the Azahar one.
It will create its own user directory so it won't step on Azahar's toes.
You can copy paste from the Azahar user dir to get your saves etc.

The Android build is available in 2 flavors.

One that has the same application id as Azahar, so it will replace it on the device.
Its display name is "AzaharPlus".
Use this one if you have other apps that target Azahar, like a frontend for example.

The other has a new application id so it can coexist with Azahar without issues.
Its display name is "+AzaharPlus+".

EDIT: Due to an issue with the logo attribution, I replaced the binaries in this release by the ones from version C