Some differences in my build version.

[scott-s0ny]

[My build version]
23:38:38 | Debug | WorldSocket | C<P S | Sending opcode SMSG_AUTH_CHALLENGE (12360).
23:38:38 | Debug | WorldSocket | C>P S | Received opcode CMSG_AUTH_SESSION (14181).
23:38:38 | Server | WorldSocket | WorldSocket:HandleAuthSession: Client 'RGOP13' authenticated successfully from 127.0.0.1:55799.
23:38:38 | Network | WorldClient | Connecting to world server...
23:38:38 | Network | WorldClient | World Server address 127.0.0.1:8085 resolved as 127.0.0.1:8085
23:38:38 | Network | WorldClient | Connection established!
23:38:38 | Debug | WorldClient | C P<S | Received opcode SMSG_AUTH_CHALLENGE (492).
23:38:38 | Debug | WorldClient | C P>S | Sending opcode CMSG_AUTH_SESSION (493) with size 221.
23:38:38 | Debug | WorldClient | C P<S | Received opcode SMSG_WARDEN_DATA (742).
23:38:38 | Warning | WorldClient | C P<S | No handler for opcode SMSG_WARDEN_DATA (742) (Got unknown packet from WorldServer)
23:38:38 | Debug | WorldClient | C P<S | Received opcode SMSG_ADDON_INFO (751).
23:38:38 | Debug | WorldSocket | C<P S | Sending opcode SMSG_AUTH_RESPONSE (9581).
23:38:38 | Error | WorldSocket | The WorldClient failed to connect to the selected world server!
23:38:38 | Error | AuthClient | C P<S | Socket Closed By Server
23:38:38 | Debug | BnetServices | [BnetTcp][127.0.0.1:55785, Account: RGOP13, Game account: RGOP13] Client requested service ConnectionService/m:7
23:38:38 | Error | WorldClient | C P<S | Socket Closed By GameWorldServer (header)

[Release version]
23:39:27 | Debug | WorldSocket | C<P S | Sending opcode SMSG_AUTH_CHALLENGE (12360).
23:39:27 | Debug | WorldSocket | C>P S | Received opcode CMSG_AUTH_SESSION (14181).
23:39:27 | Server | WorldSocket | WorldSocket:HandleAuthSession: Client 'RGOP13' authenticated successfully from 127.0.0.1:55869.
23:39:27 | Network | WorldClient | Connecting to world server...
23:39:27 | Network | WorldClient | World Server address 127.0.0.1:8085 resolved as 127.0.0.1:8085
23:39:27 | Network | WorldClient | Connection established!
23:39:27 | Debug | WorldClient | C P<S | Received opcode SMSG_AUTH_CHALLENGE (492).
23:39:27 | Debug | WorldClient | C P>S | Sending opcode CMSG_AUTH_SESSION (493) with size 221.
23:39:27 | Debug | WorldClient | C P<S | Received opcode SMSG_WARDEN_DATA (742).
23:39:27 | Debug | WorldClient | C P>S | Sending opcode CMSG_WARDEN_DATA (743) with size 5.
23:39:27 | Debug | WorldClient | C P<S | Received opcode SMSG_ADDON_INFO (751).
23:39:27 | Debug | WorldClient | C P<S | Received opcode SMSG_AUTH_RESPONSE (494).
23:39:27 | Network | WorldClient | Authentication succeeded!

In my build from the released code, there is no handler for opcode SMSG_WARDEN_DATA (742), which derives the socket closing.
I can't log in using my build version. but I can log in using the released version.
I want to fix some problems of grouping other characters far from my character. So I wanna build my self.

Is there any problem with my build process!?

[ratkosrb]

Warden is the server anticheat. You should disable the anticheat server side if you want to connect with your own build. Only the official release can pass the anticheat checks.

[scott-s0ny]

@ratkosrb

But when I use the released version, I can connect the server correctly. (Same server)
The only difference is that it's just my build version for the proxy. (play as well)
Even though I built the released source code, the warden problem arose.
But the released built version has no problem with Warden.

So I can't understand that Watden is a server-side problem.

[celguar]

Only the official release can pass the anti cheat checks. The code to pass those checks is not included publicly, so when you build yourself you build a version that can't work with anti cheat