-
Notifications
You must be signed in to change notification settings - Fork 13
image
Auto Ascend (20 points) should be easy.
Then we are left with 4 quests for the 100 chest. Maybe we could do the last 2 quests by: clicking on those tabs, swiping all the way down (the guild quest will exclude this step), and clicking the cheapest item. To keep track, we can add a variable into the temp file that keeps track of when we bought these items. It will use date +"%U", which outputs
week number of year, with Sunday as first day of week (00..53). A function will run date +"%U" and if the value is different, then we buy, and re-set variable.
If we do this, then the time in tempFile (that we use for Mythic Trick) will need to be changed into a variable, as well change the corresponding functions.
All reactions
Replies: 1 comment 10 replies
I'd like to have separate functions for these actions, namely autoAscendHeroes(), buyFromLabStore() and buyFromGuildStore(), that can be toggled to true or false in the config.sh, defaulting them to false.
I'm not sure yet how much I like this. I love the idea of involving weekly quests, though the more I think of this, the more it feels like it's going to bloat the script. I can imagine it'll be harder than expected to implement these ideas, especially the .tmp one. But it's definitely doable!
We'd also have to decide what to buy from the stores. Especially the Guild Store will be difficult, as everything always changes and each player may have their own priorities. The only option we have is to buy from the top row, and it will most likely be a random one (for example the first tile). I do not like this at all though.
Regarding the Lab Store, users also have priorities... We can choose to buy whatever, and people then decide if they want to enable it, but I still don't like this option. I'd rather have the player be able to choose which reward the script should buy, but then that is freaking difficult to code and I wonder if it's worth it...
Ugh, I don't know. I don't know what to think of this. 😅
All reactions
-
👍 1
I also think there's no need to change the current config.sh file, it should work out if the box when changing it to .ini.
Your repo is interesting! Has a lot of really nice small functions to help us out here, thanks!
I do wonder though... Isn't there a better/native way to read the .ini file, besides using read? It feels kind of a downgrade then, as .source is (I imagine) way quicker and efficient, not to mention it auto-assigns variables.
All reactions
Hm I've done some research and it doesn't look like you can... I'd rather keep the script.sh as it is then. It'll just bloat the script if we want to change it to .ini just because why not.
Maybe we should use a .sh file instead of a .tmp file since we're going to be storing variables there as well. Looks like the way to go there in my opinion. Suggestions are welcome!
All reactions
The fastest way to read a .ini file is to use this sed command, but it's not safe because it's using sed -r that does not exist everywhere:
# getFromIni <FILE> <SECTION> <PARAM> getFromIni(){ sed -nr "/^\[2ドル\]/ { :l /^3ドル[ ]*=/ { s/.*=[ ]*//; p; q;}; n; b l;}" "1ドル" }
If you use source the extension is not important, we just need to be careful to not use [section] but just # section. Once it's included just $param et voila 😄
All reactions
Yeah, I'd rather not have such a function.
All reactions
I did add it during my refacto, it's working at the moment.
All reactions
-
👍 1