Team Cape

http://osbot.org/forum/topic/106643-rip-scammer-lost-charge-back/ 2pac tried to charge-back another player as well. This is an obvious scam attempt, just like it was with @@Sysm. This user needs to be banned because it's clear that he still has the complete intention of scamming; it wasn't just a one-time occurrence. Eventually, he'll scam someone new (hence losing someone from OSBot) or someone that doesn't know the community that well. It's only a matter of time, and I say that we shouldn't wait for it. Feel free to delete this if you want.

good shit u could make this any item by adding a string in the gui though then have an option to interact on it. would be pretty cool. edit: my bad. forgot this was from a few months ago lmao. im digging more graves than charles manson right now

Interesting. I will check this out in the next day and update it. Thanks for reporting

what a retard

[NOTE: GRAPHIC]

toaster

"literally 99% of the big scammers have been people that joined in the past few months and immediately bought lifetime sponsor (like within the first month of being here)" Wasn't aware that July 2013 was 1 month ago

In the time that I've been here (like 4 months or something?), literally 99% of the big scammers have been people that joined in the past few months and immediately bought lifetime sponsor (like within the first month of being here). maybe it's all the same person, who knows, but i cant help but notice that it's been a consistent trend. i am by no means saying that all people that fit into this category are scammers, but i can't help but notice the relative consistency. anyone else seen this sort of trend?

im arab and can confirm that shouting is usually far louder and more angry than this.

back

These are my words: (and the sleep times are pretty wtf too), Alek has seen my work and knows I don't do that. I wrote this up in like 3 minutes as pseudocode to explain my thought process lol

sick bro

no more rank??? edit: nvm it appeared for me once the page reloaded

the trick to good antiban is sleeping for at least 13241789348483218242 ms

The majority that I've seen on antiban is something along the lines of: public class Class extends Script { public int doScript(); public boolean antiBan() { //possibility one switch(random(0, 10)) { case 1: return tabs.open(Tab.INVENTORY); case 2: sleep(random(4123412, 13241789348483218242)); return randomNPC.hover(); case 3: case 4: return moveYourCamera(); case 5: return true; . . . } //possibility two (just a messier version of the 1st possibility) int random = random(0, 100); if(random < 20) { return doShit; } else if(random >= 20 && random <= 40) { return doAnotherShit; } else if(...) { return etc; } return false; } public int onLoop() { if(antiBan()) { return random(1523, 521983); } return doScript(); } } This is a very dumbed down version, granted, and I doubt that anyone would really break down the methods in the way that I did here (and the sleep times are pretty wtf too), but this seems very rudimentary and repetitive, and will only likely help an account get banned. Antiban is can also be placed inside of doScript(), but it still has the same effect. I've noticed this in multiple scripts, and I've started to realize that this kind of antiban actually aids in getting the player banned, so I've stopped adding it. There needs to be a way to randomize this more, or make it far less obvious. Has anyone found a better technique? TLDR: I'm looking for a way to make antiban more efficient in terms of both randomization and structure;

Significant. This sounds a lot like asking someone their salary... it's personal. If they want to share, they should feel free to, but it's not right to ask them like that - especially not in a public thread.

there wasnt an option for 'not pug' so i didnt vote.

@@Maldesto @@Dex

not if you wear it right.

probability will be on my side if i post more often!

just getting my daily free postcount. dont mind me

keeping the train chugging on

You're important to me baby and that's all that matters

this is inappropriate. not worth a new thread. especially for something that's not even a bug. if you dont like it, go post on the thread for the script. do not make a new thread and put someone on blast for something not everyone needs to know.

yeah my bad it is .closest() i had just woken up when i wrote that