Search results

This just happened to me, presumably from looking at ascension histories. It looks like the same thing?

Apparently, this does not work for the current season (67). Apparently the HTML after "Newest Born" in the info booth makes the script fail no matter what when it comes to displaying the correct results.

So occasionally beard prediction fails as depicted in the attached screenshot. It stays that way and only ascending fixes it for me.

I have noticed that after running the script (with abortOnChoiceWhenNotInChoice set to false), afterwards mafia does not recognize my torso awareness anymore. Mafia also thinks my stats are severely below what they actually are (this only gets fixed by logging out and back in again). Another...

This is what I get with the most current and all older jar files I still have on hand: Sorry for the rushed report. edit: this is onopenjdk version "17.0.4" 2022-07-19

Okay, I guess that was it. It was at 20k, I upped it by a bit and then it purchased a DKLP through the mall. Two questions, though: 1) Why would it not rather create a DKLP instead of purchasing through the mall? I got all the ingredients. 2) Is there a way to set that prefref somewhere else...

When trying to eat a digital key lime pie, either through item manager -> food -> digital key lime pie -> consume -> 1; or cgli -> eat digital key lime pie it fails: However, when I acquire a digital key separately beforehand, mafia will cook and eat the dklp. The first time this problem...

I see that since Jan 12, ChIT has beard tracking. But I cannot find any sort of predictive tracker in the effects pane. Do I need to look somewhere else? Enable it first? By the way, I also would really love tracking support for cosmic bowling ball (i. e. when it will return) and cursed...

If anyone had the same problem as I had with either PW's or Veracity's fix: It seems like it was just a caching error. Delete or remove the old playername_pvp_season_n_.dat from your data folder, run the script again and it should be fine.

Ever since this version (also newer versions) I cannot launch relay browser anymore... edited to say this is on KDE with Java 11.0.11, and for all intents and purposes, fiddling with the system settings regarding default browsers did nothing. Should I file a bug report?

This is a really welcome addition. I suggest adding the monsters to fight, though (not sure if these show up in-run; I am in aftercore but as these are all free fights, they are valuable in either case).

Apparently, Ezandora just updated all (?) of her scripts and it works fine now.

Yes, GUI.

I am usually just checking equip and cast because those use no resources (equipment) or a neglible one (MP). So the change made it necessary for me to click twice for switching from one to the other (uncheck equip, check cast, and vice versa) instead of just one click with the radio button...

/hardcore is telling me that this is due to the most recent ASH cleanups in mafia, but ever since 19889/19890, the HP and MP bars in the charpane are blue/blue/blue instead of their usual green/orange/red.

Actually, several people still do it. It's good for PvP. :D

I believe the latest fix to deal with the birdwatching iotm broke older skills that have an apostrophe in their name. Trying to cast additional turns of a skill's effect with the arrows next to it results in > cast 1 Fat Leon27s Phat Loot Lyric Could not find a known, usable skill of yours...

When trying to get +740 fuel, I lately often get just the error message in the gCLI. +370 fuel works fine, however. Another thing the script lately does which it has not done before for me is put on Travoltan Trousers for the sake of purchasing things but then not putting on the previous pants.

I tried this for a while... and it worked... and then it stopped working? :confused: I think it might have gotten broken by the LOV tunnel enemies? I dunno, I need to test this further.

Yeah, I switched back to Firefox as well (which has its own problems). If you could, please post a link to some centralized discussion of this problem where the Chromium developers are most likely to see it. Also, thanks to Veracity for getting to the bottom of this.