Resolved Runemate Session Ended

Discussion in 'Client & Site Support' started by kazemanie, Oct 10, 2015.

  1. I was using Celestial Divination for around 25 minutes when a popup appeared on screen saying something like "Your Runemate Session Has Ended...." I didn't see what else it said before accidentally closing it.

    I couldn't start another bot again so had to close the client and reload it completely.

    For some reason I also had to reauthorise the Runemate client when I had already done this previously.


    EDIT: Could this have been caused by me loading Popcorn Time when Runemate was already running? The Popcorn Time client autoloads a VPN service when I start watching a TV show. Runemate had been running for around 10 minutes, then I loaded Popcorn Time, the Runemate client showed the error about 5-10 minutes after loading Popcorn Time.

    EDIT 2: I found my log file

    Code (Text):
    1. (10:33:33) [Debug] Version: 1.2.13
    2. (10:33:33) [Debug] Operating System: Windows 8.1 (x64)
    3. (10:33:33) [Debug] Java: 8 Update 60 (x64)
    4. (10:33:35) [Clean up] Deleted 5 outdated log files.
    5. (10:39:22)
    6. (10:39:43) Thanks for choosing Celestial Divination!
    7. (10:39:57) Rift position set to: Coordinate(3805, 3552, 0)
    8. (10:40:07) Radiant memory (ID: 29393) cached
    9. (10:40:07) Radiant energy (ID: 29322) cached
    10. (10:40:08) Radiant energy (ID: 29322) cached
    11. (10:40:09) Radiant memory (ID: 29393) cached
    12. (10:40:10) Radiant memory (ID: 29393) cached
    13. (10:40:12) Enriched radiant memory (ID: 29404) cached
    14. (10:41:54) Celestial Antipattern case 5: turn camera to random NPC
    15. (10:44:17) Capturing a chronicle
    16. (10:44:18) Capturing a chronicle
    17. (10:44:19) Chronicle fragment (ID: 29293) cached
    18. (10:44:24) Celestial Antipattern case 9: considering some afking
    19. (10:44:24) Chance on afking: 5.0%
    20. (10:45:19) Capturing a chronicle
    21. (10:45:20) Capturing a chronicle
    22. (10:45:21) Capturing a chronicle
    23. (10:48:17) Capturing a chronicle
    24. (10:48:19) Capturing a chronicle
    25. (10:48:20) Capturing a chronicle
    26. (10:48:55) Capturing a chronicle
    27. (10:50:26) Celestial Antipattern case 5: turn camera to random NPC
    28. (10:55:51) Celestial Antipattern case 4: changing camera yaw
    29. (10:58:54) Celestial Antipattern case 8: click random player
    30. (10:59:01) Failed to extend session... (300 seconds remaining)
    31. (11:01:32) Failed to extend session... (149 seconds remaining)
    32. (11:01:59) Celestial Antipattern case 10: moving mouse off screen
    33. (11:02:48) Failed to extend session... (73 seconds remaining)
    34. (11:03:33) Failed to extend session... (28 seconds remaining)
    35. (11:03:49) Failed to extend session... (12 seconds remaining)
    36. (11:04:04) Unable to extend session because it had already expired 3 seconds ago
    37. (11:04:15) Updated personal signature
    38. (11:04:16) Updated global signature
    39. (11:04:16) [Session Expired] Your RuneMate session has expired. This can happen for many reasons.
    40. (11:04:16) [Session Expired]
    41. (11:04:16) [Session Expired] If <a href="https://www.RuneMate.com/">https://www.RuneMate.com/</a> is unavailable, please try again later. Otherwise, contact the Staff for more specific information.
    42.  
     
    #1 kazemanie, Oct 10, 2015
    Last edited: Oct 10, 2015
  2. Best Answer:
    Post #2 by Microsoft, Oct 10, 2015
  3. RuneMate needs to have a pretty much constant connection to it's servers.
    Since Popcorntime uses a VPN, it changes your IP which results in this issue.
     

Share This Page

Loading...