Topic

[fixed] Messages from Pet Rock

Sometimes, the messages from my pet rock don't come through. I'm notified of messages, I just can't click on them... and then there's no way to read previous messages.
I am using Chrome in windows.

btw, this was the first time I got to play, and I'm already hooked. My friends saw my screen, and when they saw I bought a house (they're old UO guys) and milk butterflies, they were hooked too. Can't wait for the next tests.

Posted 3 years ago by max Subscriber! | Permalink

Replies

  • I've had the same problem with the pet rock messages in Chrome, Win7(64bit), Flash version WIN 10,0,45,2 (the RC doesn't seem to work well with my OS version?).
    Posted 3 years ago by fluorescence Subscriber! | Permalink
  • same here, Chrome and same flash version on WinXP.
    Posted 3 years ago by Nevet Subscriber! | Permalink
  • Same problem. Using Firefox 3.6.3 / Mac OSX 10.4.11 / Flash 10,0,45,2
    Posted 3 years ago by Moumoushou Subscriber! | Permalink
  • Same. Mac 10.6.3, newest stable safari and flash
    Posted 3 years ago by Edward Subscriber! | Permalink
  • Unfortunately Chrome 5's method of handling pop-ups means that you won't really be able to use it to play Glitch unless/until we no longer use pop-ups for various menus and other things. I don't have an estimate on when that will be, if we ever do it, so for the time being I'd suggest using another browser for Glitch. I know it's not ideal but there isn't a lot we can do about it because the problem lies within Chrome itself.

    If you're having problems with Firefox or Safari then I'd suggest making sure that it's not blocking pop-ups - sometimes it does this rather silently. Let me know if you tried this in a browser other than Chrome 5 and it still didn't work.
    Posted 3 years ago by Beefcake Subscriber! | Permalink
  • So the bad news is it's not a pop-up issue, but the good news is that it was fixed recently anyway. It can still happen on occasion when the client gets out of sync with the server, but if you click the message it should go away and not return. The client sync thing is another issue that we're working on but for now this error should be a lot less irritating :)
    Posted 3 years ago by Beefcake Subscriber! | Permalink