1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Staff Response Error Code 3 Via Steam

Discussion in 'Technical Support' started by RipVonBongle, Jul 3, 2018.

  1. RipVonBongle

    Joined:
    Dec 23, 2017
    Messages:
    29
    Likes Received:
    30
    Hello, I am currently getting an error code 3 on steam while trying to load the game. I have a fully functional internet connection and was afk fishing this morning without any problems before I shut my computer off and went off to work. I have tried several times to restart the steam client. I do not believe I have had this error in the past.
     

    Attached Files:

  2. megadoom20

    Joined:
    Sep 1, 2017
    Messages:
    22
    Likes Received:
    36
  3. KawaiiNyan

    Joined:
    Jul 3, 2018
    Messages:
    4
    Likes Received:
    0
  4. Boink

    Joined:
    Aug 14, 2017
    Messages:
    1,499
    Likes Received:
    1,014
    Steam Player here getting the same results.

    Steam Updated probably the reason why.
     
  5. SpuRkZ

    Joined:
    Jul 3, 2018
    Messages:
    1
    Likes Received:
    0
    I think all steam players are getting it. Hope it will be fixed soon.
     
  6. KawaiiNyan

    Joined:
    Jul 3, 2018
    Messages:
    4
    Likes Received:
    0
    Im back in, guess it got fixed?
     
  7. DownrightCynical

    Joined:
    Jan 16, 2018
    Messages:
    28
    Likes Received:
    27
    So, my Guild History log has been broken for 5 months, my Coherent UI completely ruined everything and makes it so I cant even play the boardgame for 3 months now (along with using features like the guild rank, beauty album, ect) and now I can't even launch the game at all. These bugs on BDO are the greatest.
     
  8. GM Kaioken

    Game Master

    Joined:
    Oct 19, 2017
    Messages:
    2,989
    Likes Received:
    332
    If this issue is persisting for anyone, please completely exit your Steam Client and then run it again with Administrator Rights.
    This should resolve the issue for you, but if not, send us a ticket, please.
     

Share This Page