XKore: Difference between revisions

From OpenKore Wiki
Jump to navigation Jump to search
mNo edit summary
m (4epT moved page xKore to XKore over a redirect without leaving a redirect)
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
; XKore [<value>]
; XKore <value>
: This option toggles game client-reliant botting. If this is enabled, Kore will act as described in the following table's description.
: Game client-reliant botting.


:{|border="1" cellpadding="2" cellspacing="1"
{|class="TablePager", border=1
|- style=background-color:#F9F9F9;
!value !!Description !!Game Client !!Diagram
|-
|-
|align=center| 0
!Value
||
!Description
* XKore is disabled.
!Kore
* Kore acts as a client connecting to the RO server.
!Game Client
* No connection with the RO client.
!Diagram
|| unused || [[File:XKore 0.png]]
|-
|-
|align=center| 1
! 0
||
| Plain old Kore.
* RO client acts as a client connecting to the RO server, and must be connected/relogged after Kore starts to allow Kore to connect.
|
* Kore hooks onto the RO client's connection with the RO server ''(NetRedirect.dll required)''.
* required
* Kore can be closed anytime and RO client will stay connected.
* connects to the server
* No configuration for [[username]] and [[password]] needed in Kore.
|
|| required || [[File:XKore 1.png]]
* unused
| [[File:XKore 0.png]]
|-
|-
|align=center| 2
! 1
||
| '''Sniffer''': Kore hooks onto client's connection with the server using [[NetRedirect]] library.
* Kore acts as a client connecting to the RO server, and can act as a server (listening at [[XKore_publicIp]]:[[XKore_listenPort]]) for the RO client if desired.
|
* RO client can be connected to Kore or closed anytime.
* optional
* Kore must be configured to connect to the RO server; RO client must connect to Kore and use [[username]] and [[adminPassword]] to authenticate ''(so it makes a sense to disable [[secureAdminPassword]])''.
* hooks onto the client
|| optional || [[File:XKore 2.png]]
* can be closed anytime
|
* required
* connects to the server
* username and password are passed to the server
| [[File:XKore 1.png]]
|-
|-
|align=center| Proxy
! 2
||
| '''Server''': Plain old Kore additionally acts as a custom server for the game client.
* Kore will act as a proxy between the RO client and the RO server (listening at [[XKore_listenIp]]:[[XKore_listenPort]] for client connection).
|
* Both Kore and the RO client are always required.
* required, connects to the server
|| required
|
||
* 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.
  • required
  • connects to the server
  • unused
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
XKore 1.png
2 Server: Plain old Kore additionally acts as a custom server for the game client.
  • required, connects to the server
XKore 2.png
3 Proxy: Kore acts as a proxy between the client and the server.
  • required


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