XKore: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 18: | Line 18: | ||
* Kore hooks onto the RO client's connection with the RO server ''(NetRedirect.dll required)''. | * Kore hooks onto the RO client's connection with the RO server ''(NetRedirect.dll required)''. | ||
* Kore can be closed anytime and RO client will stay connected. | * Kore can be closed anytime and RO client will stay connected. | ||
* No configuration for | * No configuration for [[username]] and [[password]] needed in Kore. | ||
|| required || [[File:XKore 1.png]] | || required || [[File:XKore 1.png]] | ||
|- | |- | ||
Revision as of 16:00, 31 August 2010
- XKore [<value>]
- This option toggles game client-reliant botting. If this is enabled, Kore will act as described in the following table's description.
value Description Game Client Diagram 0 - XKore is disabled.
- Kore acts as a client connecting to the RO server.
- No connection with the RO client.
unused 
1 - 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).
- Kore can be closed anytime and RO client will stay connected.
- No configuration for username and password needed in Kore.
required 
2 - 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.
- 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).
optional 
Proxy - 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
