Visual kore X-kore cant use on euphro?

joshfulgencio · #1 Post by **joshfulgencio** » 11 Jul 2008, 04:29

It gets passed the login and char select, then it just says Rejected or failed. Im not banned or anything, i can log in fine wiht regular Visualkore and regular Euphro login but i cant use X-kore for some reason. someone please help this is the reason i bought visualkore.

#2 Post by **sli** » 11 Jul 2008, 21:41

X-Kore doesn't work on eA.

joshfulgencio · #3 Post by **joshfulgencio** » 11 Jul 2008, 23:38

thers no way to make it work =/. that stinks, is there gonna be an update in the works for this?

#4 Post by **Cozzie** » 12 Jul 2008, 03:16

not anytime soon, no devs are actively working on xkore atm.

#5 Post by **sli** » 12 Jul 2008, 18:45

What's the reason behind that? Personally, I think X-Kore is bloat and a useless feature. That's my excuse, anyway.

#6 Post by **Motivus** » 13 Jul 2008, 01:47

I've posted this in a lot of forums but I might as well post it again. I currently maintain XKore because no one else seems to want to. I looked in to why it didn't work on eAthena servers and the answer is very simple.

XKore works perfectly on all servers [with out custom protection], the issue is that OpenKore does not have a server type for new eAthena servers.

The bot sends the old login packet which forces eA to use an old packet version when communicating with the client. Newer Ragnarok clients send a different login packet and eA uses the newer packet version. Because XKore just forwards the clients' packet for logging in, the new version is used and OpenKore has no idea what is going on. It is possible for private server owners to completely block OpenKore by compiling SVN with strict support for the latest packet version.

Until someone adds a new serverType for the latest eA packet version botting on any EA server is a huge risk because simply connecting can flag you as a botter as long as the person running the server is competent.

#7 Post by **Cozzie** » 13 Jul 2008, 09:05

motivus, do you have a link to the current xkore development thread?

#8 Post by **sli** » 13 Jul 2008, 13:32

Motivus wrote:I've posted this in a lot of forums but I might as well post it again. I currently maintain XKore because no one else seems to want to. I looked in to why it didn't work on eAthena servers and the answer is very simple.

XKore works perfectly on all servers [with out custom protection], the issue is that OpenKore does not have a server type for new eAthena servers.

The bot sends the old login packet which forces eA to use an old packet version when communicating with the client. Newer Ragnarok clients send a different login packet and eA uses the newer packet version. Because XKore just forwards the clients' packet for logging in, the new version is used and OpenKore has no idea what is going on. It is possible for private server owners to completely block OpenKore by compiling SVN with strict support for the latest packet version.

Until someone adds a new serverType for the latest eA packet version botting on any EA server is a huge risk because simply connecting can flag you as a botter as long as the person running the server is competent.

Actually, vivi and I both were witness to it actually splitting the map login packet into two parts and that being the reason X-Kore mode gets no further than the char server. What you described affects all of OpenKore, not just X-Kore.

#9 Post by **Motivus** » 13 Jul 2008, 16:11

sli wrote: Actually, vivi and I both were witness to it actually splitting the map login packet into two parts and that being the reason X-Kore mode gets no further than the char server. What you described affects all of OpenKore, not just X-Kore.

Look, EA works like this:

Connect one -> use packet ver a
Connect two -> use packet ver b

The default compilation options enable both modes, and depending on how the client connects it uses the "right" packet version for that client. In XKore mode it connects using the new packet version because that is what all modern kRO clients use. EA then uses a mode kore can not currently understand because people have been lazy about making a server type for it.

If it still doesn't work when someone makes a proper server type for new eAthena I will fix it, but currently it is pointless because kore can't handle the server type.

#10 Post by **Bibian** » 13 Jul 2008, 19:13

I think your theory is wrong motivus...

If server X uses Servertype Y, why does using kore (without XKore on) work on using Servertype Y? But when you use XKore with servertype Y it fails? Your theory about strict packet handling is partially true, but imo has no real connection with this issue. An eA server without strict packet handling is able to handle openkore if you use servertype 3, but if you make it strict it has to be 8 or newer.

I believe the problem lies with XKore and not the servertypes, if it were a servertype problem you wouldn't have been able to login without XKore either. XKore does something weird with the maplogin packet, for some reason it sends 2 packets at login which are supposed to be 1 packet. But this doesn't happen in 100% of the cases, 95% of the cases it does this. but sometimes it doesn't. Also we have had reports of older versions of Openkore (with also an older version of XKore) work with eA servers where Openkore SVN's XKore doesnt work. So it HAS to be somewhere in the code of xkore.

OpenKore

Visual kore X-kore cant use on euphro?

Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?

Re: Visual kore X-kore cant use on euphro?