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)
 
(2 intermediate revisions by 2 users not shown)
Line 2: Line 2:
: Game client-reliant botting.
: Game client-reliant botting.


{|class="TablePager"
{|class="TablePager", border=1
|-
|-
!Value
!Value

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