notacarrot wrote: ↑Sat Feb 25, 2023 1:18 pm
KanaryKrusade wrote: ↑Sat Feb 25, 2023 3:19 am
Melanthios wrote: ↑Sat Feb 25, 2023 1:44 am
Aiite my turn to be confused, I just redownloaded and extracted into the folder and I'm still getting frozen. What am I doing wrong?
Also yes, Valleymoon as I've said before thank you for your work and efforts
Step-by-step of what I did, and I think I might know what's missing from yours:
-Re-download
-Drop Cheats/Config/Inject into its proper place
-Also drop main/package from the source folder that comes in the download (this is what fixed mine)
-Make sure cheats.js is updated from the pastebin
Lol, you did even more than me, I didn't redownload it at all, I just took the originals and dropped that back into the game folder after editing the cheat.js to be how I want (because if you edit it after you run the game at all, the cheats simply won't work). So in my experience, at least how I understand it is that the node js app snapshots all the files in the folder with it and can only run with those exact files and it needs to be replaced each time you change something to take another snapshot.
That's probably not what is ACTUALLY happening, but from the outside looking in, that seems to be what's happening.
Funny, node does not snapshot the files at all. You should be able to edit cheats.js, then relaunch InjectCheatsF5 and it will reload the new cheats.js file. I obviously do this a lot since I'm fairly constantly modifying it
I don't doubt your experience of it, since there can always be caching happening at many different levels (even fi;esystem), just wonder why you are finding that to be the case when I do not. Maybe try adding/removing a cheat to the startupCheats after running the game, close and reopen. This would give you a definitive answer as if the new cheat does run on starup, it must be seeing the new version of cheats.js, if not then you know there is some caching/snapshotting happening somewhere.
@KanaryKrusade, main.js and package.json from the source folder aren't used at all if you are running the exe, so it must have been something else you changed at the same time.
@Melanthios, I don't like the nullify command, it runs a load of cheats that are old and were there before I started maintaining this. Last time I ran it I discovered w3 shrinehr and some other old cheat broke my account by lvling my shrines to 10k+, therefore they got removed. I will give it a go now and see what's causing it tho...
aleyre wrote: ↑Sun Feb 19, 2023 4:24 am
Frongly wrote: ↑Sun Feb 19, 2023 1:17 am
wh0oot wrote: ↑Sat Feb 18, 2023 9:48 pm
Once your obols are rolled perfect they stay like that, even if you launch without cheat. New obols you loot
without wide perfectobols activated will not change.
I mean I rerolled the perfect obols to not be perfect obols, relaunched f5 (have not activated perfectobols), then it sets all my obols to perfect obols again on launch. I made sure to cloudsave after I rerolled them as well.
Wide Obols is currently enabled even if you disable it.
Hopefully it'll be fixed.
This can ruin obols for a lot of people since what is deemed as perfect isn't perfect for everyone, especially if you use LUK on Droprate obols and you're not on a Maestro it'll roll them for the main stat of whatever class you're on.
I see what you mean now, my apologies, this was a mistake on my part, forgetting to check if you actually had the cheat enabled and rolling on player load regardless, I have fixed it now, and also added a config option that allows you to choose your preferred stat to be rolled on obols if you do have it enabled. You can pick "PRIMARY", "STR", "AGI", "WIS" or LUK"