You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/faq.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ sidebar_position: 100
11
11
No, OpenBullet 2 can read `.loli` configs, except for a few specific blocks or settings. You can simply import a `.loli` config inside OpenBullet 2 and it will automatically repackage it into the `.opk` format. You can also drop the config in the `UserData/Configs` folder and perform a rescan to achieve the same thing.
12
12
13
13
The following features are **not supported**:
14
+
- editing the config through *Stacker*, only raw *LoliScript* code
Copy file name to clipboardExpand all lines: docs/jobs/multi-run-job/running.md
+15-32Lines changed: 15 additions & 32 deletions
Original file line number
Diff line number
Diff line change
@@ -6,40 +6,36 @@ sidebar_position: 2
6
6
# Running a Multi Run Job
7
7
8
8
### Setup
9
-
For this guide, you will need to create a Multi Run Job with the given options (you can read the [creation guide](./creation.md) to know more about all the available options):
9
+
For this guide, you will need to create a Multi Run Job by going to the *Jobs* tab, clicking on *New* and selecting *Multi Run Job*. You can read the [creation guide](./creation.md) to know more about all the available options. We will use the following options:
10
10
- config: [sample config](/download/Test.opk)
11
11
- 5 bots
12
12
- data pool: range from 0 to 100 with step 1, Default wordlist type
13
13
14
-
At this point, you will see something like this
14
+
Leave everything else default. Your options need to look like these:
Now run the job again, you will see something like this
32
-
33
-
34
-
35
31
:::info INFO
36
32
If you want to run the job again, you will need to rewind the *skip* value to the beginning, so click on the *Change* button and set the *skip* back to 0 before attempting to start the job again.
|**Captcha Credit**|The remaining captcha credit (if the config uses a captcha service)|
66
62
|**Elapsed**|The time elapsed since the beginning of the run|
67
63
|**Remaining**|The estimated remaining time based on the number of data lines to process and the CPM|
68
64
|**Progress**|The overall progress of the check (includes the *skip*)|
69
65
70
66
### Controls
71
-
72
-
73
-
74
67
During the run, you are able to
75
68
-**Pause** the job and resume it later. When you click pause, the job waits until all bots finished processing their assigned items before going into a paused state
76
69
-**Stop** the job. When you click stop, the job waits until all bots finished processing their assigned items before going into an idle state
77
70
-**Abort** the job. When you click abort, the job will abruptly terminate all bots and you might lose the outcome of the ongoing checks
78
71
79
72
:::info INFO
80
-
In the job options, you can enable the *mark as to check on abort* option to make the current items go to *To check* when you click abort, so that you can check them manually or include them in the next run if needed.
73
+
In the job options, you can enable the *mark as to check on abort* option to make the current items go to *To Check* when you click abort, so that you can check them manually or include them in the next run if needed.
81
74
:::
82
75
83
76
:::caution WARNING
84
77
If a bot is stuck in a *ban loop* (for example because it keeps ending with an `ERROR` status), pausing or stopping the job will take forever. In this case you can either abort the job, or go to the config's settings page and set the *ban loop evasion* to a value higher than 0, so that eventually, after the specified amount of bans, the data will go to *To check* and the job will be able to be paused.
85
78
:::
86
79
87
80
### Hits
88
-
By default, a job will save hits, custom and to check results to memory, in addition to sending them to the *hit outputs* you configured. You can see the hits right below a job in the job viewer page.
81
+
By default, a job will save hits, custom and to check results to memory, in addition to sending them to the *hit outputs* you configured. You can see the hits the job obtained in the bottom-right area of the page.
89
82
90
83
91
84
92
85
You can select more than one hit by using the CTRL or SHIFT keys on your keyboard to add individual items or entire ranges to the selection, respectively. You can then copy the data from the hits and paste it where you want.
93
86
94
-
:::caution WARNING
95
-
If you are using the web client without HTTPS, your browser will show you this error
To solve this problem you can either enable unsecure sources in the browser or use something like [ngrok or cloudflared](https://discourse.openbullet.dev/t/your-openbullet-online/925)
100
-
:::
101
-
102
-
You are also able to *send* the hit (along with the proxy and wordlist type) to the *debugger*, and *show the full log* of the hit. The full log is only saved if you enable this option in the *RL Settings* section.
You are also able to *send* the hit (along with the proxy and wordlist type) to the *debugger*, and *show the full log* of the hit. The full log is only saved if you enable this option in the *RL Settings* section. Also, bot logs are only available to the admin user.
105
88
106
89
:::caution WARNING
107
-
Bot logs can be huge and eat up a lot of your RAM, so only enable them while debugging a config (for example to check why something ended up as *To check* instead of another result). Do not leave it enabled while checking a high amount of data lines, otherwise you will run into problems.
90
+
Bot logs can be huge and eat up a lot of your RAM, so only enable them while debugging a config (for example to check why something ended up as *To check* instead of another result). Do not leave it enabled while checking a high amount of data lines, otherwise you will run into memory issues.
0 commit comments