@@ -98,7 +98,7 @@ In this section, you will understand below how-tos:
98981 . ** Download the Client**
9999 Download the jar archive file: ` DolphinBot-[version]-full.jar ` .
100100
101- > [ !NOTE ]
101+ > [ !IMPORTANT ]
102102> Requirements: ** Java version >= 17**
103103
1041042 . ** Configuration of the Bot**
@@ -134,7 +134,7 @@ In this section, you will understand below how-tos:
134134 </p>
135135
136136> [!NOTE]
137- > **Warning:** Command-line has high authority than config file, meaning that if options are duplicated, will only recognize
137+ > Command-line has high authority than config file, meaning that if options are duplicated, will only recognize
138138 command-line, and ignore config file one.
139139
140140> [!TIP]
@@ -153,67 +153,67 @@ In this section, you will understand below how-tos:
153153 To specify the path of config file is optional, Use option `--config-file` to locate config directory or file.
154154 For example:
155155 ```bash
156- java -jar "DolphinBot-[version].jar" --config-file=path/to/config.json
156+ java -jar "DolphinBot-[version].jar" --config-file=path/to/config.json
157157 ```
158158 If the path you specified is a directory instead of a file, Dolphin will extract config file as default config in this directory.
159159 ```bash
160- java -jar "DolphinBot-[version].jar" --config-file=path/to/config_directory
160+ java -jar "DolphinBot-[version].jar" --config-file=path/to/config_directory
161161 ```
162162 If the `--config-file` parameter is absented, DolphinBot will create a default file on jar directory.
163163 ```bash
164- java -jar "DolphinBot-[version].jar"
164+ java -jar "DolphinBot-[version].jar"
165165 ```
166166 **multiple bot & proxy settings**
167167 In the profile config file, you can create `profiles` field in `bot.profiles.json` to specify multiple bot profiles to log to a server.
168168
169169> [!NOTE]
170- > Some servers may prohibit multiple bots started on same IP, proxy settings is aimed to help you to run multiple bots
171- from different network environments or requiring distinct egress IPs.
170+ > Some servers may prohibit multiple bots started on same IP, the proxy settings is aimed to help you to run multiple bots
171+ from different network environments or requiring distinct egress IPs.
172172
173173To configure proxy settings for each bot, you need to edit `proxy` field. An example shown below:
174-
175- > [!WARN]
176- > **Warning**: Defining multiple bots may trigger the anti-bot or anti-cheat, and some servers with strict policy may prohibit it.
177-
178- ```json
179- {
180- "profiles": {
181- "bot#1": {
182- "name": "Player494",
183- "password": "123example",
184- "owner": ["player_name"],
185- "enabled_plugins": [
186- "QuestionAnswerer",
187- "MessageDisplay",
188- "HumanVerify"
189- ],
190- "proxy": {
191- "enabled": false,
192- "info": {
193- "address": "XX.XXX.XXX.XX",
194- "port": 8081,
195- "type": "SOCKS4",
196- "username": "",
197- "password": ""
198- }
199- }
200- },
201- "bot#2": {
202- "name": "Player495",
203- "password": "password",
204- "owner": ["player_name", "other_owner"],
205- "enabled_plugins": [
206- "HumanVerify"
207- ],
208- "proxy": {
209- "enabled": false,
210- "info": {"...": "..."}
174+
175+ > [!WARNING]
176+ > Defining multiple bots may trigger the anti-bot or anti-cheat, and some servers with strict policy may prohibit it.
177+
178+ ```json
179+ {
180+ "profiles": {
181+ "bot#1": {
182+ "name": "Player494",
183+ "password": "123example",
184+ "owner": ["player_name"],
185+ "enabled_plugins": [
186+ "QuestionAnswerer",
187+ "MessageDisplay",
188+ "HumanVerify"
189+ ],
190+ "proxy": {
191+ "enabled": false,
192+ "info": {
193+ "address": "XX.XXX.XXX.XX",
194+ "port": 8081,
195+ "type": "SOCKS4",
196+ "username": "",
197+ "password": ""
211198 }
212- },
213- "bot#3": {"...": "..."}
214- }
199+ }
200+ },
201+ "bot#2": {
202+ "name": "Player495",
203+ "password": "password",
204+ "owner": ["player_name", "other_owner"],
205+ "enabled_plugins": [
206+ "HumanVerify"
207+ ],
208+ "proxy": {
209+ "enabled": false,
210+ "info": {"...": "..."}
211+ }
212+ },
213+ "bot#3": {"...": "..."}
215214 }
216- ```
215+ }
216+ ```
217217
218218 1. `enabled_plugins` field represents which plugins should enable on the bot.
219219 2. `proxy` fields (optional) represents a proxy configurations for each bot, field `enabled` marks whether activate this proxy setting,
@@ -226,7 +226,7 @@ To configure proxy settings for each bot, you need to edit `proxy` field. An exa
226226 | `type` | Proxy mode. (`HTTP`, `SOCKS4`, `SOCKS5`) |
227227
228228> [!TIP]
229- > "username", "password" is optional, if the remote proxy server require to auth, you need to add these.
229+ > "username", "password" is optional, if the remote proxy server require to auth, then you need to add these.
230230
231231 In this case, if you want to load `bot#1` as your single bot, you should add below argument:
232232 ```bash
0 commit comments