Ever since I joined I joined the Dallas War-Room I made it a part of my goal to be annoying and "helpfully" remind people of doing their Point Tasks. At the same time I found it quite annoying to find out who on the team has and hasn't done them yet quickly without clicking through a lot of peoples profiles and threads.
A lot of people may not care about earning, a lot of people may care, I don't know, but I still made this thing to help you check your team or a specific user or a specific set of users, whatever.
As a disclaimer: This script right now has horrible UX, it's just the start and you need to put stuff into a commandline and install node and change a piece of code, so if you're not into that, don't look further. If you are into that and don't care who's earning, it's ok too, I just made it for myself and thought I'd share. Also it's just the start of something bigger I want to do with it, so over time the UX will get better and more features will be added. But for now: Enough talking, how does it work?
As a disclaimer, this sounds like a ton of things to do, but it's always like that when it's written out, so I put the whole install/setup into a YouTube Video and it's like 2 Minutes long, you can view it here, just remember to install node first. (Also if you're in Denmark, you are out of luck, because the video is blocked there because I forgot to turn off music)
It's pretty easy: First of all you have to install node on your machine. You can download it from here. The latest LTS version should suffice. It's really easy. In the end it's just a windows installer that you run and it installs spyware itself and dependencies.
Then you need a code editor. Notepad is enough. If you want to go fancy you can use Notepad++ if you wanna go mega fancy, you can use Visual Studio Code, but it does not matter at all. You can use VIM for all that it matters and you can still do this. Just need something that can open a Javascript text file and edit two variables.
After you installed Node.JS and the Editor of your choice you go to the Github Page of the project here: ISFL Whipper on GitHub, you can then either clone the project if you know what you are doing or if you aren't click on the green code button and download it as a ZIP File.
When you have it downloaded, unzip it on your system and open up the command line of your choice (PowerShell in my case, but the normal Windows Command Line does the trick as well, press your Windows key and type "cmd" and open up the command line). Navigate to the unzipped folder and type in "npm i". It will do a bunch of things and then show you this (ignore the repository field warning):
After that all that is left is opening up the index.js in the aforementioned code editor and changing it to the thread you want checked. So for example if we take a look at Week 15 Predictions, we copy the part behind ?tid= (the bunch of numbers) and put it in the right spot in the index.js:
All that is left now is change the array of people to check. You have to put all the names you want to check inside the team array (the thing between the [ ] after team =). Each username needs to be put in between "" and separated with a comma. So if your team to check consists of the usernames BradLeone Claire and Jean Luc, your team array should look like this:
If your team is gdfsjhghsjd, hallodri, Frolf and Asked Madden, your team array should look like this:
You only have to do this once, and then just updated it whenever the people you check for change. There doesn't have to be any order to the names, it's just important that they are their forum usernames.
All that is left for you to do then is save the file, go back to your command line inside that folder and type in: node index.js. The script will then run and spit out all the names that have not partaken in this specific point task (It takes a bit because it scrapes through all the pages first, you will see a bit of command line action first):
If it ever just stop at a point because the website decides to not give it any reply, just hit Ctrl+C and do it again. Sometimes it be like that.
So yes, this is it. It is still rough around the edges and I want to do a lot more things with it to make the whole User Experience a bit better, but it's a start and it may be helpful for some people. I hope you, dear reader, are one of the people who find it helpful.
A lot of people may not care about earning, a lot of people may care, I don't know, but I still made this thing to help you check your team or a specific user or a specific set of users, whatever.
As a disclaimer: This script right now has horrible UX, it's just the start and you need to put stuff into a commandline and install node and change a piece of code, so if you're not into that, don't look further. If you are into that and don't care who's earning, it's ok too, I just made it for myself and thought I'd share. Also it's just the start of something bigger I want to do with it, so over time the UX will get better and more features will be added. But for now: Enough talking, how does it work?
As a disclaimer, this sounds like a ton of things to do, but it's always like that when it's written out, so I put the whole install/setup into a YouTube Video and it's like 2 Minutes long, you can view it here, just remember to install node first. (Also if you're in Denmark, you are out of luck, because the video is blocked there because I forgot to turn off music)
It's pretty easy: First of all you have to install node on your machine. You can download it from here. The latest LTS version should suffice. It's really easy. In the end it's just a windows installer that you run and it installs spyware itself and dependencies.
Then you need a code editor. Notepad is enough. If you want to go fancy you can use Notepad++ if you wanna go mega fancy, you can use Visual Studio Code, but it does not matter at all. You can use VIM for all that it matters and you can still do this. Just need something that can open a Javascript text file and edit two variables.
After you installed Node.JS and the Editor of your choice you go to the Github Page of the project here: ISFL Whipper on GitHub, you can then either clone the project if you know what you are doing or if you aren't click on the green code button and download it as a ZIP File.
When you have it downloaded, unzip it on your system and open up the command line of your choice (PowerShell in my case, but the normal Windows Command Line does the trick as well, press your Windows key and type "cmd" and open up the command line). Navigate to the unzipped folder and type in "npm i". It will do a bunch of things and then show you this (ignore the repository field warning):
After that all that is left is opening up the index.js in the aforementioned code editor and changing it to the thread you want checked. So for example if we take a look at Week 15 Predictions, we copy the part behind ?tid= (the bunch of numbers) and put it in the right spot in the index.js:
All that is left now is change the array of people to check. You have to put all the names you want to check inside the team array (the thing between the [ ] after team =). Each username needs to be put in between "" and separated with a comma. So if your team to check consists of the usernames BradLeone Claire and Jean Luc, your team array should look like this:
Code:
const team = ["BradLeone", "Claire", "Jean Luc"];
If your team is gdfsjhghsjd, hallodri, Frolf and Asked Madden, your team array should look like this:
Code:
const team = ["gdfsjhghsjd", "hallodri", "Frolf", "Asked Madden"];
You only have to do this once, and then just updated it whenever the people you check for change. There doesn't have to be any order to the names, it's just important that they are their forum usernames.
All that is left for you to do then is save the file, go back to your command line inside that folder and type in: node index.js. The script will then run and spit out all the names that have not partaken in this specific point task (It takes a bit because it scrapes through all the pages first, you will see a bit of command line action first):
If it ever just stop at a point because the website decides to not give it any reply, just hit Ctrl+C and do it again. Sometimes it be like that.
So yes, this is it. It is still rough around the edges and I want to do a lot more things with it to make the whole User Experience a bit better, but it's a start and it may be helpful for some people. I hope you, dear reader, are one of the people who find it helpful.