Another logging on issue?

Discussion in 'General Archive' started by .-ŚìζvєŖ†βuζζєT-., Oct 7, 2014.

Dear forum reader,

if you’d like to actively participate on the forum by joining discussions or starting your own threads or topics, please log into the game first. If you do not have a game account, you will need to register for one. We look forward to your next visit! CLICK HERE
  1. I tried to log on last night at around 12:20am & couldn't do so despite using 4 different browsers over an a hour.

    On Mozilla Firefox it would come up with an error in conection after a bit & the following message ...

    An error occurred while processing your request.
    Reference #97.8e8c3451.1412644177.1db83ae.


    I know this is not normal & can you explain why?

    You create these problems & if some players suffer more than others & ask for compensation because they have suffered more, you fob them off with excuses & state that individual compenstion is not considered & any compensation would be given as a whole. However, we know that this is total rubbish & baloney as there are players who have been accused of certain things & when these accusations turned out to be baseless & unfounded, they were given individual compensation packages.

    This is another example of the DOUBLE STANDARDS that are being employed in this game. It is about time players started being treated like players & as individuals & not like some mindless cattle to the slaughter!!
     
  2. i had this again this morning. its taken me 20 minutes of trying to get past the dreaded

    An error occurred while processing your request.
    Reference #pick-a-number


    it seems to be associated with auth3.bpsecure.com

    the other evening i wasted an hour. clearing cache, etc doesn't seem to help

    another DO cockup ??

    steve
     
  3. Had the same problem this morning trying to log in.

    auth3.bpsecure.com is a server I believe & it's DNS admin is sysadmins@bigpoint.net. In other words, it is Bigpoint's fault that these problems occur, not ours. As such, Bigpoint should pull their finger out & rectify this problem!!
     
  4. Hello .-ŚìζvєŖ†βuζζєT-.

    Sorry for the delayed response.


    Anything further on this same subject?