version 1.6.0

As with all the "releases", this is just marking a certain point in the state of the repo. To make use of this, you can download a .zip or .tar.gz archive of the repo using the asset links below. (And then start with the toplevel readme.)

---

Since I've switched to using the Firefox browser personally, I wanted to make a Firefox version of this extension. It was a bit of a journey but here we are.

So the main thing in this new version is the addition of the Firefox extension (the Chrome extension is still available). The instructions have been updated accordingly.

I've also done a minor tweak to the Chrome extension, removing an unneeded "scripting" permission in its manifest.

version 1.5.1

As with all the "releases", this is just marking a certain point in the state of the repo. To make use of this, you can download a .zip or .tar.gz archive of the repo using the asset links below. (And then start with the toplevel readme.)

---

Small release to pick up these changes/fixes:

• Fix for browser extension handling the download of zipfiles with names containing "bad" characters (that are not valid for URLs).
• Some fixes for savegame-loading and other operations in cases where the path contains a space.
• More documentation about installing the icon for "shortcut" files in various distros.
• More documentation about installing utility dependencies.
• Documenting that I've also run this stuff on Pop!_OS.

Both the browser extension and the quakelaunch script are touched here. The fixes can be taken on board for an existing installation just by reloading the new extension files and replacing the script; no other actions needed.

version 1.5.0

As with all the "releases", this is just marking a certain point in the state of the repo. To make use of this, you can download a .zip or .tar.gz archive of the repo using the asset links below. (And then start with the toplevel readme.)

---

The only change here is to designate the "Manifest V3" version of the Chrome extension as the default/stable one. It should work on Chrome version 110.0.5469.0 or later.

If you have the old version of the extension installed, you can remove it and then load this newer version (which is now the occupant of the browser_integration/chrome_extension directory).

version 1.4.0

As with all the "releases", this is just marking a certain point in the state of the repo. To make use of this, you can download a .zip or .tar.gz archive of the repo using the asset links below. (And then start with the toplevel readme.)

---

If you're starting from scratch with this version, well the docs have been updated accordingly so you'll be fine. If you're using the previous version and want to migrate... I'll describe the migration steps in a minute, but the rationale for them is clearer if we talk about the changes first. So let's do that!

• One of the most obvious changes is that "quakelaunch.conf" will no longer sit next to your "quakelaunch" script; instead it will be stored according to XDG config-file placement rules. (Normally this means it will be in the "~/.config/quakelaunch" directory.)
• A "quakelaunch-defaults.conf" file will be autogenerated in that same location, containing the defaults for all the properties which can be set in "quakelaunch.conf".
• There's no longer a separate "quakecleanup" script. That functionality is now handled by the main "quakelaunch" script. The quakecleanup.desktop file has changed accordingly.
• Documentation now directs putting "quakelaunch" in your PATH, so that the .desktop files no longer need to specify an explicit path for it.
• The MIME type definition for Quake .bsp files now uses the file header rather than file extension to identify them. This should avoid any conflict with other uses of the .bsp extension.
• FYI a new "manifest v3" version of the Chrome extension is available in the repo, in a directory next to the current ("manifest v2") version. However, it is recommended to stick with the current one for now. (Eventually Google/Chrome will force us to switch to the new one.)
• And there's various documentation updates about the above changes, as well as a rework of how the docs describe the way the browser extension works.

---

OK, here's what migration of an existing setup would involve.

First, apply the new version of the the Quake .bsp file MIME type:

xdg-mime install --novendor --mode user x-bsp-map.xml
update-mime-database ~/.local/share/mime

Next:

• Remove your installed "quakecleanup" script.
• Replace your installed "quakelaunch" script with the new one.

Now manually run the new installed "quakelaunch" script once, without arguments, just to import your current "quakelaunch.conf". (You can immediately quit out of Quake when it launches.) In the shell where you ran "quakelaunch", you'll see an info message about where your "quakelaunch.conf" now lives.

If the installed "quakelaunch" script isn't in your PATH, you may choose to move it into some PATH directory at this point. (I'd recommend doing so if possible.)

Before making any .desktop file changes, take note of whatever modifications you previously made to the installed .desktop files. Probably if you made any changes, it was only to set the Icon path value in "quake.desktop", and maybe also setting the Exec path values in one or both of the .desktop files.

Check out the new .desktop files here and see if you need/want to apply those same changes. E.g. maybe you need to set the Icon path in "quake.desktop". And if the installed quakelaunch script is not in your PATH, modify the Exec value in both "quake.desktop" and "quakecleanup.desktop" to specify the complete correct path to "quakelaunch".

OK, now you can apply the new versions of the .desktop files:

xdg-desktop-menu install --novendor --mode user quake.desktop
xdg-desktop-menu install --novendor --mode user quakecleanup.desktop
xdg-mime default quake.desktop application/x-quake
xdg-mime default quake.desktop application/x-bsp-map
xdg-mime default quake.desktop application/x-qz
update-desktop-database ~/.local/share/applications

No migration needed for the browser extension, since the current version hasn't changed. As mentioned in the relevant readme, I don't generally recommend switching to the "manifest v3" version yet.

I'll insert my standard apology here for not having a cleaner process for installation or upgrade/migration, but I'm pretty dubious that there are many (if any) folks other than me that are using this. :-)

version 1.3.0

If you're updating to this release from the previous one, FYI the non-documentation things that have changed are:

• The quakelaunch script. Get the new script and replace your old one with it.
• quakelaunch.conf now supports two additional settings: alkaline_basegame_args and alkaline_gamedir. These work just like similar args for copper and ad; see the updated quakelaunch.conf in the repo for examples. If you have Alkaline installed you can add these settings to your quakelaunch.conf.
• The browser extension is updated, so if you're using this extension you should update the files and then re-load it into Chrome (using the circular-arrow "reload me" button on the "Open with Quake" tile in the extensions manager).

Do I need a better packaging and upgrading solution for all this? Probably! If you're using this, be sure to let me know, especially if you have a preferred solution for how the distribution of this stuff should be handled.

---

OK the changes are:

• When quakelaunch examines readme/doc files in a release to try to determine its dependencies, it will now also look in "*.md" (markdown format) files.
• As implied above, quakelaunch can now handle releases that depend on Alkaline in the same way as those that depend on Arcane Dimensions and Copper. Not a lot of those yet, but hey we can be ahead of the curve here.
• If an archive installed by quakelaunch has Quake-important folders (like "maps") inside a folder that looks like a base mod dependence (like "copper", "quoth", etc.) ... quakelaunch will now handle that folder structure and also take that organization as a signal of a dependence (unless the release turns out to have its own progs.dat, making it standalone). The Quoth and missionpacks and Arcane Dimensions, Copper, and Alkaline sections of the docs go into a bit more detail, but the bottom line really is that quakelaunch will just handle a few more releases correctly and you shouldn't have to worry about it.
• The browser extension now properly handles downloads that rely on the "Content-Disposition" header to set the filename, like downloads from Slipgate Sightseer.
• The source for the browser extension is also now Apache-licensed. I had to bring in some other Apache-licensed code to handle that header, so might as well apply it to the whole deal.

version 1.2.0

For updating to this release from the previous release, you only need to make sure you get the new quakelaunch script.

Various pieces of documentation (md files) have changed too, just FYI if you are storing these somewhere outside the repo.

There is a nice new option available in quakelaunch.conf, called create_filename_symlinks. This is false by default but you can set it to true to fix a kind of Quake-on-Linux issue caused by filename case sensitivity. The quakelaunch.conf file in this repo contains a comment block that explains further.

Another new minor option you can set in quakelaunch.conf is md_viewer. As with the other "viewer" options you can set this to the application that should be used to view the relevant kind of readme files, in this case ".md" files. If you know that the correct application would run when double-clicking on such a file, you can just use a value of xdg-open for this option.

OK all that being said, here's the complete list of changes since the previous release:

• Better handling of releases that have a dot in their name, for example "smej2_1.1.zip". Issue #20 has a bit more discussion of this.
• Handle releases that contain directories with weird permissions. A bit more detail in the commit, but this should be a transparent improvement that you don't have to know about.
• Updated docs to include mention of the Ironwail Quake engine where appropriate.
• Support for viewing ".md" readme files, as mentioned above.
• Support for auto-creating file and subdirectory symlinks with upper/lowercase name variants, as mentioned above.

version 1.1.0

If you're updating to this release and you previously went through installation with the files/instructions from version 1.0.0, there's not much you really need to change. The main thing is to get the new quakelaunch script. Everything else is just minor doc tweaks and some minor comment changes in quakelaunch.conf.

• Better detection of when a non-standalone mod does or does not depend on AD (related to issue #9).
• Misc polish to docs and comments (issue #12 and more).
• Remove .bat and .cmd files during mod installation (issue #14).
• Assume a .pak or *progs.dat file indicates the top of mod directory structure (issue #14).
• Give .jmf/.rmf/.vmf files the same treatment as .map, i.e. put in maps dir (issue #14).
• Avoid trying to open directories that have readme-like names during readme preview (issue #15).

version 1.0.0

Features look good at this point IMO, and no known bugs, so let's call it a "release".

To use this, download or clone the repo and then start with the README.md in the top directory. All the instructions are in markdown so it may be easiest to read them online.