I understand what you're asking for, but I'm not sure there's a good, automated way to do it at present. I could set up a bunch of redirects but then that just puts the manual management burden on me rather than on you.
Although I get your point about the PPG front-end (which will turn 11 years old in a few days, yay us), it's not a snap-your-fingers-and-it's-done process.
That said, if there's someone out there who is interested in presenting a tangible plan for more-or-less smoothly moving us from our rather rickety old Joomla install into something new that (among other things) would support your needs, I'd be happy to discuss it.
Here is a suggestion: move PPG mods to GitHub, as was already done with BG1UB. GitHub has a "release" process so you can designate a certain commit as a tagged release, and you can optionally designate a release as a "pre-release" or not.
We have a PHP script hosted at this URL:
http://lynxlynx.info/ie/modhub.php?GITHUBACCOUNT/REPOSITORYNAMEThis URL is a stable URL that always redirects to the latest "release" (ignoring "pre-release" versions) on GitHub.
For example, BWS is now using
http://lynxlynx.info/ie/modhub.php?AstroBryGuy/bg1ub for BG1UB.
G3 is apparently moving to the GitHub model now too. It would be very helpful if PPG mod authors could do the same, especially for mods that are still under development, e.g. Kulyok please consider this for Reunion and let us know if you need any help figuring out how to set up a GitHub repository for it.
Thanks and happy new year!