Network/Receive/ServerType0.pm: '01DC' => ['secure_login_key', 'x2 a*', [qw(secure_key)]],
This received packet does not exist in the kRO ST tree and I have yet to see a pserver that uses it.
I suspect that this is a mere symptom of a bigger issue.
Some packet lenghts in recvpackets may be wrong, causing incorrect tokenization of the incoming datastream. (= splitting the received packetstream up in actual packets)
(kore is probably mixing up packet data & switches)
A wrong length may cause kore to go look in packet data for a packet switch, which may cause several problems.
When this non-actual switch does exist, kore will unpack the bogus data and build a bogus environment from this.
This could explain unknown Monsters/NPC's.
If kore then decides to attack one of these bogus/phantom monsters, the server can acknowledge that the client is sending bogus data (e.g. bogus ID of a monster that does not exist on the map) and may disconnect the client.
When this wrong switch does not exists, kore throws away all received data from its buffer.
When the server sends a request that kore must answer, like a synchronisation packet or some such, kore may not be able to respond if the packet gets lost by kore throwing away this buffer.
This could also explain the disconnects.
Also client-sent packets may cause disconnects, when the client version of the packet does not match the server version of the packet.
Again, the server may decide that a client is sending bogus data and dc it.
(I'm not referring to those configuration options: server_version or client_version here, altough, there is a connection somewhere)
Anyhow, you told me your .exe was packed and could not extract recvpackets?
I suggest you upload that exe somewhere and ask on the forums if someone could help you unpack it.
