Innerspace and you.... Anyone still developing?

[Nokia5800]

hey @tdrake

You said you be willing to share some of your old bot code as long as it wasnt some commercial bot, and thats exactly what Im doing. I just want a private bot worth using for my main account. Since I work alot I like to let it play while im gone But as of now with my bots limited resources/cycle it wont run longer then 30 mins without running into some type of issue.

It would be a HUGE help to me, if you were to share this code with me. Rest assured it would never be release, nor be sold what so ever. I intend to keep blizz away from all the methods of botting as long as possible.


(tryed to pm you but it was lagging otu or something. Let me know if its cool, we can talk on skype or something)

[demisehi]

/agree on the commerical bot problem, but payment for a private version is just that. private. Non-distributable. Sometimes, people just don't get that.

[klufas]

Nokia what is your aim/msn or skype? I'd love to talk to you asap!

[BoogieManTM]

Thats my only stipulation. Dont mind sharing code but I prefer not to give away my work for some stupid commercial bot.

Regardless Boogieman, ppather was a resource hog.

Bot I used was programmed as a FSM and had everything incorporated into it and didnt use 1/10 the resources glider did with ppather including real time questing(not the half ass questing system ppather had to use since glider wasnt able to get quest log info/kill counts, etc.

Sure glider started using a little more resources the last few releases but with ppather running, I had a tough time running 2 instances before movement started going haywire. Simple point mesh system similar to what bbot then later openbot used tends to be less process intensive. Used the same approach as well in my bot and I could run 5 instances if i wanted with crap 128mb vid card , 1.63ghz cpu(1gig ram) with no problems.

Oh definitely, but that was my point. the whole thing is inefficient, pathing was only half to blame. ppather's FSM was on another level of inefficiency.

Even a (good) full mesh, with a normal A* algo if implemented correctly will run fine on pretty much any system

[tdrake]

I'll set up a msn and post it here later today. Just keep in mind it will do nothing unless you have a working isxwow not to mention some anti-warden like isxwarden.

Only class coded for it is hunter and druid. Wouldnt take long to add a different class. Bot was done pre lich king expansion so any changes for classes would have to be updated as well(skills that changed, etc)

Too bad Lax couldnt figure out how to keep IS safe. Lost more money having to buy accounts after getting numerous suspensions and bans then was worth. Wouldnt touch IS again personally with a ten foot pole even if Lax released a new isxwarden.

[Apoc]

I'll set up a msn and post it here later today. Just keep in mind it will do nothing unless you have a working isxwow not to mention some anti-warden like isxwarden.

Only class coded for it is hunter and druid. Wouldnt take long to add a different class. Bot was done pre lich king expansion so any changes for classes would have to be updated as well(skills that changed, etc)

Too bad Lax couldnt figure out how to keep IS safe. Lost more money having to buy accounts after getting numerous suspensions and bans then was worth. Wouldnt touch IS again personally with a ten foot pole even if Lax released a new isxwarden.

It wasn't an issue with keeping it safe. (Lax already had ISXWarden fixed, and ready to go) He took it down due to legal reasons. Obviously, he didn't want to end up like Glider, and pay millions of dollars to battle Blizzard for something he does in his free time.

[tdrake]

No offense Apoc but how many times did Lax say isxwarden was fixed only to have everyone suspended or banned? Then he started up with the orange alert, red alert crap after users kept getting suspended over and over or banned after his "fixes". Used IS for almost 2 yrs and he had a good run for 7-8 months but when there was a detection, it took him awhile to actually fix the hole.

Toward the end Lax had no idea what was going on.

[KuRIoS]

No offense Apoc but how many times did Lax say isxwarden was fixed only to have everyone suspended or banned? Then he started up with the orange alert, red alert crap after users kept getting suspended over and over or banned after his "fixes". Used IS for almost 2 yrs and he had a good run for 7-8 months but when there was a detection, it took him awhile to actually fix the hole.

Toward the end Lax had no idea what was going on.

Yet Lax was the one that helped merc out when they had problems? i only had accounts banned with innerspace from 1 wave and I used it for , well since bytebot was an option...

[tdrake]

Far as i know, Lax helped merc with the tripwire setup.

Far as IS ban/suspension waves, I can find pages and pages for probably 8-10 isxwarden releases where people got banned or suspensions from the isxwow forums if theyre still around.

Either way, its a moot point now lol. I dont care one way or another.

When IS worked and was safe, it had alot more flexibility then glider ever had. Its the only reason i stuck around after all the bans/suspensions before I finally gave up on Lax/IS.

[Cypher]

Far as i know, Lax helped merc with the tripwire setup.

Far as IS ban/suspension waves, I can find pages and pages for probably 8-10 isxwarden releases where people got banned or suspensions from the isxwow forums if theyre still around.

Either way, its a moot point now lol. I dont care one way or another.

When IS worked and was safe, it had alot more flexibility then glider ever had. Its the only reason i stuck around after all the bans/suspensions before I finally gave up on Lax/IS.

You're wrong.

Not sure about the relationship between ISXWarden and Tripwire, but I know for a fact that Glider had a banwave that they couldn't work out the cause of, and they paid Lax USD $18,000 to tell them how they were detected.

Most of the bans you're referring to were also from a single batch of waves from the same detection. After the first wave though, and up until the point he knew he found the actual problem, he repeatedly said "the risk level is much higher on these builds, do not use them if you value your accounts" etc etc. If you got banned in the waves after the initial one that's your own fault.

And anyway, ISXWarden was a LOT more powerful than Tripwire, you can't really compare them.

[tdrake]

Never compared isxwarden to tripwire did I. Thatd be like comparing apples to oranges.


There were multiple builds of isxwarden the last few months before isxwarden died causing suspensions and or bans. As I stated before, Lax had no clue what was happening and was just putting out releases fixing potential holes in it. Year before that, there was another fiasco with IS and it took a month of releases before Lax finally fixed that.

Just saying even the most knowledgeable people of warden have had a hard time fixing holes over the years. If its public and blizzard has access to it, they'll eventually find something.

[GliderPro]

and gliderpro if your interested in working on a bot with me, with pure scripting or making a innerspace lua controler let me know. PM me or something mate

I hang out in the #isxeve channel most days. You can catch me there if you want to discuss your project.

[undrgrnd59]

Man I wish there was an ISXWarden again. I had no idea how much work had gone in to ISXWoW. It made everything so insanely easy, a great piece of programming, doing things without it sucks, plain and simple.

[ramey]

Never compared isxwarden to tripwire did I. Thatd be like comparing apples to oranges.


There were multiple builds of isxwarden the last few months before isxwarden died causing suspensions and or bans. As I stated before, Lax had no clue what was happening and was just putting out releases fixing potential holes in it. Year before that, there was another fiasco with IS and it took a month of releases before Lax finally fixed that.

Just saying even the most knowledgeable people of warden have had a hard time fixing holes over the years. If its public and blizzard has access to it, they'll eventually find something.

Lax obviously did know what was happening, considering he did keep IS safe for quite a while.

Remember, Lax didn't even have to supply ISXWarden, he was never obliged to do anything relating to WoW, and I feel like you're being ungrateful for somebody elses hard work which they didn't have to do. It's like comparing apples to oranges. Glider tripwire was a feature you were paying for if you had Glider, while ISXWarden was not.

I don't get why you're saying all this now, considering it was ended due to legal reasons, quite some time ago. It is obvious that there are private versions of ISXWarden, which would not be very hard to do, considering it would be kept private instead of being public. Pretty pointless to have an argument like this if you ask me.

[clanstyles]

Ramey, IS was never detected. ISXWarden / ISXWoW were what was detected.