Bale
Minion
Jick's place.php thing, while no doubt wonderfully effective for refactoring the game on the back end, is troublesome to the usefulness of KoLmafia's relay override scripts. Things like manor.php use to be just fine. Now we need to have a relay for place.php since its address is place.php?whichplace=spookyraven1 and could make it difficult for the user to also have an override for place.php?whichplace=KOLHS, just to name two scripts I use. I've got them sorted out by using a place.php override that does this:
Let's face it, this solution is kinda kludgy. I would like to propose a better solution KoLmafia could implement. I believe someone mentioned this idea in some thread somewhere, but pardon me for not giving proper credit to the original proposal.
In the relay directory should be a subdirectory /relay/whichplace and in that subdirectory, an override called spookyraven1.ash would be applied as a relay override to place.php?whichplace=spookyraven1. If we did this, all place.php locations could play nicely with each other, without troubling the user to untangle the knot of overrides as I did in the previous example.
PHP:
import "manor.ash";
import "kolhs.ash";
void main() {
switch(form_field("whichplace")) {
case "spookyraven1": main@manor();
break;
case "KOLHS": main@kolhs();
break;
}
}
Let's face it, this solution is kinda kludgy. I would like to propose a better solution KoLmafia could implement. I believe someone mentioned this idea in some thread somewhere, but pardon me for not giving proper credit to the original proposal.
In the relay directory should be a subdirectory /relay/whichplace and in that subdirectory, an override called spookyraven1.ash would be applied as a relay override to place.php?whichplace=spookyraven1. If we did this, all place.php locations could play nicely with each other, without troubling the user to untangle the knot of overrides as I did in the previous example.