Need archive to work. Download it from https://foundryvtt.com/me/licenses.

You can download it manually and place it with the PKGBUILD, or you can use the download_foundry.bash script in the repo to download it with your foundryvtt.com credentials, and you can configure makepkg to invoke the script automatically for you by adding the following line to ~/.config/pacman/makepkg.conf:

DLAGENTS+=("foundryvtt::./download_foundry.bash")

@GrantMoyer Thanks! The script works great, but the zip didn't pass sha256:

4b3cc09d8274d079222abf71440bc98e01a6dec7c6978e117a5d3d35c34baabe FoundryVTT-Linux-13.351.zip c3e535264274bb9092234aedc7b1e945b4767ca62f9b9da1e088a19beabee9b5 FoundryVTT-Linux-13.359.zip (website doesn't force latest version) 93b7563e2d4ede16d505eecb74ff11cb2835d14e8fc138db30954b20e3498412 EXPECTED for 13.351 zip

They don't list the sha256 on their website, so I'd use SKIP as they can change the file at any time without marking it as a new version. By computing it yourself you're just adding more maintenance burden on yourself, can break randomly, and really only serves to verify that the download wasn't partial.

I ported your script to posix shell and added pass support and also a file-backed store which is more common for download helpers: https://gist.github.com/Caellian/6d3b0ce9cba85368354f7858ce0c92f4

@linuxham, See pinned comment.

:: (1/1) Parsing SRCINFO: foundryvtt ==> Making package: foundryvtt 13.351-1 (Wed 11 Mar 2026 06:21:58 PM EDT) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading FoundryVTT-Linux-13.351.zip... FoundryVTT-Linux-13.351.zip.part must be downloaded from https://foundryvtt.com/me/licenses. See comment in ./download_foundry.bash for automatic download. ==> ERROR: Failure while downloading foundryvtt://FoundryVTT-Linux-13.351.zip Aborting... -> error making: foundryvtt-exit status 1 -> Failed to install the following packages. Manual intervention is required: foundryvtt - exit status 1

@caellian I think I've found an acceptable way to support automatically fetching the FoundryVTT package. I've added a script, download_foundry.bash to the repo which can be invoked manually to download the package after prompting for foundryvtt.com credentials.

The script is also compatible with makepkg's DLAGENTS functionality, so you can configure makepkg to invoke download_foundry.bash for you by adding the following line to ~/.config/pacman/makepkg.conf:

DLAGENTS+=("foundryvtt::./download_foundry.bash")

This way, the PKGBUILD is not interactive by default, but users can opt in to interactive credential prompts.

Let me know if you have any trouble with the script; hopefully the upcoming major version release of Foundry doesn't break it.

@GrantMoyer Thank you for fast response. After reading though the wiki and consulting ChatGPT I see that local:// is the only approach that doesn't violate the license and wouldn't break. ChatGPT suggested that a script like fvtt_login.py can be provided through a separate package which would allow users to automate the download, which actually seems like a much better approach.

I made the python script interactive and handle arguments: https://gist.github.com/Caellian/aade59087699f4fdc48fd510e95e7790 It's vibe coded with Claude, tested, and it seems to work for now.

@caellian I've considered downloading the foundry package automatically, (I even had an update script which did it for a while), but the download requires authentication and interactive PKGBUILDs are considered bad practice. See Nonfree applications package guidelines § Missing files.

I consider browser automation an overkill and fragile approach to the problem, but I recognize it'd be convenient to have the packages downloaded automatically, so I'll look back into best practices and see if I can come up with a way to reduce the friction.

Add selenium please and make the PKGBUILD use it.

EDIT: Contained code that's written poorly, see my later comment for a python script to download the file through terminal.

Good to know! Thanks for the help.

@aripa49 The best way is to flag the package out of date. I'll get an email notification and update it.

Note that updating your local copy of the PKGBUILD typically only requires bumping the pkgver variable and setting the first element of the sha256sums array to 'SKIP'.

I see version 13.350 is available. Is there any way to help on keeping this up to date?