highco
-
Posts
38 -
Joined
-
Last visited
Recent Profile Visitors
1600 profile views
highco's Achievements
Newbie (1/14)
7
Reputation
-
fragik reacted to a comment on a file:
Multi Pull
-
highco reacted to a post in a topic:
Botting on Retail/Live-Servers
-
highco reacted to a post in a topic:
Quest profile creation video tutorial
-
highco reacted to a post in a topic:
Farm Dungeons How Fix It
-
highco reacted to a post in a topic:
Farm Dungeons How Fix It
-
highco reacted to a file:
Combat Looter Plugin
-
highco reacted to a post in a topic:
Is it possible when I die for the bot to take a 5min break?
-
highco reacted to a file:
[2face] Warlock Demonology AOE Farm
-
highco reacted to a file:
OpenChests
-
hi, sry i didnt check this thread and found your post just now. The problem still happens. I didnt have the time to do much debugging, but i dont think that it has anything to do with wrob. For some reason WoW tends to accumulate ramusage during runtime and at some point it probably reaches an upper limit for the application and throws up errors. If i run a single instance this happens after some days (WoW crashes but WoWs ramusage (above 1.5Gig) is far below the overall available ram on the machine (8Gig) ) if i run a bigger number of WoWs simultaneously (6) it happens after 6 to 8 hours. I am running a memory cleaning program now, that wipes the ram every 5 minutes which enabled me to run several WoWs (6) for the duration of about a day without an error. Right now i just restart the WoWs on a daily basis. Not the best workaround but acceptable. The issue that some of the WoW settings (in particular the max fps boundary) gets reset at some point is probably also not related to Wrob but a WoW problem. Right now i take care of this by firing a macro every some minutes to put the boundary back in place. Since this seems to be a very particular problem i dont think that it is neccesary for you to spent extended time on it. Still it would be of interest whether anybody else is able to reproduce this behavior or has similar issues. I didnt spend much time on botting during the past weeks as soon as i get back to it i will do more bugtracking and get you informed. Best regards and a happy and succesfull new year. highco
-
Thank You very much I will try that.
-
Hey Droidz, I was wondering whether there is a way have Lua code in the <is complete condition> for questprofiles. I would like to expand the garrison routine to starting workorders. and as <is complete condition> i would like to evaluate the number of available orders. this is possible with the returns from C_Garrison.GetLandingPageShipmentInfo() Lua Befehl. I thougt it might be possible to just use the wManager.Wow.Helpers.Lua.LuaDoString(with proper lua script) in the is complete condition, but i can get it to work. Would this even work in theory. How do i have to format the Luascript for the wmanager. Can i just put my luascript in the brakets. If this wouldnt work this way at all, is there a possibility to use the OverridePulseCSharpCode QuestType and have the <is complete condition> configured somehow in the c# code. Thanks a lot for Your help. Best Regards highco
-
this actually happens persistently since i got back to botting some weeks ago (earliest error logs are from mid oktober 2015). I just found that the RAM usage for some of the wow instances increased during runtime for some reason. The fps settings have been reset during runtime to higher values. Maybe while zoning, maybe during relogging. But i doubt that this is due to anything from wrob. Ram usage might be a problem therefore.
-
Hi droidz, thanks a lot for your fast reply. just some remarks from my limited understanding. I already disabled all addons. Yes i do have several instances of wow running. They all run in minimal graphics settings. The usage of ram (of all wow and wrobot instances included) normally settles between 6 and 7 GB. That is quite a lot but still below the available physical ram. The crashes happen about once a day. Its hard to tell because i dont keep exact track of which wow crashed when. But there is hardly a day whith out several instances crashin. In principle I would like to let the wow run as long as possible and mostly unattendet. I will try to relaunch wow more often. The crashes also still happened with no addons loaded and only one wow instance running. May be it has something to do whit applying the hook. Today after the wrob update. When i tried to restart wrob (clean close of the bot, wow still running, updating wrob, restarting and reaplying wrob to wow instance) the wow instances crashed immediately (same error message) after starting the bot. I will try more bugtracking to find more hints on when exactly the crashes happen. It would be very nice if this would be resolve because it makes running the bots "unattendedly" very unrelying. Thanks for your work sofar. Best regards Highco
-
sry double post. pls remove.
-
Hi Droidz, i am experiencing rather unpleasant wow crashes on a regular basis (once a day). The error message says something about memory reading or writing. It only happens when i run wow with wrobot. I have included some logs (they are huge unfortunately) and slides of the error message. I can provide more logs of crashing incidents if needed. Thanks for your help. Regards Highco
-
Hi Droidz, thanks for your fas reply. Blacklisting the zone instead of the mob is unfortunately not always possible. Sometimes that would block a passage to the rest of the profile. Also blacklisting the zones does not always work reliably. The bot seems not to respect blacklisted zones fully in long moves (e.g. going to town) and when moving to farm spots. Unfortunately this also wont solve the issue that the bot will get locked on a bugged mob for hours when unattended, unless it automtically blacklists bugged mobs reliably. Thanks for your effort anyway best regards Highco
-
Hey Droidz, first of all thank You for your product. It mostly works stable and reliable and has so many useful options. One major problem that i have run into in virtually every profile that i have tried is handling bugged mobs. It happens every now and again that the bot runs into a bugged mob an tries to fight it. The health of the mob doesnt drop, it keeps evading or gets refilled after some time and is therefore unkillable. Still the bot keeps attacking and fighting it for hours. This is incredibly annoying and it is a major security issue because it is like yelling "i am a bot! please report me!" It is also very bad for performance since there is no loot, no gold, no whatsoever! I blacklisted the mob, with the blacklist mob option in tools, but the bot still keeps attacking the bugged mobs over and over again. Is there any other way to reliably blacklist mobs or make the bot respect the blacklist? Please do something to solve this problem. It sometimes helps if the bot moves around a little to make the mob attackable, although this is not a line of sight problem. A way to detect bugged mobs could be to monitor the combat text and cancel the fight after a number of evade messages. Monitoring the mob health and cacelling the fight if the health doesnt drop would also be useful. After canceling the fight, auto blacklisting of bugged mobs would be essential to not constantly get locked in fighting the same bugged mob over and over again. I have pasted a section of the log below to illustrate the issue. This happens alot on different toons with different classes and different fightclasses and goes on for hours if i dont interfere. I have also attached a full log. Thanks for your effort Best regards Highco 08:57:16 - [Looting] Loot Iron Guard 08:57:23 - [Fight] Player Attack Iron Peon (lvl 99) [F] 08:57:25 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:25 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:25 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:26 - [Spell] Cast Arcane Shot (Arcane Shot) [F] 08:57:27 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:27 - [Spell] Cast Arcane Shot (Arcane Shot) [F] 08:57:28 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:29 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:29 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:29 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:30 - [Spell] Cast Glaive Toss (Glaive Toss) [F] 08:57:31 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:32 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:32 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:33 - [Spell] Cast Arcane Shot (Arcane Shot) [F] 08:57:34 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:34 - [Spell] Cast Kill Command (Kill Command) [F] 08:57:34 - [Spell] Cast Kill Command (Kill Command) : : : [F] 11:34:44 - [Spell] Cast Kill Command (Kill Command) [F] 11:34:45 - [Spell] Cast Concussive Shot (Concussive Shot) [F] 11:34:46 - [Spell] Cast Arcane Shot (Arcane Shot)
-
-
-
reefer75 reacted to a comment on a file:
98-100 Meatgut Needs Bones (repeatable quest) (Nagrand)
-
Thank you for the fast fix. I didnt get any more freezes and no more error messages so far. It still tends to forget the character specific product settings on restart (gatherer, grinder or schedule ...) though.
-
Hi droidz, since this morning (after updating wrobot) i have the following mafunction. Since i normally run multiple processes of wow I start my wows with a script (in 32bit of course). When i start wrobot it throws the following error message after i click login in the license key manager window: Error during hook test. If the program freeze or have problem I recommend to change in game your directx version. The character specific wrobbot window pops up, but as soon as i click start it freezes and does not respond anymore. I have to kill the process from the taskmanager. I have tried both directx 9 and 11 with the same result. I also realized that in the wrobwindow where the wowprocesses are listed like "process ID - Charactername - in use" the in use part is never listed anymore and i now can start two wrobot instances on the same character. Strangely this happens when i start bot-nr2 after bot-nr1. If i start bot-nr2 first there is no error, but wrobot "forgets" the configuration of the character (like last used profile and whether it was set to gather or grind) I have attached a log file.
-
Bugreporter reacted to a post in a topic:
How to ignore PvP completely in Grinder
-
It seems like a neat feature but i really doubt that this is the most urgent issue to address.
-
tester11 reacted to a post in a topic:
How to ignore PvP completely in Grinder
-
I dont really think that this is the most urgent issue to adress but still worth of some improvement. I also would appreciate to have a more sophisticated option to deal with open world pvp. Although in most cases, i dont believe that just ignoring an attacker is an appropriate option. Just standing there and getting killed is also not the best option. Being able to chose from some options like - fight back, - ignore and carry on with whatever i do, - do nothing and take the beating or - flee run from it (my favorite) would be what i would appreciate.
