What's new

What is the problem?

ExO

Admin
5,119
2014
1,639
It's an opcode, however it doesn't really matter and it's nothing that you have to take care about / worry about so just ignore it.
 

Northstrider

Verified Member
6
2014
1
if this opcode is not send as the console says, it's probably the issue that the smsg opcode is not sent, so the client is waiting and waiting for nothing and the server is always spamming ur console.

short answer: add the opcode handler for CMSG_TIME_SYNC_RESP (probably trinity got it. cant tell exactly cuz i have my own core.)
 
  • Like
Reactions: ExO

Northstrider

Verified Member
6
2014
1
go into opcode.cpp

search for
Code:
DEFINE_OPCODE_HANDLER(CMSG_TIME_SYNC_RESP,                          STATUS_LOGGEDIN,  PROCESS_INPLACE,      &WorldSession::HandleTimeSyncResp              );

if status_loggedin is status_unhandled change it and go into HandleTimeSyncResp function and check if its the same structure like TC's
 
Top