1. Cultural Settlement - Feudal Japan

    Arising from the Sengoku period of Feudal Japan, the clan of Akechi Mitsuhide has requested your help.
    As the Daimyo of his village, it is your task to lead the Feudal Japan to prosperity! Detailed information here!
    Dismiss Notice
  2. Changelog 1.156

    Hello Queens and Kings,
    The update to 1.156 will take place on Wed, July 10, 2019. There will be a short period of downtime during the update, we apologize for any inconvenience caused during this time.
    For the detailed description of the upcoming changes, please see the details here.
    Dismiss Notice
  3. GvG Improvements

    Hello Queens and Kings,
    We'd like to keep you updated on what we're planning to do, as we're about to get started on implementing the following improvements, and would love to hear some community insight into if you feel these additions address some of the fundamental issues GvG faces.
    For the detailed description of the upcoming changes, please see the details here.
    Dismiss Notice
  4. Changelog 1.157

    Hello Queens and Kings,
    The update to 1.157 will take place on Wed, July 24, 2019. There will be a short period of downtime during the update, we apologize for any inconvenience caused during this time.
    For the detailed description of the upcoming changes, please see the details here.
    Dismiss Notice
Dismiss Notice

Opening The Tomb

Discussion in 'Bug Reports' started by Godly Luke, May 3, 2019.

  1. Godly Luke

    Godly Luke Well-Known Member

    Joined:
    Feb 4, 2018
    When I go to access the tomb area. My cursor goes to it's original out of game cursor. I have tried refreshing, restarting, and closing the window and opening it again. When I go to click it this happens. Nvm, you can screenshot a cursor... Anyways any resolution is welcome!
     
  2. Godly Luke

    Godly Luke Well-Known Member

    Joined:
    Feb 4, 2018
    It is the whole top row apparently.
     
  3. Godly Luke

    Godly Luke Well-Known Member

    Joined:
    Feb 4, 2018
    Phew! It fixed itself. I had to run an update, and it fixed itself!
     

Top