Browse
Category
DiscussionsAdd-ons / Tools

[Tool] Humble Bundle expiration exporter

Open
Ignition365

I decided to build a user script a few days ago that scans your keys & entitlements pages that builds a CSV dataset that I could paste into Excel so I can sort and see expiration dates of keys. I've recently added persistent storage and a changelog, that way when Humble inevitably updates expiration dates, you can catch those changes across scans. All times UTC.

V3.0

  • Added Expiration summary (titles expiring in next 60 days, with a toggle to show already expired titles)

V3.1

  • Fixed issue with some keys not displaying expected expiration messaging. (These expirations could be off by an hour, but so far only apply to some February/January 2025 Choice keys)

Planned changes:

  • Relabel buttons
  • Maybe account for DST in backup calculations
  • add changelog display instead of copy to clipboard.

Humble Bundle Expiration CSV Exporter

5 months ago*

Comment has been collapsed.

24 Comments
fernandopa

I thought of doing something like that yesterday, then got busy and gave up and decided to gamble with my keys. So thank you for reading my mind and doing the work for me hahaaha :)

5 months ago
Permalink

Comment has been collapsed.
Raggart

I don't have the time to look at the code right now, so I'll ask instead: does this reveal the keys or simply compile a list of already revealed keys?

5 months ago
Permalink

Comment has been collapsed.
Ignition365

Compiles a list regardless of if keys are revealed or not. Does not extract or reveal keys. From what I hear unrevealed choice keys dont show up on keys & entitlements, so won't catch those maybe.

5 months ago
Permalink

Comment has been collapsed.
Channel28

Lext's script sounds more like what you are after:
Bundle Site Key Exporting

5 months ago
Permalink

Comment has been collapsed.
Raggart

Thanks, I was not aware of this. I'll give this a try.

5 months ago*
Permalink

Comment has been collapsed.
thekenya

Nice

5 months ago
Permalink

Comment has been collapsed.
AxJ

This is awesome!!!! Save all of us a lot of time!!! I had already exported my own list, and it's very simple, useful, and clear!
Is it possible to add a button to show the next N keys that are about to expire or the keys that are about to expire in the next 3 months on HB's keys page?
Thanks for your effort anyway!!! Appreciate it!!!! 👍👊😀🤘

5 months ago
Permalink

Comment has been collapsed.
Ignition365

If you put the data into spreadsheet software, you can sort it. I can change the default sort to soonest instead of scan order

5 months ago
Permalink

Comment has been collapsed.
AxJ

That's fine, you don't have to change the default sort order because we can do it on the spreadsheet ourselves.
One click on the HB's keys page to show the upcoming expired keys is just my lazy checking idea.

5 months ago
Permalink

Comment has been collapsed.
Ignition365

Ah, I get you, I can add a button to display a window with upcoming expirations, maybe say 60 days.

5 months ago
Permalink

Comment has been collapsed.
Ignition365

I added an expiration summary button.

5 months ago
Permalink

Comment has been collapsed.
AxJ

Nice!! Works like a charm!!!

BTW, I didn't check all keys, but one of the keys doesn't show an expired date for me. (Dordogne, January 2025 Humble Choice)
Very strange. 🤔

5 months ago
Permalink

Comment has been collapsed.
Ignition365

I see the issue, I'll see about fixing it.

5 months ago
Permalink

Comment has been collapsed.
Ignition365

Sort of fixed in 3.1

5 months ago
Permalink

Comment has been collapsed.
AxJ

It works, nice!!!

5 months ago
Permalink

Comment has been collapsed.
AmanoTC

Version 2.1 seems to be broken for me. Older versions yesterday (1.x) still worked.
When I click on "Export Dataset CSV", i can see in the Chrome console under "Network" that it checks all keys, but it doesn't create a bubble that the operation is finished nor does it write any information to the clipboard.

5 months ago
Permalink

Comment has been collapsed.
Ignition365

Any other console errors during run?

5 months ago
Permalink

Comment has been collapsed.
AmanoTC

Nope, nothing

To provide a little more context:

  • 190 pages at "Keys & Entitlements"
  • I clicked on "Changelog" first, no changes. Because I wanted your time signatures within the data set, I cleared the stored data, then clicked on "Export Dataset CSV" with the aforementioned result.

Maybe I did something unexpected? Maybe the script recognizes that it's not the first run? (I think I have seen in your code that the Dataset only gets pasted to the clipboard at the first run. I could be very wrong, though).

5 months ago*
Permalink

Comment has been collapsed.
Ignition365

Does the console have a message about going back to page 1?

I'll take a look when I get back to a computer. It is possible I broke something when I put in the first run logic.

5 months ago
Permalink

Comment has been collapsed.
AmanoTC

Something... weird... happened :D

I was on page 1, but it looked like the console was stuck on "Navigating to page 1…". I then manually changed the page on the "Key & Entitlement"-page in Chrome to page 3, which somehow seems to have triggered your script, because under console there was "Starting full scan…" and a few seconds later the bubble showed up "First scan complete. Dataset saved and copied to clipboard.".

Which it did.
Dataset was indeed posted to clipboard and I could paste it to Excel

5 months ago
Permalink

Comment has been collapsed.
Ignition365

Ah, Ill have to double check that, it should work from page 1, but I'll double check regardless.

5 months ago
Permalink

Comment has been collapsed.
Ignition365

Yeah, I broke it running on page 1 when I added the logic to go back to page 1. Fixed in 2.2

5 months ago
Permalink

Comment has been collapsed.
AmanoTC

Thank you! :)

5 months ago
Permalink

Comment has been collapsed.

Deleted

This comment was deleted 2 weeks ago.

3 weeks ago*
Permalink

Comment has been collapsed.

Sign in through Steam to add a comment.