Valastro Baby
Active Member
- Joined
- Apr 4, 2015
- Sythe Gold
- 0
- Messages
- 213
I dont know where to post this, but i saw a similar thread posted in this section.
So i recently acquired the service of a sythe quester to get me 93 questpoints @ 600k/qp which came to 55.8m Gp http://www.sythe.org/members/450317-factory-new.html. Which has been given to the user http://www.sythe.org/members/405752-krillex.html to hold as the service is being completed.
Now here is where the problem arises and where i dont know what a fair compensation would be.
I ordered the quest points (93) in order to get barrows gloves on two conditions, the account would get a maximum of 45 defence, and a maximum of 16 prayer, which is reflected in the price.
http://gyazo.com/be29e24eaaa12f7e1c2e42224a107191 (he confirms 16 prayer and 45 def max, the acc at this point has 15 prayer completely quested, and no more prayer exp gaining quests need to be completed)
I log into my account to find the account now has 20 prayer due to the quester completing the quest (mountain daughter). I believe i should get some sort of compensation, not only did the quester negligently complete the quest and gained me a combat level, but now in order for my account to be efficient i will have to get 31 prayer + full void, gaining me another combat level and hours of work or 10+M for someone to complete the service.
That is a total of 2 combat levels which i did not want, and i believe that the quester is largely at fault becuase he should have known the quest gains prayer experience, due to him being a sythe quester, it is expected of him to know, or atleast put in the effort to check the experience gained from the quest, due to the stakes being so high.
https://gyazo.com/e84948b26894b213138ba3141e82feb9
I just want some idea on the amount of compensation, as i dont want to be under-compensated and im sure the quester doesnt want to over-compensate me, so i leave it to the admins to decide.
Will provide more if needed
Other information: So far he has completed quests totalling 14 quest points. But the service has stopped for now until we resolve this.
So i recently acquired the service of a sythe quester to get me 93 questpoints @ 600k/qp which came to 55.8m Gp http://www.sythe.org/members/450317-factory-new.html. Which has been given to the user http://www.sythe.org/members/405752-krillex.html to hold as the service is being completed.
Now here is where the problem arises and where i dont know what a fair compensation would be.
I ordered the quest points (93) in order to get barrows gloves on two conditions, the account would get a maximum of 45 defence, and a maximum of 16 prayer, which is reflected in the price.
http://gyazo.com/be29e24eaaa12f7e1c2e42224a107191 (he confirms 16 prayer and 45 def max, the acc at this point has 15 prayer completely quested, and no more prayer exp gaining quests need to be completed)
I log into my account to find the account now has 20 prayer due to the quester completing the quest (mountain daughter). I believe i should get some sort of compensation, not only did the quester negligently complete the quest and gained me a combat level, but now in order for my account to be efficient i will have to get 31 prayer + full void, gaining me another combat level and hours of work or 10+M for someone to complete the service.
That is a total of 2 combat levels which i did not want, and i believe that the quester is largely at fault becuase he should have known the quest gains prayer experience, due to him being a sythe quester, it is expected of him to know, or atleast put in the effort to check the experience gained from the quest, due to the stakes being so high.
https://gyazo.com/e84948b26894b213138ba3141e82feb9
I just want some idea on the amount of compensation, as i dont want to be under-compensated and im sure the quester doesnt want to over-compensate me, so i leave it to the admins to decide.
Will provide more if needed
Other information: So far he has completed quests totalling 14 quest points. But the service has stopped for now until we resolve this.


















