What each import script actually does
Two different scripts, two different jobs — read exactly what each one does before you run either
Script 1 — “Get the link” (regular import)
This is the script behind “Copy command” in the regular URL import — the simple one, used since before Quick Import existed. All it does is find a link and copy it to your clipboard; the script itself never sends anything anywhere.
1. Permission for this window only
The command starts with Set-ExecutionPolicy Bypass -Scope Process. "-Scope Process" means the permission applies only to this one open PowerShell window — nothing changes permanently in Windows, and it's gone the moment you close the window.
2. Finding where the game is installed
The script reads Player.log — an ordinary log file the game writes on its own for debugging its own errors. Inside it finds the path to the game's install folder, which the game put there itself.
3. Reading a copy of the game's own cache
Inside the game folder is a webCaches directory — the browser cache the game uses to render pop-up windows like your pull history (that screen is drawn as an embedded web page, not part of the 3D game). The script copies one file from there to a temporary folder — a copy, not the original — and searches it for a link containing getGachaLog: the same address the game itself opens to show you your history.
4. One check, then it's done
Before handing you the link, the script makes a single test request to the game's own official server to confirm the link still works — the same kind of request the game itself would make. The temporary copy is deleted, and the link is copied to your clipboard.
Script 2 — “Quick Import” (full local fetch)
Why a separate method exists
A regular link import downloads your history from our server, not your own computer — and everyone who imports at the same time shares one request budget against the game's servers. The more people import at once, the longer everyone waits. Quick Import fixes this differently: the script downloads your history straight from your own machine, under your own internet's limit, not one shared by everyone.
The script finds the same temporary pull-history link the regular method does, but doesn't stop there. It pages through the whole history itself, collects the pulls, and sends them to the site using a short, single-use access key issued just for this import. It never needs your game or site password at any step.
What happens while you wait
1. Permission for this window only
The command starts with Set-ExecutionPolicy Bypass -Scope Process. "-Scope Process" means the permission applies only to this one open PowerShell window — nothing changes permanently in Windows, and it's gone the moment you close the window.
2. Finds and checks the history link
The same mechanism as the regular import method (see the FAQ “Is it safe?”) — the script reads the game's own log and cache, finds the temporary pull-history link, and confirms it still works. Nothing new here, just the first step before what comes next.
3. Pages through the history itself, banner by banner
Using that link, the script talks to the game's own official server again, many times in a row — about 20 records at a time, separately for each of the banners. Between requests there's a pause of roughly half a second, so it puts no more load on the game's servers than you scrolling through your own history to the end would.
4. Shows progress right in the console
While it fetches, the PowerShell window shows which banner is being collected and how many pulls so far. Nothing happens silently in the background — if something goes wrong, it shows up on screen immediately.
5. Sends what it collected to the site
Once a banner is fully collected, the script sends those records to gacha-tracker.com, together with the temporary pull-history link it found in step 2 — the same link the regular import uses. It proves it's really you not with a password, but with a short, single-use access key — the site issued it for this one import while you were logged in on the upload page, and the key stops working on its own once it's no longer needed.
What happens next — already on the site
The site receives from the script the list of pulls (which item, when, from which banner), your in-game UID and that temporary history link. The link is used for one thing: the site fetches a few pages per banner from the official server — the newest one and one or two from deeper in the history — and checks them against what the script sent, so nobody can upload an invented history to the leaderboard. It lives only in the server's memory for the hour the import is open and is never stored with your account. From there it's the same process as a regular link import: the site removes duplicates (anything already imported before doesn't get counted twice), recalculates pity, and saves everything to the account you're already logged into. The progress on the page updates on its own while the script is still running — there's nothing to click.
What it never does
Verify it yourself
.ps1) — open it in any text editor and read every line before running itStill have questions?
The import takes a couple of minutes — your full history is pulled in and stays yours for good
Import pull historyThe short version of this answer is in the FAQ. That's also where the rest of the import questions are