Bot missing most chests

[Atlas]

Hey guys, I started botting the other day using FragMam's Core+FOS 1.4.3, with the latest GilesTrinity, and Rads profile manager. The bot runs flawlessly, except that it misses about 80% of the chests, demonic boxes, as well as those infernal cocoons (I think thats what they are :s). Any thoughts on this?

Thanks,
Atlas

 

[FrenchBot]

Chests suck anyways

 

[Atlas]

Ehh not really. I usually get 750-1000 gold from each one. Sometimes as much as 1500.

 

[hairymexican]

Ehh not really. I usually get 750-1000 gold from each one. Sometimes as much as 1500.

Agreed, and it misses alot of bones and stuff in act 3 inferno.. and i mean ALOT!

 

[FrenchBot]

1500 gold woohoo !
Seriously have you seen the time it takes to open a chest ? No way getting an occasional 1.5k for it is worth the trouble

 

[Atlas]

1500x6 per game x 15 games per hour=135k/hour. Even if its only 2/3 that its still more than worth getting the chests.

 

[Moley]

6x 2secs and a chance for stucks x 15games per hour = no thanks, I comment out all of chest priorities except for res chests.

Also 15 games an hour?

 

[lilobat]

Chests suck anyways

Chest does give good income, especially Big chest in cave. Trinity should have highest priority to repleasant chest, not treat it as normal chest.

And it missed a lot of chest is truth.

 

[Moley]

        // Resplendent chest SNO list
        private static readonly HashSet<int> hashSNOContainerResplendant = new HashSet<int> { 
		62873, 95011, 81424, 108230, 111808, 111809, 109264,
         };
        // Chests/average-level containers that deserve a bit of extra radius (ie - they are more worthwhile to loot than "random" misc/junk containers)
        private static readonly HashSet<int> hashSNOContainerWhitelist = new HashSet<int> { 
            62859, 62865, 62872, 78790, 79016, 94708, 96522, 130170, 108122, 111870, 111947, 213447, 213446, 179865, 109264, 212491, 210422, 
         };

Trinity already does RES chests, if you find a regular or res chest and it doesn't open, pause, dump sno for the chest and add to the list depending on which type it is. You will have crank up your container open range to the max or so, this may cause stucks, ymmv

 

[lilobat]

Should have 2 different range for the normal and res chest.

 

[Moley]

Should have 2 different range for the normal and res chest.

already in trinity, you guys might try opening up the .cs and taking a look