There's a thread I created here 6 years ago that I needed to update the download links on. The files are hosted on Google Drive, and are configured to allow anyone with the link to download them.
The problem though, is that the forums are mangling the link as part of the outgoing link tracking, but then not properly de-mangling them for the redirect, which causes the query parameters to not be interpreted properly by Google Drive. This results in users needing to request access to a file that they shouldn't need to do so for.
Here is one of the links, as I entered it into the BBCode:
https://drive.google.com/file/d/0B40Xy8VSKqoOTnE3bC1xdlEwVEE/view?usp=sharing&resourcekey=0-iqlE98_7mDhZInXkO63jRg
This is how the forum mangles it:
https://www.construct.net/out?u=https%3a%2f%2fdrive.google.com%2ffile%2fd%2f0B40Xy8VSKqoOTnE3bC1xdlEwVEE%2fview%3fusp%3dsharing%26amp%3bresourcekey%3d0-iqlE98_7mDhZInXkO63jRg
According to https://deref.link/, this is how the forum is redirecting users:
https://drive.google.com/file/d/0B40Xy8VSKqoOTnE3bC1xdlEwVEE/view?usp=sharing&resourcekey=0-iqlE98_7mDhZInXkO63jRg
They key difference between this and the original link is the ampersand. The redirect has it encoded for xml, and it mucks up the parameter name.