XKore: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
Line 50: | Line 50: | ||
| | | | ||
|} | |} | ||
== 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 == |
Revision as of 23:53, 13 April 2012
- XKore <value>
- Game client-reliant botting.
Value | Description | Kore | Game Client | Diagram |
---|---|---|---|---|
0 | Plain old Kore. |
|
|
|
1 | Kore hooks onto client's connection with the server using NetRedirect.dll. |
|
|
|
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.