i get this when l2phx catches the login of L2

 

History: NConsoleWnd::RequestAuthLogin <- NCAuthWnd::OnLoginBtnClick <- NCAuthWnd::OnPasswordDone <- NControl::SendEventMessage <- NCEditBox::OnKeyDown <- NCVirtualWndMain::PassToFocusedWindow <- NCVirtualWndMain::PassToFocusedWindow <- NCVirtualWndMain::PassToFocusedWindow <- NCVirtualWndMain::DispatchWndMsg <- NConsoleWnd::DispatchWndMsgX <- NConsoleWnd::DispatchWndMsg <- UWindowsViewport::ViewportWndProc <- WWindow::StaticProc <- DispatchMessage <- 00010382 256 <- MessagePump <- MainLoop

 

 

meaning ?

It mean's nothing. Well at least nothing usefull.

mmmm you try with other version of l2phx ?

is it not just a critical error? (of L2 client)

is it not just a critical error? (of L2 client)

 

Yes, but often taking the L2PHX open, when one tries to log in with your user and pass in the main window, got critical error.

 

Why this? i don't know..

yea i always get this RIGHT when l2phx connects to server....hmm

May its only a L2 client modification for block any dll injection...

its dempax64 or whatever its called, basic server protection, emded in fire.dll and something else.

 

nothing you can do about it.

 

There Is No Bypass For Depmax? I Really Hate It :(