Comment 1 for bug 345171

Right. However, that's just the surface problem. The underlying problem is: if I have multiple versions installed and I click on an armagetronad:// link, which should be launched? Just changing the .protocol filename and and exec line won't solve that (unless that causes the browser to display a 'multiple applications registered for that protocol, which one should we pick?' selection box). I'd suggest to
a) shorten the protocol to arma://. We're rebranded to armacycles on paranoid distributions.
b) in addition to the arma:// protocol, which is handled by the last (highest, if possible) installed version, register arma03:// handled by the last installed version from the 0.3 series and arma031:// launching 0.3.1 specifically, multislot or not.
The added benefit of b) is that users of 0.3.1 will be told right away that clicking on an arma032:// is futile.