Difference between revisions of "XKore"
Jump to navigation
Jump to search
(11 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | ; XKore | + | ; XKore <value> |
− | : | + | : Game client-reliant botting. |
− | + | {|class="TablePager", border=1 | |
− | |||
− | |||
|- | |- | ||
− | + | !Value | |
− | + | !Description | |
− | + | !Kore | |
− | + | !Game Client | |
− | + | !Diagram | |
|- | |- | ||
− | | | + | ! 0 |
− | + | | Plain old Kore. | |
− | * | + | | |
− | + | * required | |
− | * | + | * connects to the server |
− | + | | | |
+ | * unused | ||
+ | | [[File:XKore 0.png]] | ||
|- | |- | ||
− | + | ! 1 | |
− | | | + | | '''Sniffer''': Kore hooks onto client's connection with the server using [[NetRedirect]] library. |
− | + | | | |
− | * | + | * optional |
− | | | + | * hooks onto the client |
+ | * can be closed anytime | ||
+ | | | ||
+ | * required | ||
+ | * connects to the server | ||
+ | * username and password are passed to the server | ||
+ | | [[File:XKore 1.png]] | ||
|- | |- | ||
− | | | + | ! 2 |
− | + | | '''Server''': Plain old Kore additionally acts as a custom server for the game client. | |
+ | | | ||
+ | * required, connects to the server | ||
+ | | | ||
+ | * optional | ||
+ | * connects to [[XKore_publicIp]]:[[XKore_listenPort]] | ||
+ | * uses [[username]] and [[adminPassword]] | ||
+ | * can be connected and closed anytime | ||
+ | | [[File:XKore 2.png]] | ||
+ | |- | ||
+ | ! 3 | ||
+ | | '''Proxy''': Kore acts as a proxy between the client and the server. | ||
+ | | | ||
+ | * required | ||
+ | | | ||
+ | * required | ||
+ | * connects to [[XKore_listenIp]]:[[XKore_listenPort]] | ||
+ | * username and password are passed to the server | ||
+ | | | ||
|} | |} | ||
− | : | + | |
+ | == Notes == | ||
+ | * XKore is less tolerant to incorrect server settings. If everything works without XKore and there is some problem with XKore, it may still be a problem with server settings like [[serverType]], [[charBlockSize]] etc. | ||
+ | |||
+ | == XKore 1 == | ||
+ | * Kore will only start functioning when you connect or reconnect after Kore starts. | ||
+ | |||
+ | == XKore 2 == | ||
+ | * When using multiple Kores simultaneously, the following options should be enabled in maximum of one Kore: [[autoTalkCont]]. Otherwise you may experience problems like disconnects. | ||
+ | * It makes a sense to disable [[secureAdminPassword]], due to adminPassword being used to log in. | ||
+ | * Original client configured in the same way as with [[Poseidon]]. | ||
+ | |||
+ | == XKore 3 == | ||
[[Category:config.txt]] | [[Category:config.txt]] | ||
[[Category:XKore]] | [[Category:XKore]] |
Latest revision as of 21:58, 27 April 2021
- XKore <value>
- Game client-reliant botting.
Value | Description | Kore | Game Client | Diagram |
---|---|---|---|---|
0 | Plain old Kore. |
|
|
|
1 | Sniffer: Kore hooks onto client's connection with the server using NetRedirect library. |
|
|
|
2 | Server: Plain old Kore additionally acts as a custom server for the game client. |
|
|
|
3 | Proxy: Kore acts as a proxy between the client and the server. |
|
|
Notes
- XKore is less tolerant to incorrect server settings. If everything works without XKore and there is some problem with XKore, it may still be a problem with server settings like serverType, charBlockSize etc.
XKore 1
- Kore will only start functioning when you connect or reconnect after Kore starts.
XKore 2
- When using multiple Kores simultaneously, the following options should be enabled in maximum of one Kore: autoTalkCont. Otherwise you may experience problems like disconnects.
- It makes a sense to disable secureAdminPassword, due to adminPassword being used to log in.
- Original client configured in the same way as with Poseidon.