Disputed member: http://osbot.org/forum/user/53487-therealjok3y

Thread Link: N/A

Explanation:

I told him to powerlevel on my account from a fresh level 3. I haven't added an email, and he eventually changed the password not even 50% through the service. (not only 1 acc but I will post more later if he does end up scamming)

I need bond reimbursements. 

 

 

Evidence:

(just a skype confirmation)

 

 

 

I need a bond back + 300k in supplies for this acc, and i have more proof for other accs if you need it 

 

 

 

I have notified the user and made them aware of the dispute. I have also gone ahead and placed them in the Trade With Caution user group for the remainder of this time.

I just went ahead and hid the evidence that shows the email of the account so that way only mods can see it, and no one can interfere with the account further or report it to jagex.

so....please tell me what i did wrong? I'm hired to work on 2 account which I'm doing at the moment? i don't see what I've done here?

so....please tell me what i did wrong? I'm hired to work on 2 account which I'm doing at the moment? i don't see what I've done here?

 

The passwords to the account have been changed when they weren't meant to be. Doing a service means you take the accounts as they are and do not change any information on them except power level and complete them as you are supposed to.

 

Edit; Just had a word with Jok3y via pm and he claims the passwords have not been changed at all. Can you both PM me the last known password you had for the account along with the portion of the Skype convo which reveals that is the pass.

yes, but it will not allow me to pm you

yes, but it will not allow me to pm you

 

You can post here as well, I will remove the contents before approving it.

 

Edit: Sent you a pm so you can respond if you wish.

I have received confirmation from @TheRealJok3y via PM of the last known username and password. We will wait for @Cinnamon to post his part along with the Skype portion.

 

Edit: Spoke to @Cinnamon in the chatbox, issue seems to be resolved.