incorrect username or password

so today i just installing gamez black desert and successfully make an id through ur website... i can log in to the web with my passwod.. but when i tried to log in via the launcher it says incorrect username or password.. i have created another 2 accounts to make sure that i'm not have a mistake and it still says incorrect username or password in the launcher and i can log in to the website....

i have searched another old threads to find any clues but i can't find any... there's a thread that says i must be verified my account, but i can't find anything in my email (inbox and spam/junk) contain any verification email.... can someone help me? sry for my broken english

 

Are you sure that you're using the correct GamezBD client?
Or,
Perhaps, the problem might have been occurred after the games update. That's why you get that continuous "incorrect username & password messages".

Anyway, Try changing your password (Yeah, I know, i know you didn't type it wrong, and i'm pretty sure your info is correct). Maybe it'll work.
Apparently reinstalling the game is the best way to fix the problem.

If the problem still persist. The instructions here should be able to help you by clicking this link below:
http://forum.gameznetwork.com/threads/advanced-install-and-troubleshooting.206362/
Or contact any GamezBD staffs to be able to help you out.

 

already got a fix on this... i think the launcher is still buggy or somewhat error.....

the fix for me :
- u must click / checked button "remember" to get into the game
- if it leave unchecked, it will popup the warning "incorrect username/password"

i try install it on my cybercafe to attract more customers, so i have to tweak it a little bit using deep freeze so my customers's id will not saved to each client >_<

i hope it will fixed soon

 

Other than precious time burning, a complete reinstallation of the game is definitely not the solution, especially when it comes to launcher problem such as this one.
Apparently this is a launcher related issue which @Carl should be aware of.