Requesting an act3 package with multiple different X Y Z cords

[jason805]

To solve the banwave, I think developers need to focus on profiles that load random profile packs (like CIGARCS).

Say for instance

/Act3_CompliationCydaea_1
/Act3_CompliationCydaea_2
/Act3_CompliationCydaea_3
/Act3_CompliationCydaea_4
/Act3_CompliationCydaea_5

each directory would have XML's that would have different x y z cord's in each different file. DB would randomly select one of the five. That would solve the issue with blizz seeing the same exact cords loaded thousands of times... I knew this ban wave was coming, but didnt know when they would execute

 

[Polyester]

To solve the banwave, I think developers need to focus on profiles that load random profile packs (like CIGARCS).

Say for instance

/Act3_CompliationCydaea_1
/Act3_CompliationCydaea_2
/Act3_CompliationCydaea_3
/Act3_CompliationCydaea_4
/Act3_CompliationCydaea_5

each directory would have XML's that would have different x y z cord's in each different file. DB would randomly select one of the five. That would solve the issue with blizz seeing the same exact cords loaded thousands of times... I knew this ban wave was coming, but didnt know when they would execute

ugh

 

[StefanKFG]

Which "banwave" do you mean oO?

 

[satan2004]

gotta agree with what hes saying for every part in act 3 there should be sub sections with atleast 4 different profiles with different waypoints

More work but alot safer

 

[jason805]

gotta agree with what hes saying for every part in act 3 there should be sub sections with atleast 4 different profiles with different waypoints

More work but alot safer

not that much work maybe 2 hours tops. I was changing out the last digit ie (108.1119) instead of (109.1119) tested out fine changing a minor digit

I'd do it--But I would be stuck with "randomly" selecting a package




Which "banwave" do you mean oO?

Starting this months ban, the first week blizz started. Keep it to the min

 

[humble]

That's a great idea

 

[Gingerbread]

noone knows how or why Blizzard ban people.

We don't know what they monitor, how they flag accounts, anything like that at all.

We are planning to add more variation to our profiles with ABCD etc versions but it's far down the priority list and tbh I don't think it'lll make a lot of difference.

If you use a bot and break Blizzards rules eventually you will get your account banned. Some people last a few hours some people run for months. Most of our profiles use pathPrecision which nudges the exact co-ordinates a bot runs to on a given map by a couple of points already. Our multi version profiles run in completely different directions. e.g. in Act 2 Gardettos wrote the A versions mostly which I cleaned up later. I wrote the B versions. If the A version takes a clockwise route around an area my B version goes anticlockwise.

Some of our profiles use unsafeRandomDistance as well as pathPrecision which nudges MoveTo points around randomly everytime they are used by a few pixels. Also given the random terrain and monster spawns in the game it's very rare that you approach a MoveTo point from exactly the same direction anyway because of the way the bot identifies mobs to kill/chests to open/things to break along its route.