Difference between revisions of "XKore"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
|align=center| 0 | |align=center| 0 | ||
|| | || | ||
| − | * | + | * XKore is disabled. |
| + | * Kore acts as a client connecting to the RO server. | ||
* No connection with the RO client. | * No connection with the RO client. | ||
|| unused || [[File:XKore 0.png]] | || unused || [[File:XKore 0.png]] | ||
| Line 14: | Line 15: | ||
|align=center| 1 | |align=center| 1 | ||
|| | || | ||
| − | * Kore hooks onto the RO client's connection with the RO server. | + | * 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 and RO client will stay connected. | + | * Kore can be closed anytime and RO client will stay connected. |
|| required || [[File:XKore 1.png]] | || required || [[File:XKore 1.png]] | ||
|- | |- | ||
|align=center| 2 | |align=center| 2 | ||
|| | || | ||
| − | * Kore acts as a client connecting to the RO server | + | * Kore acts as a client connecting to the RO server, and can act as a server for the RO client if desired. |
| − | * RO client can be connected or closed anytime. | + | * RO client can be connected to Kore or closed anytime. |
|| optional || [[File:XKore 2.png]] | || optional || [[File:XKore 2.png]] | ||
|- | |- | ||
| − | |align=center|Proxy|| | + | |align=center| Proxy |
| − | * Kore will act as a proxy between the RO client and | + | || |
| + | * Kore will act as a proxy between the RO client and the RO server. | ||
| + | * Both Kore and the RO client are always required. | ||
| + | || required | ||
| + | || | ||
|} | |} | ||
Revision as of 12:21, 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.
required 
2 - Kore acts as a client connecting to the RO server, and can act as a server for the RO client if desired.
- RO client can be connected to Kore or closed anytime.
optional 
Proxy - Kore will act as a proxy between the RO client and the RO server.
- Both Kore and the RO client are always required.
required
- Note: It is not advised to set secureAdminPassword if you're using Xkore 2.
