SketchySolid
Member
Yeah, sorry. I goofed up updating to the latest version. The latest version is very nice. Thanks for the continued updates!
A Multi-Armed Bandit PVP Script
- Thread starter WARriorer
- Start date
Heads up: Because of the new "modifier" change in mafia, if the script throws an error pertaining to "modifier", UberPvPOptimizer will have to be updated (from here: https://github.com/Loathing-Associates-Scripting-Society/UberPvPOptimizer - note that you might need to delete your old version of UberPvPOptimizer if you previously manually downloaded the ASH script from within the forums here)
There was a bug where the number of minis was hardcoded to be 12, which is not true for drunken season. This has now been fixed, but the stats may be wrong with the new mini in play. To do a hard reset, type "set myCurrentPVPSeason=-1" in the CLI.
The newly implemented bandit algorithms should get you back up to speed (with the optimal mini) exponentially quickly, so one doesn't need to worry (too much) about having said stats being reset.
The newly implemented bandit algorithms should get you back up to speed (with the optimal mini) exponentially quickly, so one doesn't need to worry (too much) about having said stats being reset.
Crowther
Active member
That's why that started happening! I thought it was a new mafia feature.
autoscend saves the old value, sets the preference to true and runs. If autoscend is not allowed to finish normally it will sometimes be in a state where it is true and not restored to the previous value. The next run of autoscend will thus restore the value to true. I tracked this down because it is a global preference and I started seeing the clutter for farming characters who weren't going to do anything with the information.
TBH, I generally turn it off while autoscend is starting up, with the caveat that I am basically on my own for support if it's broken.
I really need to get back on my project to provide separate logging levels for what's recorded vs. what's in the gCLI. I don't care if a script fills up my log file, but I do care if it adds so much useless clutter to the gCLI that the useful information scrolls out of the buffer very quickly.
I really need to get back on my project to provide separate logging levels for what's recorded vs. what's in the gCLI. I don't care if a script fills up my log file, but I do care if it adds so much useless clutter to the gCLI that the useful information scrolls out of the buffer very quickly.
Just pushed a fix for this. Sorry about that!