heisenburger
Beta Tester-
Content Count
202 -
Joined
-
Last visited
Everything posted by heisenburger
-
New conditions to consider the map cleared
heisenburger replied to topic's heisenburger in Exiled Bot Feature Request
Just tested it. The bot still went back to the old map after "max run" timed out. Same thing with chicken on low hp. But frankly I find the "max run" timer a bit unnecessary. If no mobs are killed in several minutes, the bot should just chicken. The "max run" timer only makes us look more suspicious when we get stuck for 10-20 minutes repeating the same action. I could be wrong, but please consider giving "no mobs killed" timer the highest priority. -
New conditions to consider the map cleared
a topic posted heisenburger in Exiled Bot Feature Request
Now the bot can treat a map as cleared if the "no mobs killed" timer runs out. Please consider adding two more conditions (optional): - If the bot chickened for any reason (boss on sight, low hp), the map is considered cleared - If the "max run" timer runs out, the map is considered cleared (for some reason the bot sometimes would return to the same map after "max run" time, so this option would be helpful) Thanks! -
Hopefully this will be fixed. The bot shouldn't wait 15 minutes to pick up an item or do anything else. It should just chicken after 60-120s if nothing's killed.
-
Having the same problem.
-
0.54i bot does not chicken and gets stuck in map
heisenburger replied to topic's heisenburger in Archives
Bump. Same problem in 55g. The bot just spent 15 minutes attacking air in a map. No mobs nearby. edit: I just restarted the bot at the same spot in the map, and it stopped attacking air and started exploring again. suggestion for a quick fix: if the bot has been attacking too long without moving again, reset the bot using F11 or chicken. -
For skills like flame totem with Ancestral Bond, it's useful to cast two totems quickly with very short delays, and wait a few seconds to cast another two totems. If this is implemented, it'd be much appreciated. Idea for a "simple" fix: for each skill in "skills.ini", add a second cooldown variable and a cast counter variable. Assuming the current bot does something like this: while (mob_in_range) cast_skill(); wait(1000); //1000 is user defined Suggested version: while (mob_in_range) { cast_skill(); count++; wait(50); //50 is user defined if (count >= user_defined_val) { count = 0; wait(1000); //1000 is user defined } } This will allow the bot to use a skill several times in short bursts followed by a longer cooldown.
-
Just name your main char with "axxx" or "bxxx" so it's near the top.
-
The tasks may sound basic, but that's a shit ton of work for one person. I don't see this happening before the other problems get sorted out.
-
Anyone else's screen gets messed up randomly?
heisenburger replied to topic's heisenburger in Archives
This is it. Thanks! -
This is a problem with my OS, so I'll just post here. Sometimes my screen looks like this. It happens only when I'm botting. If I drag this "thing" to the right, everything's fine again except all my windows become narrower. If I drag it to the left, it takes me to the Win8.1 Start screen. Using Win8.1. PC's connected to 2 monitors. Anyone ever experienced this weird thing?
-
Just from what I've seen, the bot always attacks Animated Guardian first. The bot also attacks "Summoned Skeletons" endlessly when it should instead focus on the totem/shrine.
-
Just to make sure: did you put all the maps in stash 1,2,3,4?
-
Focusing Voll/ other main bosses in a map.
KiLLLer6091 replied to topic's heisenburger in Exiled Bot Feature Request
Having never farmed Voll, I'm curious about how profitable it is to farm Voll. My bot makes about 5ex after running maps for 24hrs. Is it much better to farm Voll? -
Botting a higher resolutions??
andromeda05 replied to topic's heisenburger in Exiled Bot Feature Request
I imagine a lot of legitimate players also use 800x600. To avoid false bans, GGG most likely doesn't ban you unless you're being extremely suspicious, like running a flagged process in your system or doing something really unusual in their system (like repeating the same action for a long time, running 24/7, using VM+VPN). -
Since I have just 4 tabs.... have you tried using just stash 1,2,3,4 in the bot and storing a map in those tabs and see what happens?
-
Which game client? normal/steam/garena/etc?
-
0.54i bot does not chicken and gets stuck in map
heisenburger replied to topic's heisenburger in Archives
^ That's a better idea. Since the bot can already chicken on user-specified monsters, it might as well ignore specified monsters as well as unspecified monsters that you spent X seconds fighting. edit: ignoring unspecified mobs may be too much work for alk due to reversing, so for now a quick fix like "chicken if no mobs killed for X seconds" would be nice. Actually... the bot is designed to chicken after no mobs are killed in X seconds, but sometimes it doesn't chicken (described in the 1st post). -
0.54i bot does not chicken and gets stuck in map
heisenburger replied to topic's heisenburger in Archives
The bot was attacking a "smoke" on the ground, and the smoke never went away. All mobs were killed near the bot (within ~5 screens) . Maybe a quick hack would be useful: if "Map finished" repeats more than x times in a zone, chicken. It'd be like the "get unstuck" function the bot currently uses. -
What client are you using? Show us the logs? I never had this problem.
-
After the map is explored and the bot is in "restart state" and "chicken state", sometimes the bot would spend the entire "max run" time attacking air. Last run: 2015-11-29 08:57:30 [info] -> Current complex map explored !! 2015-11-29 08:57:30 [info] -> Chicken state because no tp found in player's inventory 2015-11-29 08:57:30 [info] -> Restart state because no monster were killed for 130 s 2015-11-29 08:57:30 [info] -> Chicken state because no tp found in player's inventory 2015-11-29 08:57:30 [info] -> Map finished!! 2015-11-29 08:57:30 [info] -> Attacking monster using mouse_right key at distance : 1.414214 2015-11-29 08:57:30 [info] -> current area not found, please wait for alkpone to add it. 2015-11-29 08:57:30 [info] -> Current complex map explored !! 2015-11-29 08:57:30 [info] -> Chicken state because no tp found in player's inventory 2015-11-29 08:57:30 [info] -> Restart state because no monster were killed for 130 s 2015-11-29 08:57:30 [info] -> Chicken state because no tp found in player's inventory 2015-11-29 08:57:30 [info] -> Map finished!! . . . 2015-11-29 09:03:30 [info] -> Attacking monster using mouse_right key at distance : 1.414214 2015-11-29 09:03:30 [info] -> current area not found, please wait for alkpone to add it. 2015-11-29 09:03:30 [info] -> Current complex map explored !! 2015-11-29 09:03:30 [info] -> Chicken state because no tp found in player's inventory 2015-11-29 09:03:30 [info] -> Restart state because no monster were killed for 130 s 2015-11-29 09:03:30 [info] -> Chicken state because no tp found in player's inventory 2015-11-29 09:03:30 [info] -> Map finished!! Timer:
-
Ideal pc build for 20+ VMware and exiled bot runs?
Facebook replied to topic's heisenburger in Archives
Unless you can buy Amazon Cloud IPs in bulk and assign one to each of your bots, I guess you'll need to find/pay for VPN as usual. Either way your accounts will look suspicious as hell, but I'm still entertained by this idea. -
Ideal pc build for 20+ VMware and exiled bot runs?
Facebook replied to topic's heisenburger in Archives
Very interesting. Even if it's feasible, once enough people do it, GGG will catch on and flag EC2 IPs. Just like VM+VPN, pretty safe until it became popular. -
Set a low priority on "Summoned Skeletons" from totems and shrines
a topic posted heisenburger in Exiled Bot Feature Request
The bot would spend the whole "max run time" to kill summoned skeletons that come from shrines and totems. The bot doesn't give these mobs a low priority like it does to other summoned mobs. Sometimes the bot gets lucky and activates the shrine or kills the totem, but most of the times it just gets stuck in an endless loop of killing... A fix would be much appreciated. -
Or restarting the bot. Maybe for now we just need a script that restarts the bot/client when something's stuck