Lodis
Beta Tester-
Content Count
10 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout Lodis
-
Rank
Bronze V
-
Ongoing bug since the start of Invasion: Bot fails to chicken on most Invasion bosses. Works fine on the set unique monsters I tried it on (Perpetus, Kuduku, etc.)
-
Doesn't work for me either. Failed to chicken on "Cintiq, the Inescapable" amongst many others. Does the bot not recognize some unique monsters or something?
-
I've tested it on Perpetus (works fine), Kuduku, the False God (works fine) and various invasion bosses. Like I said, it works for some of them (off the top of my head, it works for the black spider, Shivershell and a few others) and fails to chicken on the others. The bot does get its cursor on them and attack them so clearly it's aware of it. Maybe it fails to read the full name properly, who knows. Edit: There's also the problem with the interface I mentionned a few posts above (it only lets you input up to 512 characters.. makes for short lists)
-
Right. I make sure im way overleveled for the zone and still set the chicken treshold pretty high (I think it's at 50% right now).
-
Ok so despite that, it seems to work for certain uniques and not for others. My bot chickens fine when it encounters the black spider, for exemple. It fails to chicken when it encounters Ossecati, Guardian of the Mound, the totem one, etc. Makes botting in Invasion risky as hell.
-
There seems to be a bug with the interface where, if the length of the parameter value in the config.ini file is too big (492 characters according to my tests), it ignores/overwrites it with blank data. It does seem to be fucking up based on the number of characters rather than the number of elements in the list. In fact, the parameter string begins with sight_chicken_names= which is 20 characters long. It adds up to maximum of 512 characters (2x256, now thats a familiar number). TLDR: I suppose the interface parses the string with 8bit pointers and the thing goes out of bounds or something. For now, I just go with a few select invasion bosses and exiles rather than with the entire list there so I dont exceed the character limit.
-
I dont have this bot config anymore so I cant copy-paste anything but it was something like this: Left-click Bound to move-only Priority: 10 Range: 0 - 100 Cooldown: 0 Right-click Bound to Flammability (or Ice Nova or Shock Nova, up to you) Priority: 15 Range: 0-300 Cooldown: 5s Q Bound to Righteous-Fire Priority: 20 Range 0-1000 Cooldown: 30s Of the top of my head, I think my setup was similar to this but surely you could improve it. See for yourself, maybe you can make it work better than I did. Edit: You can't "disable" RF. You could spam the skill all-day and it wouldn't matter. You need a dispel burning flask. Oh and you might want to use Ruby Flasks instead of Life Flasks (it brings your fire resist to 99%. Your HP regens much faster this way.).. but then again, the bot does not work with flasks that arent health/mana atm so you're gonna have to go with a "blind" method with AHK or something.
-
I replied to your post in the other topic: https://exiled-bot.net/community/index.php/topic/2285-rf-build-working/?p=14869 As for casting RF, I tried 2 methods (both worked): 1 - Using AHK to image-search for an aura (to know when you're in a zone - NOT in town) and the RF debuff (to know whether it's on you or not), pause the bot, cast RF, un-pause the bot. 2 - Setting the bot to use it as a high-priority skill with a high cooldown (30s or something). I've used this build myself to farm Lunaris and it's really fast because you can just plow through packs as they die and burn. Used on a bot, however, is a bit slower because it waits for the target to burn and die before moving on to the next target. Edit: Do not use CWDT to cast RF as you need the gem-slots for IIQ/IIR/etc. Unless your RF dps is low, you wouldn't even have time to cull on white mobs. Edit #2: I think if there was a way to configure the bot to IGNORE all white mobs (that is, just explore the map and attack rare/unique monsters), this build would be much, much, much better. It would run through everything and be much faster/efficient.
-
I tried it. It does have good DPS and MF but desyncs make it hardly efficient. I set-up my skills so it would just walk to the mob and occasionally curse (or shock/ice nova for EE) but since you run and collide into mobs a lot, you tend to desync more. When the bot then targets a desync'd mob and follows it around (without actually dealing any damage to it), you get killed by whatever is range-hitting you. I suppose you could have a AHK macro that types /oos or something but I dont think that would be too good.. Maybe you could take off the conc effect gem and increase the attack range on the bot to reduce the number of collisions, I havent tried it. At this point, I have as much IIR/IIQ on my double strike duelist with much less hassle. Good luck
-
I went back to v0.15d as well, the account im using at the moment has 20+ tabs and the bot cycles through all of them before stashing anything.