84 replies to this topic

[Ilya]

hawk when i came in i had 1.8 avarage, you noob had 1.1 and still have.. so dont blame me that you can even applyf ro private because you lacking posts...

you liked my application that much huh?

Edited by Adobe, 07 April 2006 - 08:14 PM.

[Balistix]

@hawk : oh.. my bad . Sorry sir . . *feel silly* haha

@adobe : Ender earn his way in, obviously he is eligible to use the ab too. Beside he is a good programmer . If you dont play neo anymore then you shouldnt worry about the ab being in private lol.

[Sean]

Too bad you wont get to see it either hawk...

and ender, dont argue like you know what you saying... you only saying that because your an smod... you got access to everything... If i was an smod hell yea i would like a private aber....

Anyway I dont play neo anymore...

Wtf?!

Don't argue like you know what you are saying?
He DOES know what he is saying. If he is staff, then he knows what he is talking about, when talking about the rules of a website that he dedicates a lot of his on.

And are you rubbing it in somebody's face that you are elligible to apply for private?
wtf?

>_<

Edited by Sean, 07 April 2006 - 08:20 PM.

[Hawk]

@Balistix its ok, either Im too blunt or to, well, the other end of the spectrum

@Adobe
Ooh, so because I care about my grades in school and get off at difficult times means I am inactive? I just finished my two most stressful quarters of school. I have always been under the impression that real life issues > online stuff.

Technically you cannot even apply for private. By the way, please dont use "...", it is annoying. One simple period or comma will be fine.

I liked your application so much I never read it

Calling me a noob? I got a pic for you

Also, I will see it sometime, whether in two months, or two years. I doubt I will be using it then, but whatever.

If you dont play neo anymore why would you like a private autobuyer? Ender deserves access to everything, he is a contributing, loyal member. That is what seperates the few from the rest of the pack.

PM me back if your going to flame or argue. I dont care, do either, I wont report it unless it gets too out of hand

Edited by hawk117, 07 April 2006 - 08:50 PM.

[Nenofyn]

Ehm, yeah xD

I hope i'm not being too late with leaving my opinion here but I have to agree with Adobe and Noitidart. An ABer should be simple, no extra things like multiply account option and so on.

A perfect ABer (for me) should be:

-Login in with your account
-Entering id number of shop
-Load the list you have for the shop
-Set No RS and set RS options
-The max refreshes you want
-A log under that all to see what the ABer missed or got for you
-The prices you bought the items for -to see what items are bringing much profit and wich not- and that's about it.

I hope I explained it good xD

[fred]

For the timing of the Ab, Have it set so that it will check the food shop at 0-1 seconds, if it doenst rs then it wont refresh at your desinated abing spot. This will make rs banned very difficult to get. P/M me for anymore qustions...

**also sockopen i have still have your other program with all those different programs in it. haha

Edited by fred, 09 April 2006 - 07:49 AM.

[Decade]

haha hawk, thats such a funny pic

i wouldnt care what goes into an autobuyer, except that it works, and maybe pull np from shop till. thats about it

[llywelyn]

Here's the thing for all you saying that extra options "bog it down". If your running of NST time and waiting for the correct restock time to check the shop, the program is sitting there and increasing a small number, that's all it's doing. Anything extra would logically be done in that great amount of availible time, not when the program is busy trying to buy items. With that amount of time, you could check your till, stock and price bought items, and even check up on a pet training in the mystery island or something. Basic can be good, but advanced can run just as fast if you put it together right, and I KNOW sock knows how to do that

Well if he knows how, then that's great. I have come across quite a few programs though where the multiple features haven't worked efficiently, hence my previous comment.

Also another consideration should be risk factor. If you have a program which is automatically buying items, as well as training your pets, stocking/pricing items, and handling your finances in it's spare time, surely there's a greater risk of being frozen. Would it not be better to keep it as un-automated as possible?

[Kyle]

Well if he knows how, then that's great. I have come across quite a few programs though where the multiple features haven't worked efficiently, hence my previous comment.

I agree. Assuming its not going to still be processing a request to train a pet when the refresh time comes, then it will be wonderful. Because its an AutoBuyer, the actual process of AutoBuying should override the other processes going on at that specific time.

[llywelyn]

I agree. Assuming its not going to still be processing a request to train a pet when the refresh time comes, then it will be wonderful. Because its an AutoBuyer, the actual process of AutoBuying should override the other processes going on at that specific time.

Exactly. That's it's purpose, anything else is a bonus and shouldn't take priority. Or hinder the process of autobuying.

Also, Alias... I think you are over-emphasising the inactivity time of an ABer. It only waits a certain number of seconds before it starts refreshing the shop again. Depending on the timing you use. Another consideration should be threads. If Sock is adding some sort of multi-account or multi-thread function then that will reduce the inactivity time even further. People use ABers differently... depending on the shop(s) they go for. Some only use only the first few seconds after a minute, whereas others like myself refresh in multiple shops using 0-20+ seconds of a minute.

So in a matter of seconds you're asking it to stock and price several items, perhaps withdraw money from the till or bank, AND to train pets? It would have to process these requests inhumanly fast... which leads back to the risk factor.

Your theory about what "sends warning signals off" is all good and well, but it doesn't really justify some of the instances where I (and others I'm sure) have been frozen for using programs.

[sockopen]

Multi-threading allows me to do several things at once, in the program I could have it going to 10 pages at the exact same time for example, whereas every other AutoBuyer to date excluding 'Atmos' and 'fAB' have not been multi-threaded, and therefor can only do one thing at a time, load one page, wait for it to be done, then goto another page; which is not how I browse the internet either, I have 5+ tabs open at all times loading several pages simultaneously, especially if I'm researching something, "Open in new tab" 20 times, 20 pages loading at once.

The AutoBuyer will allow you to just use one account, and only use the AutoBuyer of course, I might even have a drop-down menu where you can select either Complex or Simple User Modes or something. lol.

On a 'side note': Currently I'm getting pages in around 140ms, I'm guessing the AutoBuyer will be capable of buying an item in around 300ms, which is 0.3 seconds. Don't quote me on that yet though, I haven't done any of the imaging yet, but I was capable of doing that in 0ms in Visual Basic 6.0. =P

[llywelyn]

Multi-threading allows me to do several things at once, in the program I could have it going to 10 pages at the exact same time for example, whereas every other AutoBuyer to date excluding 'Atmos' and 'fAB' have not been multi-threaded, and therefor can only do one thing at a time, load one page, wait for it to be done, then goto another page; which is not how I browse the internet either, I have 5+ tabs open at all times loading several pages simultaneously, especially if I'm researching something, "Open in new tab" 20 times, 20 pages loading at once.

The AutoBuyer will allow you to just use one account, and only use the AutoBuyer of course, I might even have a drop-down menu where you can select either Complex or Simple User Modes or something. lol.

On a 'side not': Currently I'm getting pages in around 140ms, I'm guessing the AutoBuyer will be capable of buying an item in around 300ms, which is 0.3 seconds. Don't quote me on that yet though, I haven't done any of the imaging yet, but I was capable of doing that in 0ms in Visual Basic 6.0. =P

Sounds great.

[japser_be]

yeah sounds really great sockopen

you already got a name for it ?

[Kyle]

On a 'side note': Currently I'm getting pages in around 140ms, I'm guessing the AutoBuyer will be capable of buying an item in around 300ms, which is 0.3 seconds. Don't quote me on that yet though, I haven't done any of the imaging yet, but I was capable of doing that in 0ms in Visual Basic 6.0. =P

Thats depending on the individual's connection, though. That would be hella fast though! Looking forward to this Sock. You should put a countdown until the release date in your sig

[Mystical]

whereas every other AutoBuyer to date excluding 'Atmos' and 'fAB'

Cough... 2 years ago I wrote blerp in c++ and it was multithreaded.

Don't have the source to it anymore but i'm writing it in c++ agian, currently

[sockopen]

yeah sounds really great sockopen

you already got a name for it ?

Well my original name for it was stAB (sockopen's trusty AutoBuyer), but I've been considering jAB (java AutoBuyer). Jab and Stab are pretty good code names for it, not sure of it's name yet though, I'm up for suggestions. =P

A wrapper with GZIP only takes mili seconds to grab a page, and string parsing takes past .00, it's not like it's a long process.

Yea I've got the GZip down, fastest time was 108ms to grab a page, but it's taken as long as 400ms which is not good, but that means the slowest it could grab the item would still be under one second, which isn't too bad either.

[k0oLg1]

You didnt detect my sarcasm? Next time I will go like this [sarcasm] Blah Blah whatever I feel like saying [/sarcasm]

Were you being sarcastic there as well ??

[Mystical]

it should have an option to auto-remove items that don't meet a set profit range... just incase an item drops dramitically over night or some bs

[supatyson]

Multi-threading sounds awesome, I really should learn how to program.

[Nenofyn]

Well my original name for it was stAB (sockopen's trusty AutoBuyer), but I've been considering jAB (java AutoBuyer). Jab and Stab are pretty good code names for it, not sure of it's name yet though, I'm up for suggestions. =P

If you want my opinion I would go for stab... that sounds better then jab to me xD but maybe you or someone else will come up with another name again. But I like stAB the most

[Ives]

Whether this is going to be barebones or huge, good luck with it.

For multi accounts all you have to do is run multiple copies of the prog

That uses a lot more memory. Not to mention, with an RS alert system, it could grab things FASTER if you have three threads running.

[hitman666]

Don't waste your time with a fast Ab... Neo is now freezing based on buy speeds. I am getting frozen daily, and Most of the time I do not even last long enough to get restock banned. My times are .2-.6 seconds...

[StefanKai]

Neo's really cracking down on ab's lately

[Hawk]

Neo's really cracking down on ab's lately

I thought they always were cracking down

Like that stupid image you have to click, or the thing that required the OCR.

['B']

Multi-threading allows me to do several things at once, in the program I could have it going to 10 pages at the exact same time for example, whereas every other AutoBuyer to date excluding 'Atmos' and 'fAB' have not been multi-threaded, and therefor can only do one thing at a time, load one page, wait for it to be done, then goto another page; which is not how I browse the internet either, I have 5+ tabs open at all times loading several pages simultaneously, especially if I'm researching something, "Open in new tab" 20 times, 20 pages loading at once.

Multithreading is not the perfect solution. You have to take into consideration the effects of having threads. Of course no one will have as many processors as they do threads. This is why there are performance implications of having too many threads. First the operating system has to keep track of threads deciding when one thread will stop and then another will get to run. Then the operating system has to keep track of thread priorities. Another performance implication is that when a CPU switches from one thread to another it has to save the context of that thread and load up the context of the new thread AKA context switching.