While setting up my HS/RL system I missed the point in my tutorial to set up the "Default Frontend Path" in the General Settings section and ended up only configuring the default Frontend in the RLUI section. This leads to an obscure and little informative Scripting Error when starting games from HS while launching games from RocketLauncherUI worked like a charm. By using Google i found a couple of threads where people had the same problem. Some suggested to copy their databases to the RocketLauncherUI directory while others set a link in the file system to point to the correct databases... So you can see this is a real problem for your users. In my opinion it doesn't make any sense to ship RL with this path pre set to anything because you should encurage users to correctly utilize the -f parameter when calling RL in all cases. For new HS/RL users it is kind of confusing and not very intuitive having to set the same setting (Default FE) twice in the same tool. My suggestion to improve the situation is this:
Solution 1: Remove the pre set path from RL install files so HS users get a more informative error message when they fail to set up the path and still try to call RL via legacy interface without the -f param. That way they may even be motivated to fix the problem at the source (update HS) instead of using some obscure legacy setting in RL.
Solution 2: Set the path automatically when the user sets up his default FE in the RLUI tab. In my opinion there is little reason not to do so since power users who might want to have multiple FEs should be able to configure/update HS correctly to deliver the -f parameter in the first place while new HS users would have an easier and more intuitive setup experiance without having to set up the same default FE path twice. Non-HS users would not be affected anyway since they don't need to set the legacy path at all.
Solution 3: Bleasby seems convinced, that the legacy setting needs to stay around for some reason and therefore can't be set automatically when the user changes his default FE in RLGUI. In this case I suggest that you ask the user via msg box only when he chooses HS as his default FE if he also would like to update the legacy setting in RL. We know if the user is choosing Hs by analysing the path (executalbe) and/or the RL/RLUI plugin he is selecting. All non HS users would not be affected at all. Bleasby thinks this could be annoying for the power users who switch the default FE all the time. But even that could be easily avoided by having a simple "Don't ask me again" option in the msg box.
Solution 1: Remove the pre set path from RL install files so HS users get a more informative error message when they fail to set up the path and still try to call RL via legacy interface without the -f param. That way they may even be motivated to fix the problem at the source (update HS) instead of using some obscure legacy setting in RL.
Solution 2: Set the path automatically when the user sets up his default FE in the RLUI tab. In my opinion there is little reason not to do so since power users who might want to have multiple FEs should be able to configure/update HS correctly to deliver the -f parameter in the first place while new HS users would have an easier and more intuitive setup experiance without having to set up the same default FE path twice. Non-HS users would not be affected anyway since they don't need to set the legacy path at all.
Solution 3: Bleasby seems convinced, that the legacy setting needs to stay around for some reason and therefore can't be set automatically when the user changes his default FE in RLGUI. In this case I suggest that you ask the user via msg box only when he chooses HS as his default FE if he also would like to update the legacy setting in RL. We know if the user is choosing Hs by analysing the path (executalbe) and/or the RL/RLUI plugin he is selecting. All non HS users would not be affected at all. Bleasby thinks this could be annoying for the power users who switch the default FE all the time. But even that could be easily avoided by having a simple "Don't ask me again" option in the msg box.
Last edited:
