Pokémon Center drops: sticky sessions through the queue, start to finish
2026-10-05 · Bazyl

After this post you can run a Pokémon Center drop on sticky sessions, from the first purchase to the statistics page the morning after. The step most people get wrong is the session id: one id per task, never one id shared across a bot.
A queue remembers where you connected from. A task that changes IP halfway through is a new person to the queue, and two tasks on one id are one person. Everything below follows from that.
Buy pay as you go, and buy small
Pay as you go starts at 1 GB and never expires, so the first purchase can be a test. In US dollars, as of September 2026, 1 GB costs $4.20 a gigabyte, 5 to 14 GB $3.60 and 15 to 29 GB $3.00.
Buy a few gigabytes, run one drop, and let your own usage decide the next size. We don't publish how many gigabytes a Pokémon Center drop uses. It depends on the site and on the bot, and a number we can't stand behind is worse than none.
The full ladder, in your own currency, is on the pricing page.
Pick the gateway nearest the bot, not the store
Three gateways, one pool: eu-residential2.basilproxies.com,
us-residential2.basilproxies.com and ap-residential2.basilproxies.com. The gateway
only decides the latency between your machine and us. The exit country comes from the
username.
So a bot on a server in Frankfurt running the US store goes through eu with
-country-us. The same credentials on a machine in Singapore running the Japanese store
go through ap with -country-jp. Same account, same password, a different first hop.
Build one string per task on port 4243
Port 4243 is sticky: the same session id keeps the same IP. Three tokens do the work, in
a fixed order: -country-<store country>, then -session-<8 lowercase letters or digits>,
then -lifetime-<minutes>. The lifetime takes any value from 1 to 1440, and 1440 minutes,
a full 24 hours, is the ceiling.
Size the lifetime a little longer than the queue you expect, not as long as it goes. A
queue that tends to clear in an hour and a half gets -lifetime-120. A session that
outlives the queue by a day is just your whole task's traffic parked on one address.
These are the three strings from the Pokémon Center page: the queue, a second region and the restock monitor. One pair of credentials. Only the username changes.
# Pokémon Center US: one IP for two hours (port 4243)
us-residential2.basilproxies.com:4243:USER-country-us-session-k4mz61pq-lifetime-120:PASS
# A Japanese exit through the Asia gateway, same credentials
ap-residential2.basilproxies.com:4243:USER-country-jp-session-x9d02mvq-lifetime-120:PASS
# Restock monitor: a new IP on every request (port 4242)
us-residential2.basilproxies.com:4242:USER-country-us:PASS
Generate them in the dashboard, which writes up to 100,000 lines per generation, each
with its own session id, in the format your bot expects. Or DM the Basil bot /proxies
on Discord: it answers with your own lines, a code block up to 25 and a .txt file beyond
that, with country targeting. City tokens come from the dashboard's city picker.
Fifty tasks means fifty strings with fifty different session ids. Not one string pasted fifty times.
Test early, because a new pair can answer 407 for about a minute
Brand-new credentials can answer 407 Proxy Authentication Required for about a minute
while the gateway picks them up. A 407 in that window is not a bad password. Wait, retry,
and only then re-copy the pair from the dashboard.
So the first test happens when you generate, not when the queue opens. A string that worked an hour before the drop is a string you don't think about on release day. If a 407 outlives the minute, check where the tokens are. They belong on the username, never on the password.
Check the exit twice
One request through port 4243 tells you the string authenticates. Two tell you it's sticky. The IP has to come back identical, and the country has to be the store's.
# The same string your task will use. Sticky means the same IP twice.
PROXY="http://USER-country-us-session-k4mz61pq-lifetime-120:[email protected]:4243"
curl -s -x "$PROXY" https://api.ipify.org; echo
curl -s -x "$PROXY" https://api.ipify.org; echo
# The country of that exit. A US store wants US.
curl -s -x "$PROXY" https://ipinfo.io/country
Both ports speak plain HTTP proxy and an https:// target tunnels through, so this runs
as written once you put in your own user, password and session id. There is no SOCKS5 on
this pool, so don't configure the task for it.
When the IP changes mid-queue, start that task again
A residential IP is a home connection, and home connections go away. When a session's IP changes before its lifetime is up, the queue sees a new person, and carrying on with the same id doesn't bring the old one back.
Start that task again on a new session id. Changing eight characters is a fresh identity at once. Make sure the bot builds the string once per task and keeps it, because a bot that regenerates the id on every request is doing this to itself, all day.
Afterwards: read the statistics page, then post the win
The dashboard's statistics page shows bandwidth and request charts from 24 hours to 30 days, a success rate and latency, and a per-domain table of your top targets. That table is where your real gigabytes-per-drop number lives. Read it the morning after and size the next purchase from it, not from a group chat.
Then post a photo of the win in #success on our Discord. A picture of a win enters a gigabyte draw
with prizes of 0, 1, 2, 5, 10 or 25 GB. Entries need a linked account, a paid purchase in
the last 30 days and a Discord account at least a year old; one entry a day, three a
week. Post weekly and the streaks pay on top: 10 GB at four weeks, 30 GB at eight, and a
permanent 10% code plus the Veteran role at twelve.
What we don't publish, and what we answer for
We don't publish gigabytes per drop, and we don't promise an outcome on Pokémon Center or on any other site. We answer for the proxy being live and reachable from the country you asked for. What a site does with a request is the site's.
What we do publish is everything above: the ports, the tokens, the ceiling, the warm-up minute and the draw rules, all current as of October 2026.
If the next drop is tomorrow, start from the strings on the Pokémon Center page and change the country token to your store's.
Common questions
- Which port do I use for a Pokémon Center queue?
- Port 4243. It holds one IP for the lifetime written into the string, up to 1,440 minutes. Port 4242 hands out a new IP on every request, which is right for a restock monitor and wrong for a queue.
- How long should the sticky lifetime be?
- A little longer than the queue you expect. For a queue that tends to clear in an hour and a half, -lifetime-120 gives two hours. Any value from 1 to 1440 minutes works, and 1440 is the ceiling.
- My new string answers 407. Is the password wrong?
- Usually not. Brand-new credentials can answer 407 for about a minute while the gateway picks them up. Wait, retry, and only then re-copy the pair from the dashboard. Targeting tokens go on the username, never the password.
- How much data does a Pokémon Center drop use?
- It depends on the site and the bot, so we don't publish a number. Pay as you go starts at 1 GB and never expires. Run one drop, read the statistics page for the bytes per domain, and size the next purchase from that.
- Where do I get the strings?
- The residential page of the dashboard generates up to 100,000 lines at a time, in the format your bot takes. Or DM the Basil bot /proxies on Discord. It answers with a code block up to 25 lines and a .txt file beyond that.