XKore: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
: Game client-reliant botting. | : Game client-reliant botting. | ||
{|class="TablePager" | {|class="TablePager", border=1 | ||
|- | |- | ||
!Value | !Value | ||
| Line 20: | Line 20: | ||
|- | |- | ||
! 1 | ! 1 | ||
| Kore hooks onto client's connection with the server using [[NetRedirect]] | | '''Sniffer''': Kore hooks onto client's connection with the server using [[NetRedirect]] library. | ||
| | | | ||
* optional | * optional | ||
* | * hooks onto the client | ||
* can be closed anytime | * can be closed anytime | ||
| | | | ||
* required | * required | ||
* connects to the server | * connects to the server | ||
* username and password are passed to the server | |||
| [[File:XKore 1.png]] | | [[File:XKore 1.png]] | ||
|- | |- | ||
! 2 | ! 2 | ||
| Plain old Kore additionally acts as a custom server for the game client. | | '''Server''': Plain old Kore additionally acts as a custom server for the game client. | ||
| | | | ||
* required, connects to the server | * required, connects to the server | ||
| Line 37: | Line 38: | ||
* optional | * optional | ||
* connects to [[XKore_publicIp]]:[[XKore_listenPort]] | * connects to [[XKore_publicIp]]:[[XKore_listenPort]] | ||
* uses [[username]] | * uses [[username]] and [[adminPassword]] | ||
* can be connected and closed anytime | * can be connected and closed anytime | ||
| [[File:XKore 2.png]] | | [[File:XKore 2.png]] | ||
|- | |- | ||
! | ! 3 | ||
| Kore acts as a proxy between the client and the server. | | '''Proxy''': Kore acts as a proxy between the client and the server. | ||
| | | | ||
* required | * required | ||
| Line 48: | Line 49: | ||
* required | * required | ||
* connects to [[XKore_listenIp]]:[[XKore_listenPort]] | * 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 == | == XKore 1 == | ||
| Line 57: | Line 63: | ||
* When using multiple Kores simultaneously, the following options should be enabled in maximum of one Kore: [[autoTalkCont]]. Otherwise you may experience problems like disconnects. | * 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. | * 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 | == 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.