Wayland Update, Texture Pack Fix

I modified download_resources.py by adding a small if loop that examines the path requested, and modifies it if it doesn't match the sandbox layout.

This is not a permanent fix, as I still don't understand why the paths are being configured like this, but for now, it does resolve the missing textures the Flatpak release was experiencing much better than my last fix, as the textures are actually properly transparent now.

Also resolved is the issue of it not loading on Wayland. The modified code is in my fork of Amulet - once the wxPython framework gets updated (it was recently patched but the upstream fix hasn't made it into a full release yet), this Wayland work-around won't be needed.

The Meta Data Update (v0.10.36)

While I haven't yet resolved the missing textures issue, I have fixed the metadata in the Amulet Flatpak so now the version number, icon, and .desktop launch runner are all present and verifiable with FlatSeal.

As with the previous release, the optional amulet.sh script can automate the installation and launching of the Amulet flatpak.

Ubuntu users are strongly encouraged to use the script unless they've manually enabled Flathub already.

v0.10.36 - The Flathub Friendly Release (kinda)

The flatpak build manifest has been cleaned up and streamlined, and the internal naming conventions have been overhauled to conform to Flathub standard practices.

After downloading the .flatpak file included below, you'll need to manually install it by running flatpak install -u amulet-x86_64.flatpak from the folder you downloaded it to. To launch it, run flatpak run io.github.evilsupahfly.amulet-flatpak.

Or, you can just download the included amulet.sh script, written to automate these steps for you. However, since GitHub doesn't save file permissions, if you opt to download the script, you may need to set the executable bit or confirm that you want to run the file as a program.

The flickering UI which is currently plaguing the Flatpak build also impacts upstream Amulet and is being worked on upstream by the Amulet devs. If you want to help, refer to Amulet Upstream Issues #127 for details.

Just a side note - since this is a pre-release, it was built against a debug build of Python v3.12.7, so launching from the terminal will likely output a LOT of (probably useless to you) information, most of which can be safely disregarded. Unfortunately, on lower-end machines, this debug build also runs slower.

I'm still trying to fix the missing textures issue, and aside from this, Amulet is still usable as a Flatpak. However, until the missing texture issue is finally resolved, future versions of flatpak Amulet will probably also be debug builds.

That said, you can clone this repository's testing branch and comment out these three lines in io.github.evilsupahfly.amulet-flatpak.yaml...:

  - --env=PYTHONDEBUG=3
  - --env=PYTHONVERBOSE=3
  - --env=PYTHONTRACEMALLOC=10

... to build your own local version of the flatpak, which can be installed using the instructions above. If you opt to clone and build locally, be sure you've installed flatpak-builder from your package manager, and org.freedesktop.Platform and org.freedesktop.Sdk from Flathub, and that you're running in a Python virtual environment. Also make sure your GPU drivers are up to date since they handle the OpenGL stuff that Amulet depends on, though, Flatpak will ask you to update them anyway if they're behind.

I found PythonZ to be quite the useful tool for managing my venvs, and suggest you give it a try. To simplify things, I added this function to my $HOME/.bashrc to facilitate the creation and usage of my various testing venvs using PythonZ.

If you want to automate this entire process of building and installing locally, you can clone the testing branch and run do_this.sh. Run it once with no options or with --help to see what it can do. Just a side note however - if you opt to generate a new pip-gen.yaml file using the --pip-gen option, you'll likely run into issues during the build process as some of the auto-generated wheels will generate error messages. For this reason, I manually switched many of the wheels to source archives, since flatpak-pip-generator doesn't have an option to prioritize source over wheel.

Initial Release, v0.10.35

It finally works! It was a hell of a ride, but the flatpak actually works!

Since this flatpak is based on Amulet 0.10.35, I've simply followed Amulet Team's version numbering for this release, and will continue to do so in the future with updates.

After downloading the .flatpak file, you'll need to manually install it by running flatpak install amulet.flatpak from the folder you downloaded it to, then, run flatpak run com.github.amulet_map_editor, or, you can download amulet.sh which automates all this for you.