Quote:
Originally Posted by Korvacs
Clientless bots dont exist publically for a number of reasons, firstly they are difficult to get working, secondly they are difficult to keep upto date, and finally and most importantly, they dont exist publically because they will be over used and therefore abused, which will trash the economy, will resulting in alot of exploits being patched (dont suppose you recall the Fatal strike speed exploit being patched? Partly by your own hand with cofarmer) and will result in yet anouther big encryption change which will mean no botting for 6 months.
Youve made a massive error in judgement by adding such a feature... :rolleyes:
|
From what I've heard matt isn't even a developer. (I forgot his old name here) But .John is the actual developer so there's no point in talking to matt about it, he's just the voice of co farmer.
Anyways yes, clientless is a bad decision over all to be released publicly.
You argument about my public anti aimbot and aimbot is totally skewed.
Clientless and aimbot are on two totally different levels of botting/ exploitation.
You didn't hear anyone bitch about CoFarmers aimbot. Cause it's not a big deal. The reason you guys have some many complaints by the co hacking community is because well, IT'S A FUCKING STUPID DECISION YOU GUYS HAVE MADE. You see clint maybe showing everyone he's got clientless, other people have it too. But who the fuck gives it to the public? NO ONE. For a good damned reason too.
Whether or not the encryptions change doesn't matter a damn bit to me, I don't have to worry about them, proxy might be gone but there's always other ways.
You may be looking at this from a financial point of view.
But if it's not even a big feature... then who cares that it's clientless?
You won't be getting many new subscribers for clientless alone anyways. Alls you will be doing is putting CoFarmer developers work at risk.
Everything would be back at point one. Maybe the logic of the bot doesn't have to change. But who want's to go threw all of the trouble of figuring out how to re-make a proxy when it can be completely avoided in the first place?
Selfish decision made, good to have for personal use. But the public doesn't need it, and no one seems all that excited about it anyways.
Best thing you guys could do is remove the feature and act like it never existed.