Groundhack
New Member
- Joined
- Jun 1, 2011
- Messages
- 8
- Reaction score
- 0
So this isn't a permanent fix for the problem per say but it does let you use the ryftomate bot again
now when I updated yesterday I kept on getting the session key already in use BS that I noticed a few people were getting. Many of the posts asked to restart computer well after 6 restarts because of
Uac crashin my rift by dimming the screen I found out you can open a cmd prompt and ipconfig /release and /renew and ryftomate will work again.
I am thinking that this error is caused by ryftomate maybe not issuwing a logout command to the bot server or something so while the bot may not be on and working something is still connected and by resetting your IP you sever the connection allowing you to relog into the bot and continue botting. Sorry foe the bad spelling I'm typing from my cm7 captivate
now when I updated yesterday I kept on getting the session key already in use BS that I noticed a few people were getting. Many of the posts asked to restart computer well after 6 restarts because of
Uac crashin my rift by dimming the screen I found out you can open a cmd prompt and ipconfig /release and /renew and ryftomate will work again.
I am thinking that this error is caused by ryftomate maybe not issuwing a logout command to the bot server or something so while the bot may not be on and working something is still connected and by resetting your IP you sever the connection allowing you to relog into the bot and continue botting. Sorry foe the bad spelling I'm typing from my cm7 captivate