The Last Homely House

Undying Lands => Valinor => Topic started by: Bruno on January 27, 2013, 08:49:05 PM

Title: inactive for too long, Refresh or re-enter
Post by: Bruno on January 27, 2013, 08:49:05 PM

Hi,

I'm not that new on Gemp-Lotr but i've been having this message since beginning and i'm wondering if there is something to do to remove it. Every time i log in, i get this message where i've been inactive for too long and that i need to refresh or re-enter the game hall. and recently it's worst with the new server update were i can't chat at all.

i would apresiate if someone could help me out with this.

Thank you and it's fun to finaly play again this awsome game whit awsome people.

B

Title: Re: inactive for too long, Refresh or re-enter
Post by: MarcinS on January 28, 2013, 01:45:34 AM

Quote from: Bruno on January 27, 2013, 08:49:05 PM

Hi,

I'm not that new on Gemp-Lotr but i've been having this message since beginning and i'm wondering if there is something to do to remove it. Every time i log in, i get this message where i've been inactive for too long and that i need to refresh or re-enter the game hall. and recently it's worst with the new server update were i can't chat at all.

i would apresiate if someone could help me out with this.

Thank you and it's fun to finaly play again this awsome game whit awsome people.

B

What browser are you using and which version? You can try either updating your browser to the latest version, or alternatively download and install Chrome.

Title: Re: inactive for too long, Refresh or re-enter
Post by: Bruno on January 28, 2013, 06:48:56 PM

chrome worked thanks i apresiate

Title: Re: inactive for too long, Refresh or re-enter
Post by: bibfortuna25 on January 28, 2013, 11:05:48 PM

I get that message when I use Gemp on my iPad, where I use Safari as my browser.

Title: Re: inactive for too long, Refresh or re-enter
Post by: MarcinS on January 31, 2013, 08:03:31 AM

Quote from: bibfortuna25 on January 28, 2013, 11:05:48 PM

I get that message when I use Gemp on my iPad, where I use Safari as my browser.

Try clearing your browser cache. About a week ago I have deployed a new version that fixed this problem for CoS.