famecvv
Royal
Royal
hi all i want to buy a config maker that makes for svb and OPK SPK and so on, please message me if its possible i will pay asap im tired of config makers
Step-by-Step Process for Making a Config1. Capture the Target TrafficBefore touching OpenBullet 2 or SilverBullet, you need to understand how the target website handles authentication:
- Open your browser (e.g., Google Chrome) and open Developer Tools (
Code:
).
- Go to the Network tab and make sure Preserve log is enabled.
- Perform a manual login on the target website using a test account.
- Look for the authentication request (usually a
Code:
request named
Code:
,
Code:
,
Code:
, or similar).
- Note down the Request URL, Request Headers (such as User-Agent, Content-Type, Referer), and the Request Body / Form Data (where the username and password fields are sent).
2. Create a New Config in the Stacker
- Launch OpenBullet 2 or SilverBullet and navigate to the Configs section.
- Click New, give your config a name, author name, and optional category.
- Open the Stacker, which is where you build the workflow block by block from top to bottom.
3. Set Up the HTTP Request Block
- Add an HTTP Request block to your stack.
- Set the request Method to
Code:
or
Code:
depending on what the website uses.
- Paste the Request URL you captured earlier.
- Input the necessary custom headers.
- In the POST Data (or body) section, paste the parameters from the website's login payload, replacing the test credentials with OpenBullet variables like
Code:
and
Code:
: Plaintext
Code:
4. Configure Key Checks (Success & Failure)To let the program know whether an account is valid or invalid, you must analyze the server's response:
- Add a KeyCheck block right after your request block.
- Set up conditions using strings found in the response:
- Failure Keys: Strings that appear when login fails (e.g.,
Code:
,
Code:
).
- Success Keys: Strings or tokens that appear only upon successful login (e.g.,
Code:
,
Code:
).
- Ban / Custom Keys: Triggers for when proxies are blocked or account status requires a custom label (e.g.,
Code:
,
Code:
).
5. Parse and Capture DataIf you want to extract extra information from a successful login (like a wallet balance or subscription tier):
- Add a Parse block.
- Choose your parsing method based on the response format:
- LR (Left to Right): Extracts text situated between two static strings.
- JSON: Uses a JSON selector to target a specific data node.
- Regex: Uses regular expressions for complex patterns.
- Enable the Capture option and give the variable a name so it displays in your final hit outputs.
Step-by-Step Process for Making a Config1. Capture the Target TrafficBefore touching OpenBullet 2 or SilverBullet, you need to understand how the target website handles authentication:
- Open your browser (e.g., Google Chrome) and open Developer Tools (
Code:
Code:
F12
).
- Go to the Network tab and make sure Preserve log is enabled.
- Perform a manual login on the target website using a test account.
- Look for the authentication request (usually a
Code:
Code:
POST
request named
Code:
Code:
login
,
Code:
Code:
auth
,
Code:
Code:
signin
, or similar).
- Note down the Request URL, Request Headers (such as User-Agent, Content-Type, Referer), and the Request Body / Form Data (where the username and password fields are sent).
2. Create a New Config in the Stacker
- Launch OpenBullet 2 or SilverBullet and navigate to the Configs section.
- Click New, give your config a name, author name, and optional category.
- Open the Stacker, which is where you build the workflow block by block from top to bottom.
3. Set Up the HTTP Request Block
- Add an HTTP Request block to your stack.
- Set the request Method to
Code:
Code:
POST
or
Code:
Code:
GET
depending on what the website uses.
- Paste the Request URL you captured earlier.
- Input the necessary custom headers.
- In the POST Data (or body) section, paste the parameters from the website's login payload, replacing the test credentials with OpenBullet variables like
Code:
Code:
<USER>
and
Code:
Code:
<PASS>
: Plaintext
Code:
Code:
username=<USER>&password=<PASS>&remember_me=true
4. Configure Key Checks (Success & Failure)To let the program know whether an account is valid or invalid, you must analyze the server's response:
- Add a KeyCheck block right after your request block.
- Set up conditions using strings found in the response:
- Failure Keys: Strings that appear when login fails (e.g.,
Code:
Code:
"Invalid password"
,
Code:
Code:
"Account not found"
).
- Success Keys: Strings or tokens that appear only upon successful login (e.g.,
Code:
Code:
"access_token"
,
Code:
Code:
"Welcome back"
).
- Ban / Custom Keys: Triggers for when proxies are blocked or account status requires a custom label (e.g.,
Code:
Code:
"Cloudflare"
,
Code:
Code:
"CAPTCHA"
).
5. Parse and Capture DataIf you want to extract extra information from a successful login (like a wallet balance or subscription tier):
- Add a Parse block.
- Choose your parsing method based on the response format:
- LR (Left to Right): Extracts text situated between two static strings.
- JSON: Uses a JSON selector to target a specific data node.
- Regex: Uses regular expressions for complex patterns.
- Enable the Capture option and give the variable a name so it displays in your final hit outputs.

