Deriver's spawn-pacing self-bot

Note: this runs on a real Discord user account (selfbot), which is against Discord's ToS. by using it you accpet the risk of getting your account either limited, disabled or even banned

Originally a Pokecord-targeting self-bot (see git history / old index_pokemon.js, add_shiny.js, pokemon.csv, shiny_pokemon.csv — all unused leftovers from that abandoned approach). Now repurposed entirely for any pokemon bot. Here's what it does:

1. Spawn-pacing spam — sends a random filler word into the target channel to avoid triggering discord's AI for spam every 4-7s (randomized) to bump Deriver's message-count-based spawn trigger, so wild Pokémon actually appear.

Bot is off by default and can controlled remotely via chat commands (DM or server message) — no need to touch the account directly or SSH in to it to toggle anything.

Credit

The original project skeleton this was built on top of is caow2/pokecord-selfbot — credit to them for the base self-bot structure.

The actual Discord client library this currently runs on is youtsuhodev/discord.js-selfbot-youtsuho-v13 — credit to them for maintaining a working self-bot fork of discord.js against Discord's current API (the original discord.js v11 this repo used is dead — Discord retired the API version it depends on back in 2023).

Setup

1. Discord account token

This needs a real user account token (not a bot token) for whichever account will run it.

To get it:

1. Log into discord.com/app in a browser with that account.
2. Open DevTools (F12) → Network tab → check Preserve log → reload the page (F5).
3. Filter for api, click a request like /api/v9/users/@me (200 status, has real size — not @me?lurker=true).
4. Under Headers → Request Headers, copy the authorization value.

Paste it into TOKEN near the top of index.js.

If the account gets rate-limited/flagged for spam, the token stays valid, but sending will fail with a 403/code: 340013 error until the restriction lifts — that's Discord-side, nothing to fix in the code.

2. Target channel

CHANNEL_ID in index.js must be the exact channel ID Deriver is configured to watch for spawns in your server. Get it via Discord's own "Copy Channel ID" (enable Developer Mode in Discord settings first).

The account running this script must actually be a member of that server/channel — if it isn't, messages/spawns silently never reach it (no error, just nothing happens).

3. Install & run

npm install
pm2 start index.js --name spammer

(subsequent restarts: pm2 restart spammer — no ecosystem file needed)

Usage

Send these from any DM or server message the account can see (any sender works, not just the account's own owner):

Command	Effect
!start	Starts the spawn-pacing spam (random word every 4-7s)
!stop	Stops it

All four are off by default on launch — nothing runs until you explicitly send the "on" commands. Command text !start and the spam pacing range (SPAM_MIN_MS/SPAM_MAX_MS) are all plain constants near the top of index.js if you want to change them.