r/Discord_selfbots

I want to automate votes on top.gg [ multiple accounts actually ] .

Uh I recently have created an farming script but that's inside of discord and beyond that I have no clue where to begin with , and would really like to automate votes and there's on more website - sofi.gg which i like to automate too it's like a vote but called bump refreshed every 4h and stuff . If anyone have the script or have the idea how can I build it it would be really appreciated.

And I had a query like i couldn't use data centre proxies/ips and gotta use residential ips that are mostly paid [ so would like to save bandwidth their too idk how tho] and if there's alternative do lmk.

reddit.com
u/Alive_Beginning_3668 — 3 days ago

code to auto claim tickets in discord

i need code that claim ticket fast when someone open it and ping my role
and i want it to work in any kind of tickets tools

reddit.com
u/dravendeku — 4 days ago

How can i make these types of selfbots?

This is a gc screenshot where a guy came and typed some codes and his 3 bots started spamming like 30-40 msgs every second. Yea ofc his bots were abusing.

u/YourSigmaGuy_234 — 6 days ago

hes messeging on two accounts at the same time Interesting

i asked them how there is two of you and both accounts responded at the exact time. Do most selfbots have this feature?

u/RedEnergy92 — 7 days ago

what ai is easy to manipulate and get it to make me selfbots and stuff

I used to use groq and asked it to make selfbots but it doesn't work anymore and I guess he just got smarter, so what ai could I use or any jailbreaking methods?

reddit.com
u/FentanylSPEAK — 9 days ago

Altkit Discord 4.2.0 - JS Wrapper (and updates since release)

Hey everyone,

@altkit/discord has changed significantly since its original 4.0.0 release.

The project started as a maintained fork of discord.js-selfbot-v13, with the goal of modernising the codebase while preserving user-account functionality. Since then, it has evolved into a much more extensively updated Discord.js-compatible wrapper rather than simply being a renamed fork. Here are the updates since the first release:

Discord.js 14.27 compatibility

The public API has been updated substantially toward the Discord.js 14.27 API surface, including:

  • Modern Events and Partials
  • Current builders and formatters
  • Updated structures, flags and TypeScript definitions
  • Modern attachment handling
  • Poll support
  • Voice-message metadata
  • Collectibles and newer role functionality
  • Stage-instance improvements

The library now targets Discord REST API v10 and Gateway v10 by default.

User-account-first architecture

The library has been cleaned up to focus specifically on user-account functionality instead of retaining bot-specific internals that don't apply to selfbots.

Supported user workflows include:

  • Sending and editing messages
  • Invoking installed application slash commands
  • Buttons, select menus and modals
  • Webhooks
  • Account settings
  • Custom and rich presence
  • Spotify presence
  • Voice, audio and video
  • CAPTCHA callbacks
  • Automatic TOTP/MFA handling
  • Guild discovery and invite handling

Bot-only functionality such as intents, bot command registration, bot interaction responses and bot sharding is explicitly disabled instead of existing in a partially functional state.

Discord API v10 support

A large amount of newer Discord API behaviour has been implemented since the initial release.

This includes:

  • Modern attachment upload and edit behaviour
  • Explicit spoiler attachment metadata
  • Voice-message attachments
  • Voice channel status and start-time information
  • Community invite roles
  • Invite target-user CSV support
  • New modal components including file uploads, radio groups and checkbox groups
  • ChannelFlags
  • Channel creation flags
  • File-type restrictions for upload components
  • Updated application flag handling using bigint
  • A complete Discord API v10 REST error-code table

Note: some Discord API v10 routes are bot-only and may not be available for user accounts.

REST and rate-limit handling

The REST implementation has received a fairly major overhaul.

Rate limits are now handled using Discord bucket hashes, HTTP methods and major resources rather than relying on simpler route-level handling.

Retry behaviour was also changed so ambiguous POST and PATCH requests are not automatically replayed when Discord may have already processed them.

The library also handles current Discord rate-limit scopes, retry timings, transport errors and 204 / 205 responses more accurately.

TLS and networking

The networking layer was also substantially improved.

REST, Gateway, voice and RemoteAuth now use TLS 1.2+ defaults, with separate configuration available for:

  • REST TLS
  • Gateway and voice TLS
  • Destination TLS through proxies
  • HTTPS proxy TLS

Security improvements

Version 4.2.0 includes a broad security review across the codebase.

Changes include:

  • Authentication tokens redacted from debug logs
  • TOTP secrets no longer exposed through serialization
  • Passwords and MFA codes sanitized from errors
  • The private _eval() method has been disabled because it allowed arbitrary code execution. However, eval can still be used directly in your Node.js project as it is not an included Altkit function
  • Safer handling of malformed UDP and voice packets
  • Safer RemoteAuth JSON parsing
  • Dependency updates resolving previously identified vulnerabilities

Stability improvements

A number of crash and cleanup issues were also fixed:

  • Malformed voice and UDP packets no longer crash the process
  • UDP socket cleanup was fixed
  • RemoteAuth WebSocket cleanup was fixed
  • Voice connection null dereferences were patched
  • Client.destroy() now handles cleanup failures more gracefully
  • Voice connections are properly cleaned up on client shutdown

Additional fixes include:

  • onSpeaking
  • acceptInvite()
  • deauthorize()
  • Poll voter fetching
  • Guild member flags
  • WebSocket ping reporting

Performance improvements

There were also several performance optimisations opportunities we found, and we took action.

REST hot paths now cache expensive timezone and header information instead of recomputing it for every request.

GuildMemberRoleManager was also changed from an O(n²) role lookup path to O(n). Previously, role lookups could repeatedly scan large guild role collections while resolving a member's roles. The updated implementation instead iterates the member's role IDs directly, allowing the amount of work to scale linearly rather than quadratically as guild size increases.

Documentation

The project now includes:

  • Full documentation
  • Migration documentation for older selfbot projects
  • Runnable examples
  • TypeScript declaration validation
  • API compatibility regression coverage
  • Discord API v10 regression coverage
  • Security and transport coverage
  • Active CI

Installation

npm install @altkit/discord

Basic example

const { Client, Events } = require('@altkit/discord');

const client = new Client();

client.once(Events.ClientReady, readyClient => {
  console.log(`${readyClient.user.tag} is ready`);
});

client.login(process.env.DISCORD_TOKEN);

The project is still actively developing, so bug reports, feature requests and contributions are welcome.

I'd especially appreciate feedback from anyone currently using discord.js-selfbot-v13 or migrating an existing selfbot project to Altkit.

As always, automating normal Discord user accounts violates Discord's Terms of Service and can result in account restrictions or termination. Use it entirely at your own risk, and never expose or commit your user token.

GitHub | Documentation | NPM

reddit.com
u/BackgroundSale3533 — 8 days ago

Question

Hi!

I am looking to make a bot that scans messages from certain channels in certain servers to feed AI to make a report / forward webhook to another server for more concise information?

is this possible with a self bot without any risk of the account getting banned?

Thanks!

reddit.com
u/Country6500 — 9 days ago

I need help with a selfbot.

I'm trying to create a self-bot that automatically replies when someone messages the account. However, after sending the message—even with a delay—the account gets banned. How can I get around this?
reddit.com
u/gbxzw7 — 10 days ago

Selfbot being flagged by discord (Unusual Activity)

So as shown in the video, whenever my selfbot sends a dm, the discord catches this activity and flags the account and forcing a password reset and mail verification before activating the account again. Is there any workaround for this? This may also happen during a server channel messaging.

THINGS TO NOTE:

- I have already implemented Captcha Solver

- I use proxy for different accounts

- There is some cooldown between each messages

- I use typing indicator aswell

u/Realtrickz — 14 days ago

Request based username changer

Is there any detections here ? As far as i know unflagged accounts get a capctha less username change Am I fine with just firing the request while making it look like it came from a browser or do I need to humanize the behavior more like using web sockets etc… So far I have a user id based monitorer so when the username changes from xxx to deleted_user_…. I just claim it on my own Am I fine if I just do it with the token of an unflagged account or will that captcha?

reddit.com
u/Fair_Dig4945 — 11 days ago

Recent changes, self bot question.

I had a simple selfbot that essentially sent a message in a channel once every 6 - 8 hours (with variance). based on discord.js but after starting up the project and launching it again for the first time in about a year I got an immediate account limitation, had to reset my password etc..

I usually use AI to help code but Codex is absolutely refusing to touch selfbots now so i'm kind of lost. Does anyone know a solution that works, or what I need to do to get things working again. After looking at discord.js it's discontinued.

reddit.com
u/Recent-Suspect-4375 — 12 days ago