Announcement 📢

[Fabbi]

This project is not dead (anymore) and I am in the process of rewriting/updating the code to support all sorts of SHIFT-code-sources.
It will take a few days to get this done (work, private stuff and obviously Borderlands 4 occupy a lot of time) but I think that I can push a new version next week.

I am sorry for the silence before.

[XxUnkn0wnxX]

can you add support for parsing a local generated shiftcodes.json from say https://github.com/zarmstrong/autoshift-scraper project?

[zarmstrong]

hey i made a boatload of changes. take a look at my branches (spun from ugoogalizers)

https://github.com/zarmstrong/autoshift-scraper/tree/master
https://github.com/zarmstrong/autoshift/tree/master

[XxUnkn0wnxX]

hey i made a boatload of changes. take a look at my branches (spun from ugoogalizers)

https://github.com/zarmstrong/autoshift-scraper/tree/master https://github.com/zarmstrong/autoshift/tree/master

In query.py, the source for shiftcodes.json is hard-coded to your Gist. Could we make this configurable and also support a local file?

Proposed (backwards-compatible):

• Add a --codes-source CLI flag and/or an AUTOSHIFT_CODES_SOURCE env var.

• Accept either an http(s):// URL or a filesystem path (e.g., ./data/shiftcodes.json).

• Optionally auto-detect shiftcodes.json in the project root when no flag/env is set, then fall back to the current default URL.

Why: I prefer to keep the scraper output as a local file on my system, and this also lets others point to their own hosted JSON without editing a hard-coded URL.

[zarmstrong]

hey i made a boatload of changes. take a look at my branches (spun from ugoogalizers)
https://github.com/zarmstrong/autoshift-scraper/tree/master https://github.com/zarmstrong/autoshift/tree/master

In query.py, the source for shiftcodes.json is hard-coded to your Gist. Could we make this configurable and also support a local file?

Proposed (backwards-compatible):

* Add a `--codes-source` CLI flag and/or an `AUTOSHIFT_CODES_SOURCE` env var.

* Accept either an `http(s)://` URL or a filesystem path (e.g., `./data/shiftcodes.json`).

* Optionally auto-detect `shiftcodes.json` in the project root when no flag/env is set, then fall back to the current default URL.

Why: I prefer to keep the scraper output as a local file on my system, and this also lets others point to their own hosted JSON without editing a hard-coded URL.

easy enough. added

[zarmstrong]

Why: I prefer to keep the scraper output as a local file on my system, and this also lets others point to their own hosted JSON without editing a hard-coded URL.

easy enough. added

also added scraping of ign and polygon as backups for bl4

[XxUnkn0wnxX]

@zarmstrong Any chance you could add support for multiple profiles in your autoshift fork, e.g. --profile USER-1 (and/or an AUTOSHIFT_PROFILE env var)?

Proposed UX (backwards-compatible):

• --profile <name> with a default (e.g., default) if omitted.

• Per-profile state stored under data/<profile>/, such as:

  • data/<profile>/keys.db

  • data/<profile>/.cookies.save

Optional: a --data-dir flag to override the base directory (default data/).

Why: This makes it easy to juggle multiple accounts without deleting keys.db each time I switch users, and means I don’t have to re-specify credentials (e.g., --user <name> --pass <password>) on every swap.

Meta request: Would you mind enabling GitHub Issues (and optionally Discussions) on your fork? That way we can file feature requests and bug reports directly against your version.

[zarmstrong]

@zarmstrong Any chance you could add support for multiple profiles in your autoshift fork, e.g. --profile USER-1 (and/or an AUTOSHIFT_PROFILE env var)?

Proposed UX (backwards-compatible):

* `--profile <name>` with a default (e.g., `default`) if omitted.

* Per-profile state stored under `data/<profile>/`, such as:
  
  * `data/<profile>/keys.db`
  * `data/<profile>/.cookies.save`

Optional: a --data-dir flag to override the base directory (default data/).

Why: This makes it easy to juggle multiple accounts without deleting keys.db each time I switch users, and means I don’t have to re-specify credentials (e.g., --user <name> --pass <password>) on every swap.

Meta request: Would you mind enabling GitHub Issues (and optionally Discussions) on your fork? That way we can file feature requests and bug reports directly against your version.

added profiles

[XxUnkn0wnxX]

@zarmstrong check the PR when you get the chance: zarmstrong#5
things where a little broken to say the least..

and @Fabbi I think @zarmstrong ver is bl4 ready, or if your still doing a full re-write maybe consider adding the same features discussed here?

[Fabbi]

Why the complexity with profiles? Wouldn't starting a second instance make more sense?

[Fabbi]

@zarmstrong check the PR when you get the chance: zarmstrong#5
things where a little broken to say the least..

and @Fabbi I think @zarmstrong ver is bl4 ready, or if your still doing a full re-write maybe consider adding the same features discussed here?

I want to rewrite either way for more stability, new features and fun 😁
I will add what I can from the forks.

[ugoogalizer]

Why the complexity with profiles? Wouldn't starting a second instance make more sense?

I agree with this, I run three copies in parallel without issue. It's simple and still lightweight. Not sure profiles add value

[flammable]

For what it's worth, I run 4 different copies (each as a separate Docker container) and have them running at different intervals to avoid issues with SHiFT's website. I run this for myself and 3 family members.

I'm glad to see this project is still alive. Thank you to all three of you for continuing development! Would it make sense to move this to a GitHub organization to reduce the number of forks?

[XxUnkn0wnxX]

Why the complexity with profiles? Wouldn't starting a second instance make more sense?

I agree with this, I run three copies in parallel without issue. It's simple and still lightweight. Not sure profiles add value

its not to have multiple instances on the same project

its easier to switch profiles then whole new instances for different accounts.
you can just setup your own cronjob or in my case via macOS launchd agent to just set a different profile for when redeeming keys for each user.

while docker is handy, my system is a little to old to run the current releases of it & I wanted more flexibility such as using a external schedular & having multiple folders of the same repository for each user just doesnt make sense to me.

[Fabbi]

its not to have multiple instances on the same project

its easier to switch profiles then whole new instances for different accounts.
you can just setup your own cronjob or in my case via macOS launchd agent to just set a different profile for when redeeming keys for each user.

while docker is handy, my system is a little to old to run the current releases of it & I wanted more flexibility such as using a external schedular & having multiple folders of the same repository for each user just doesnt make sense to me.

I see.
My rewrite has a config for the data-folder location and makes it easier to use the tool as part of any setup or as library for other projects. That should fit your needs.

Thanks for all your work and the great ideas.

I am toying with a few ideas, but want to first provide the base functionality again