Jump to content

gvd0x1

Beta Tester
  • Content Count

    54
  • Joined

  • Last visited

Posts posted by gvd0x1


  1. yeah, looks like it thinks area is done due to "exploration failing"?

     

    2017-01-01 00:32:59 [info] -> MAP OPENED !!
    2017-01-01 00:33:00 [info] -> Looking for gems to level up using new image detection
    2017-01-01 00:33:00 [info] -> Moving to position(1451.086914, 1853.260864). State Priority: 4
    2017-01-01 00:33:00 [info] -> Moving to position(1451.086914, 1853.260864). State Priority: 4
    2017-01-01 00:33:01 [info] -> Area switched from Enlightened Hideout to Stagnant Canal
    2017-01-01 00:33:03 [info] -> Sacrifice area reinitialized!!
    2017-01-01 00:33:03 [info] -> Casting aura
    2017-01-01 00:33:06 [info] -> Looking for gems to level up using new image detection
    2017-01-01 00:33:06 [info] -> Casting aura
    2017-01-01 00:33:09 [info] -> Idling...
    2017-01-01 00:33:09 [info] -> Exploring to position(4288.640625, 2712.431152, -96.817459). State Priority: 2
    2017-01-01 00:33:09 [info] -> Quicksilver flask taken
    2017-01-01 00:33:09 [info] -> Exploring to position(4288.640625, 2712.431152, -96.817459). State Priority: 2
    2017-01-01 00:33:09 [info] -> Exploring to position(4300.382324, 2731.739258, -96.817459). State Priority: 2
    2017-01-01 00:33:09 [info] -> Exploring to position(4304.728516, 2760.646973, -96.817459). State Priority: 2
    2017-01-01 00:33:09 [info] -> Exploring to position(4361.274414, 2791.541260, -96.817459). State Priority: 2
    2017-01-01 00:33:09 [info] -> Exploring to position(4383.750000, 2812.827393, -96.817459). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4400.638672, 2859.962158, -96.817459). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4389.726563, 2883.840820, -96.817459). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4401.135742, 2915.464355, -96.817459). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4394.168457, 2968.869385, -96.817459). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4388.846191, 3040.029541, -106.660721). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4393.355469, 3076.382324, -124.212372). State Priority: 2
    2017-01-01 00:33:10 [info] -> Already reached destination from current path to follow.
    2017-01-01 00:33:10 [info] -> Idling...
    2017-01-01 00:33:10 [info] -> Exploring to position(4528.074219, 3231.260010, -236.189194). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4657.959961, 3299.297119, -277.396301). State Priority: 2
    2017-01-01 00:33:10 [info] -> Exploring to position(4657.959961, 3299.297119, -298.461487). State Priority: 2
    2017-01-01 00:33:11 [info] -> Exploring to position(4732.697754, 3354.218750, -319.007996). State Priority: 2
    2017-01-01 00:33:11 [info] -> Exploring to position(4898.540527, 3397.398438, -353.895813). State Priority: 2
    2017-01-01 00:33:11 [info] -> Looking for gems to level up using new image detection
    2017-01-01 00:33:11 [info] -> Exploring to position(4952.364746, 3427.924316, -348.307312). State Priority: 2
    2017-01-01 00:33:11 [info] -> Exploring to position(5011.796875, 3463.999023, -346.912048). State Priority: 2
    2017-01-01 00:33:11 [info] -> Exploring to position(5060.580566, 3496.280273, -346.824219). State Priority: 2
    2017-01-01 00:33:11 [info] -> Exploring to position(5122.039551, 3528.605225, -346.818481). State Priority: 2
    2017-01-01 00:33:11 [info] -> Exploring to position(5152.221680, 3544.544678, -346.817810). State Priority: 2
    2017-01-01 00:33:11 [info] -> Exploring to position(5174.711914, 3585.603760, -346.817474). State Priority: 2
    2017-01-01 00:33:11 [info] -> Already reached destination from current path to follow.
    2017-01-01 00:33:11 [info] -> Idling...
    2017-01-01 00:33:11 [info] -> Exploring to position(5103.873535, 3241.667480, -346.817444). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5090.539551, 3233.011719, -346.817444). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5107.385254, 3241.125000, -346.817444). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5090.485840, 3239.245850, -347.005798). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5094.745605, 3202.065430, -346.848999). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5095.289063, 3169.109375, -350.481201). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5094.171387, 3135.766357, -354.288757). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5093.262695, 3075.769531, -353.296875). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5088.883789, 3007.909424, -347.793152). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5092.299805, 2994.196777, -346.975647). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5104.188965, 2961.100586, -346.840332). State Priority: 2
    2017-01-01 00:33:12 [info] -> Exploring to position(5098.755371, 2899.534180, -353.579712). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5095.808594, 2848.739014, -354.460754). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5091.786621, 2800.589111, -347.896729). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5088.239258, 2736.672363, -349.574219). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5092.299805, 2668.068115, -353.870911). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5092.299805, 2613.712402, -354.529663). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5089.478027, 2564.063477, -348.033936). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5097.604492, 2502.575195, -346.988525). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5092.345215, 2439.771973, -352.380005). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5092.345215, 2380.232910, -354.386841). State Priority: 2
    2017-01-01 00:33:13 [info] -> Exploring to position(5099.312012, 2326.307861, -353.937378). State Priority: 2
    2017-01-01 00:33:14 [info] -> Exploring to position(5096.690918, 2280.783203, -347.422516). State Priority: 2
    2017-01-01 00:33:14 [info] -> Exploring to position(5090.833984, 2226.149902, -346.908295). State Priority: 2
    2017-01-01 00:33:14 [info] -> Exploring to position(5097.940918, 2176.831543, -352.040314). State Priority: 2
    2017-01-01 00:33:14 [info] -> Exploring to position(5090.517578, 2130.626953, -354.240662). State Priority: 2
    2017-01-01 00:33:14 [info] -> Exploring to position(5095.803711, 2082.301758, -353.684692). State Priority: 2
    2017-01-01 00:33:14 [info] -> Exploring to position(5093.159668, 2034.612427, -347.783142). State Priority: 2
    2017-01-01 00:33:14 [info] -> Exploring to position(5094.354004, 1991.821533, -346.448090). State Priority: 2
    2017-01-01 00:33:14 [info] -> Already reached destination from current path to follow.
    2017-01-01 00:33:14 [info] -> Idling...
    2017-01-01 00:33:14 [info] -> Idling...
    2017-01-01 00:33:14 [info] -> Exploration failing, reseting current area to avoid bot being stucked..
    2017-01-01 00:33:14 [info] -> Distance computed for tp use: 122.196564
    2017-01-01 00:33:14 [info] -> Distance computed for tp use: 122.196564
    2017-01-01 00:33:14 [info] -> Area finished!!
    2017-01-01 00:33:14 [info] -> Creating tp...
    2017-01-01 00:33:16 [info] -> Mission finished, considering current area as cleared.
    2017-01-01 00:33:16 [info] -> Current complex map explored !!
    2017-01-01 00:33:16 [info] -> Exploration failing, reseting current area to avoid bot being stucked..
    2017-01-01 00:33:16 [info] -> Looking for gems to level up using new image detection
    2017-01-01 00:33:16 [info] -> Distance computed for tp use: 0.000000
    2017-01-01 00:33:16 [info] -> Area finished!!
    2017-01-01 00:33:16 [info] -> Moving to position(5135.869629, 1994.565186). State Priority: 14
    2017-01-01 00:33:17 [info] -> Mission finished, considering current area as cleared.
    2017-01-01 00:33:17 [info] -> Current complex map explored !!
    2017-01-01 00:33:17 [info] -> Exploration failing, reseting current area to avoid bot being stucked..
    2017-01-01 00:33:17 [info] -> Distance computed for tp use: 0.000000
    2017-01-01 00:33:17 [info] -> Area finished!!
    2017-01-01 00:33:17 [info] -> Moving to position(5135.869629, 1994.565186). State Priority: 14
    2017-01-01 00:33:18 [info] -> Area switched from Stagnant Canal to Enlightened Hideout

  2. it used to work.

     

    Not it enters and immediately leaves, grabs another sacrifice fragment and starts another area ad infinitum.

     

    map file only has

     

    [Type] == "Sacrifice at Dusk" # [RunMap] == "true"
    [Type] == "Sacrifice at Dawn" # [RunMap] == "true"
    [Type] == "Sacrifice at Noon" # [RunMap] == "true"
    // [Type] == "Sacrifice at Midnight" # [RunMap] == "true"

     

    this is with the latest version 66l


  3.  

    Why not just use the existing lines in the pickit to pickup jewelry?  It's there for a reason.

     

    // To pick up UnID items, uncomment the lines below.  Please note that the more lines you uncomment, the more stash space will be needed, especially if stashing chests

     
    // Jewelry
    // [Category] == "Belt" && [Rarity] == "Rare" && [itemLevel] >= "60" # [stashItem] == "true"
    // [Category] == "Ring" && [Rarity] == "Rare" && [itemLevel] >= "60" # [stashItem] == "true"
    // [Category] == "Amulet" && [Rarity] == "Rare" && [itemLevel] >= "60" # [stashItem] == "true"

     

     

    I wish it worked for me, there's something in the pickit that even after getting rid of belt/jewelry section as mentioned above, it would still identify stuff. I solved by being explicit

     

    [Category] == "Belt" && [Rarity] == "Rare" && [stashItem] == "true"
    [Category] == "Ring" && [Rarity] == "Rare" && [stashItem] == "true"
    [Category] == "Amulet" && [Rarity] == "Rare" && [stashItem] == "true"
    [Category] == "Map" && [stashItem] == "true"
     
    [Category] == "Helm" && [Rarity] == "Rare" # [sellItem] == "true"
    [Category] == "Chest" && [Rarity] == "Rare" # [sellItem] == "true"
    [Category] == "Shield" && [Rarity] == "Rare" # [sellItem] == "true"
    [Category] == "Weapon" && [Rarity] == "Rare" # [sellItem] == "true"
    [Category] == "Gloves" && [Rarity] == "Rare" # [sellItem] == "true"
    [Category] == "Boots" && [Rarity] == "Rare" # [sellItem] == "true"
    [Category] == "Quiver" && [Rarity] == "Rare" # [sellItem] == "true"
     
    That works after long time of trying to get things function as you'd think they do. If it works for you just doing the 3 lines above, then I don't know what it means. Thanks for the reply.

  4. remove this from ur default.ipd located in ur pickit folder:

     

    now he wont ID them anymore. btw he only sells them because theyr crap. he would keep the good ones..

     

     

     

    //////////////////////////////////////////////

    //                                          //  

    //                B e l t s                 //

    //                                          //

    //////////////////////////////////////////////

     

    //tri res  hp

    [Category] == "Belt" && [Rarity] == "Rare" # ([base_maximum_life] >= "60" || [base_maximum_energy_shield] >= "38") && [TotalResistances] >= "90" && [stashItem] == "true"

    //tri res hp Weapon Elemental Dmg

    [Category] == "Belt" && [Rarity] == "Rare" # ([base_maximum_life] >= "50" ||[base_maximum_energy_shield] >= "32") && [TotalResistances] >= "60" && [weapon_elemental_damage_+%] >= "25" && [stashItem] == "true"

    //high tri-res (incl.chaos-res)

    [Category] == "Belt" && [Rarity] == "Rare" # ([base_cold_damage_resistance_%] >= "30" && [base_fire_damage_resistance_%] >= "30") || ([base_cold_damage_resistance_%] >= "30" && [base_lightning_damage_resistance_%] >= "30") || ([base_fire_damage_resistance_%] >= "30" && [base_lightning_damage_resistance_%] >= "30") && [base_chaos_damage_resistance_%] >= "21" && [stashItem] == "true"

    //HP ARMOR Weapon Elemental Dmg

    [Category] == "Belt" && [Rarity] == "Rare" # [physical_damage_reduction_rating] >= "350" && [weapon_elemental_damage_+%] >= "25" && [base_maximum_life] >= "60" && [stashItem] == "true"

     

    /////////////////////////////////////////////

    //                                          //

    //                R i n g s                 //

    //                                          //

    //////////////////////////////////////////////

    //tri res hp//

    [Category] == "Ring" && [Rarity] == "Rare" # [TotalResistances] >= "100" && [base_maximum_life] >= "60" && [stashItem] == "true"

    //tri res hp attack speed//

    [Category] == "Ring" && [Rarity] == "Rare" # ([attack_speed_+%] >= "5" || [cast_speed_+%] >= "5") && [base_maximum_life] >= "60" && [TotalResistances] >= "60" && [stashItem] == "true"

    //tri res hp

    [Category] == "Ring" && [Rarity] == "Rare" # ([mana_leech_from_physical_damage_permyriad] >= "2" || [life_leech_from_physical_damage_permyriad] >= "2") && [TotalResistances] >= "60" && [base_maximum_life] >= "50" && [stashItem] == "true"

     

    //tri res hp WED

    [Category] == "Ring" && [Rarity] == "Rare" # [TotalResistances] >= "60" && [weapon_elemental_damage_+%] >= "25" && [base_maximum_life] >= "60" && [stashItem] == "true"

    //Dual Leech + HP

    [Category] == "Ring" && [Rarity] == "Rare" # [life_leech_from_physical_damage_permyriad] == "2" && [mana_leech_from_physical_damage_permyriad] == "2" && [base_maximum_life] >= "50" && [stashItem] == "true"

    // WED + Attack Speed / Cast Speed

    [Category] == "Ring" && [Rarity] == "Rare" # ([attack_speed_+%] >= "5" || [cast_speed_+%] >= "5") && [base_maximum_life] >= "60" && [TotalResistances] >= "60" && [stashItem] == "true"

    // Tri Ele Dmg

    [Category] == "Ring" && [Rarity] == "Rare" # [local_maximum_added_cold_damage] >= "24" && [local_maximum_added_fire_damage] >= "27" && [local_maximum_added_lightning_damage] >= "40" && [stashItem] == "true"

    //crit res hp

    [Category] == "Ring" && [Rarity] == "Rare" # [base_critical_strike_multiplier_+] >= "50" && [base_maximum_life] >= "40" && [critical_strike_chance_+%] >= "30" && [TotalResistances] >= "40" && [stashItem] == "true"

    //tri res hp

    [Category] == "Ring" && [Rarity] == "Rare" # [TotalResistances] >= "40" && [base_item_found_rarity_+%] >= "25" && [base_maximum_life] >= "50" && [stashItem] == "true"

    //tri res hp iir Rings

    [Category] == "Ring" && [Rarity] == "Rare" # [TotalResistances] >= "60" && [base_item_found_rarity_+%] >= "20" && [base_maximum_life] >= "60" && [stashItem] == "true"

    [Category] == "Ring" && [Rarity] == "Rare" # [base_item_found_rarity_+%] >= "25" && [base_maximum_life] >= "60" && [stashItem] == "true"

    [Category] == "Ring" && [Rarity] == "Rare" # [base_item_found_quantity_+%] >= "10" && [base_item_found_rarity_+%] >= "20" && [stashItem] == "true"

    [Category] == "Ring" && [Rarity] == "Rare" # [base_item_found_rarity_+%] >= "35" && [stashItem] == "true"

    // [Category] == "Ring" && [Rarity] == "Magic" # [base_maximum_life] >= "50" && [base_item_found_rarity_+%] >= "30" && [stashItem] == "true"

    // [Category] == "Ring" && [Rarity] == "Magic" # [base_item_found_quantity_+%] >= "10" && [base_item_found_rarity_+%] >= "20" && [stashItem] == "true"

    // [Category] == "Ring" && [Rarity] == "Magic" # [base_item_found_rarity_+%] >= "45" && [stashItem] == "true"

     

    //////////////////////////////////////////////

    //                                          //

    //              A m u l e t s               //

    //                                          //

    //////////////////////////////////////////////

     

    //crit hp

    [Category] == "Amulet" && [Rarity] == "Rare" # ([base_maximum_life] >= "55" || [base_maximum_energy_shield] >= "38" || [maximum_energy_shield_+%] >= "14") && [base_critical_strike_multiplier_+] >= "30" && [critical_strike_chance_+%] >= "30" && [stashItem] == "true"

    [Category] == "Amulet" && [Rarity] == "Rare" # ([base_maximum_life] >= "50" || [base_maximum_energy_shield] >= "38" || [maximum_energy_shield_+%] >= "14") && [base_item_found_rarity_+%] >= "30" && [stashItem] == "true"

    //Caster Crit cast and spelldamage

    [Category] == "Amulet" && [Rarity] == "Rare" # [base_critical_strike_multiplier_+] >= "50" && [critical_strike_chance_+%] >= "30" && [base_cast_speed_+%] >= "8" && [spell_damage_+%] >= "15" && [stashItem] == "true"

     

    //IIR Amulets

    [Category] == "Amulet" && [Rarity] == "Rare" # [base_maximum_life] >= "50" && [base_item_found_rarity_+%] >= "30" && [stashItem] == "true"

    [Category] == "Amulet" && [Rarity] == "Rare" # [base_item_found_rarity_+%] >= "45" && [stashItem] == "true"

    [Category] == "Amulet" && [Rarity] == "Rare" # [base_item_found_quantity_+%] >= "15" && [base_item_found_rarity_+%] >= "25" && [stashItem] == "true"

    // [Category] == "Amulet" && [Rarity] == "Magic" # [base_maximum_life] >= "50" && [base_item_found_rarity_+%] >= "30" && [stashItem] == "true"

    // [Category] == "Amulet" && [Rarity] == "Magic" # [base_item_found_rarity_+%] >= "40" && [stashItem] == "true"

    // [Category] == "Amulet" && [Rarity] == "Magic" # [base_item_found_quantity_+%] >= "15" && [base_item_found_rarity_+%] >= "25" && [stashItem] == "true"

     

    I already removed that section(i kept all rings/amys since the beginning of me using the bot, before chaos recipe was implemented). 

     

    1st try
     
    checkboxes in ui
     
    loot rare rings/amys unchecked
    loot rare items unchecked
     
    modified pickit profile which has nothing but this:
     
     
    // To pick up UnID items, uncomment the lines below.  Please note that the more lines you uncomment, the more stash space will be needed, especially if stashing chests
     
    // Jewelry
    [Category] == "Belt" && [Rarity] == "Rare" && [stashItem] == "true"
    [Category] == "Ring" && [Rarity] == "Rare" && [stashItem] == "true"
    [Category] == "Amulet" && [Rarity] == "Rare" && [stashItem] == "true"
     
    bot would not even pick up rares. Ok, so checkboxes are needed.
     
    Checked loot rare items. Same pickit as above, picks items, doesn't id anything,BUT
    sells rings and amulets(seems stash item is useless in the above pickit)
     
    checked "loot rare rings/amys", same pickit as above, bot still sells unid rings/amys.
     
    Finally, removed 
     
    && [stashItem] == "true"
     
    Success. Clearly the pickit parsing code isn't right, since the expression is equivalent, adding or removing 
     
    && [stashItem] == "true"
     
    should make no difference. Maybe someone out there can benefit from this knowledge. Thanks for the reply.

  5. How to make the bot not identify jewelry+belts? I have never been able to get this working.

     

    chaos recipe is off

    loot rare items is off

    lott amys/rings is off

     

    delete pretty much everything in pickit, at least there's nothing left related tio belts/rings/amulets except these lines

     

    [Category] == "Belt" && [Rarity] == "Rare" && [stashItem] == "true"
    [Category] == "Ring" && [Rarity] == "Rare" && [stashItem] == "true"
    [Category] == "Amulet" && [Rarity] == "Rare" && [stashItem] == "true"
    [Rarity] == "Rare" # [sellItem] == "true"
     
    Bot picks up rares and sells, stashes belts/rins/amys, BUT it identifies them before stashing. How to make it stash it unid??? There's no # in the expression, why bot is id'ing stuff?
     
    i haven't been able to make this work ever on any version of eb.

  6.  

    Each time my logs have this

     

    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12639.863281, 3125.591553). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12639.863281, 3125.591553). State Priority: 15
    2016-03-26 03:24:07 [info] -> Moving to position(12639.863281, 3125.591553). State Priority: 15
     
    It is a guaranteed ban. No human would do such precise back and forth at exact coordinates. Why can't bot actions be stored and made sure they are not repeated? Seems a very simple change. Plus, each action could have a fuzz factor if we do want bot to repeat it ie if it's a move, add some delta. Sometimes that's all that's needed to make bot work.

     

     

    also additionally for the above, attacking same thing , even with timeout set(i have 45 seconds), this is also a guaranteed ban

     

    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_wheel key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:32 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:33 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:33 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:33 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:33 [info] -> Attacking monster Undying Worker using mouse_right key at distance : 4.123106
    2016-03-26 03:22:33 [info] -> Restart state because no monster were killed for 45 s

  7. Each time my logs have this

     

    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12657.608398, 3125.000000). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12639.863281, 3125.591553). State Priority: 15
    2016-03-26 03:24:06 [info] -> Moving to position(12639.863281, 3125.591553). State Priority: 15
    2016-03-26 03:24:07 [info] -> Moving to position(12639.863281, 3125.591553). State Priority: 15
     
    It is a guaranteed ban. No human would do such precise back and forth at exact coordinates. Why can't bot actions be stored and made sure they are not repeated? Seems a very simple change. Plus, each action could have a fuzz factor if we do want bot to repeat it ie if it's a move, add some delta. Sometimes that's all that's needed to make bot work.

  8. I added it for testing, to see if I can force the bot to get rid of it. In my initial pickit I didn;t even have it, all I had were the lines for gems I wanted to be picked up. That worked great in earlier bot versions: bot picked those gems + gems that had my preset quality. Right now bot is picking up ALL gems and stashing them in stash tab and I can't figure out why.

     

    Are you saying that there is a difference between line not being present at all and line being present and commented out? I commented it out and the bot still grabs the gem(I did restart the bot completely). Something is clearly different with how pickit is interpreted from earlier versions. I did not try to remove quality threshold from the GUI.

    • Upvote 1

  9. I used my own pickit and it was working fine with earlier version. My settings were simple:

     

    1) only take >1% quality(set in gui, also verified in init that it is there)

    2) pick drop only gems, but do sell detonate mines gem

     

    Now bot with the same pickit stashes all gems. I purposely added detonate mines with a pickit having

     

    [Type] == "Detonate Mines" # [sellItem] == "true"

     

    And the bot still stashes it. Pickit section is super simple for gems and it is clearly not working.

     

    // For quality gem, use the setting Min Gem Quality from Pickit tab of GUI
     
    // White Skill Gem
     
    [Type] == "Portal" // Gem
    [Type] == "Detonate Mines" # [sellItem] == "true"
     
    //Red Support Gem Skill
     
    [Type] == "Empower" // Gem
    [Type] == "Increased Duration" // Gem
     
    // Green Support Gem Skill
     
    [Type] == "Enhance" // Gem
     
    // Blue Support Gem Skill
     
    [Type] == "Added Chaos Damage" // Gem
    [Type] == "Enlighten" // Gem
     
    // Currently no Vaal gems with quality have been found
     
    [Type] == "Vaal Glacial Hammer" // Gem
     
     
    I feel like certain parts of the code could be open sourced ie pickit code, since it seems to be bug ridden and other people could contribute fixes thru git etc Keep the core secret code, but pickit code is not something anyone would benefit from, but more people couple help out with that.
    • Upvote 1
×
×
  • Create New...