Zer0
-
Posts
216 -
Joined
-
Last visited
Content Type
Forums
Articles
Bug Tracker
Downloads
Store
Everything posted by Zer0
-
Unfortunately, among the many things I've tried, I did that. I even tried to check 10 random tracelines between the ones I wanted. You know, for science. Even then, the results were all cached somewhere, for a time at least.
-
Hi, I have noticed that TraceLine.TraceLineGo doesn't update its result immediately when called repeatedly. The best example I can give is when I try to check the LoS for a door. I go in front of a closed door, check for LoS, which returns a positive result (so, no LoS). The method takes roughly 15ms to execute. Then I open the door, but even when the door is open, TraceLine.TraceLineGo keeps returning a positive result, and seems to only update at a random time after a few seconds, sometimes minutes. I'm thinking this is a cached result because when returning wrong results, the method takes 0ms. What exactly is going on here? Does this method have a cache? If so, is there a way to not use cached results at all? Any insight is appreciated.
-
Just posting a comment to clear the air around the Outlands "issue". We've had a few people complaining that the bot does nothing when they take their level 58 character to Outlands. Other have made ridiculous claims that it's linked to having a mount or not. As the developer of this product, here's the final answer: The AQ not working in Outlands before level 60 is not a bug, but an intended feature and there are good reasons for it. Don't manually take your character to Outlands, the AQ will do it for you at level 60. Just let it run! -
That's normal behaviour. If you want to control the life cycle of a thread you have created, you need to keep track of it by assigning it to a variable. This way you can start it in Initialize() and then Stop it in Dispose() // Define the thread and assign it to a variable Thread myThread = new Thread(() => { }); // Start the thread myThread.Start(); // Stop the thread myThread.Abort();
-
Hi guys, I've created a video showing how to create a C# plugin from scratch. If you have questions or need more info, don't hesitate to ask.
- 1 reply
-
- 5
-
-
-
Hi, the paladin book issue seems like an edge case that is indeed not handled properly by the AQ. Usually in WoW, there's no way to lock yourself out of a quest by deleting an item, as there's always a mechanic implemented to give you back the item, even after abandoning a quest. Not this time it seems. The one quick way you can solve this issue on your side is to simply blacklist the quest using the tracker GUI (ADD TO BL button). The other way to solve this would be to add an exception in the code for this specific item when scanning for items to delete, but I'd need more thorough testings, and a guarantee that it doesn't have any undesirable side effects. As for your other issue, this is not a bug, but how the product works. It's especially prevalent on high rate servers (I believe warmane is x7 XP?) at earlier levels, where you level so fast that quests become deprecated really fast. Now I understand that the AQ abandoning a finished quest is frustrating, even if it's gray, but it also prevents the occasional issue of a quest that cannot be turned in for whatever reason, and the AQ going back to turn the quest in every new level and eventually having your quest log infested with irrelevant gray quests. Both issue can be worked out for sure, but I've moved on to other projects and I don't think I'll be updating the AQ any more. When I released the product I had a hope that a lot of people would be interested in testing the product seriously and give relevant feedback, or even that developers would participate. But the reality is, all the development and testing have been done pretty much by me alone (with some help from my team), and after hundreds of hours of work, I grew a little tired of it. So I'll use this comment to remind developers that the project is open source. Anyone is welcome to participate, make a fork, or take over. Thanks for your kind words anyway, it's appreciated.
-
Create a new text file. Copy/paste the code into it. Rename the file something like DungeonAccept.cs (make sure you change the extension). Move the file to your wrobot plugin folder.
-
I remember having the exact same issue with Matenia's HMP. If at any point during the session you change your public IP (for example by connecting/disconnecting to a VPN), you get locked out of the product for a time. This is a vendor protection to ensure that only one of their product is active at a time per key/IP. It has nothing to do with WRobot itself.
-
I'm refactoring my inventory plugin from the grounds up and there's still one lasting issue that I can't seem to figure out after days of investigating. For context, I'm testing in dungeons, with high drop rates and I occasionally get a LUA error "stack overflow (table too big to unpack)". I can't trace back to its origin. I have only 3 LUA calls that unpack tables on return in the entire plugin. I'm positive they're not the issue, so something else is happening. I've noticed that it happens mostly on group rolls (but not only) and not on all characters. My only way to confirm this is by using BugGrabber and BugSack to get the time stamp of the LUA error, and outputting the time stamp in the chat before each LUA call, but even that is not very reliable since you don't get milliseconds precision, only seconds. The LUA call I make when rolling is the following: Lua.LuaDoString($"ConfirmLootRoll({rollId}, 2)"); It's exactly the same as before the rework (which was working flawlessly). As you can see, it's extremely simple. the rollId parameter is always checked in the log and always correct. I've never had this issue before, so any input is appreciated. Have you ever seen this issue? What could cause it? Is there any way at all to reliably detect which LUA call in the plugin is faulty?
-
Having a flying mount doesn't have any impact on the AQ. If you had an issue, it was something else.
-
Can't help you if you don't provide any details at all. The plugin simply calculates a score for each item depending on their stats and your stats weights. If one has a higher score and is equippable, it equips it. -
The AQ is not meant to handle training. For this, you can use our vendor plugin which will take you to a trainer every even level (or every level specified in the settings).
-
Hi, I indeed forgot to add the default gathering states. I've pushed a new version. This is fixed.
-
It is possible, but you'd have to write your own plugin. It would simply subscribe to either wManager.Events.LootingEvents.OnLootSuccessful or wManager.Events.LootingEvents.OnLootingPulse. The first argument of both handlers being the unit, you can add it to the WRobot blacklist directly from here, or manage your own blacklist. -
A lot of crashes
Zer0 replied to Phantom's topic in WRobot for Wow Wrath of the Lich King - Help and support
This issue is sometimes caused by a faulty/broken xml file from the WRobot/Settings folder. Make a backup of this folder and try removing the files in this folder containing your character name. -
The issue is fixed but you will have to redownload both the Inventory plugin and the FlightMaster plugin. Sorry for the inconvenience.
-
Thanks you. Just FYI, as the description says, Northrend is actually the worst zone for the AQ, especially above level 75. Most quests at this level are unreachable or unfeasible. So I advise you switch to a grinder or a profile quest once things get complicated.
-
Version 1.0.0
3467 downloads
Overview Hi guys, The Wholesome team is proud to present the Wholesome Auto Quester (AQ) for Wrath of the Lich King. Please read the description below before downloading. DISCLAIMER: We DO NOT provide public support for this product. Please don't contact us about it unless you're actively participating in its development. The AQ is an experimental product for WRobot. It is not a profile. It is not a one-click leveler. The AQ uses an Azeroth Core core WotLK database to extract quests and objectives available in your set level range. The information is compressed and embedded into the file, so no additional download is required. It then generates tasks with different priorities based on their nature and distance, making it automatically complete quests. It only tries to complete objectives of the following types: Talk to / Kill / Kill & Loot / Gather / Interact / Explore. All other types of quests are automatically filtered out (escort / PvP / dungeons / item interactions etc..). The AQ is open source and free to use. Prerequisites Before starting with the AQ, make sure that: - Your WoW client is in English. - You don't use any WRobot plugin, other than the Wholesome ones. - You don't use any WoW addons. - You don't use it on an account you're not ready to lose. Due to the dynamic nature of this product, it might put itself in difficult situations. - You keep an eye on it while it's running. - Your WRobot folder is not in a Cloud sync folder, like Dropbox or OneDrive. These have been reported to lock files and cause issues with WRobot and the content of the Data folder. How to install Copy the .dll file into your Wrobot/Products folder. Next time you start WRobot, Wholesome_Auto_Quester should appear in your list of available products and be ready to use. Settings Log debug - Displays additional dev info in the log. Should be used by devs only. Quests GUI - Will display a GUI window with a lot of info on the current state of the AQ. Dev mode - Displays info on the client screen and generates a debug JSON file. Should be used by devs only. Level delta minus - The minimum level of the quest range to do. Level delta plus - The maximum level of the quest range to do. The default value is delta minus 5 and delta plus 0, meaning, if you're level 12, the AQ will only try to do quests from level 7 (12 - 5) to level 12 (12 + 0). These two settings are very important to understand. They are updated every time you level up. You should set a lower range for weaker classes. Record unreachables - The pathfinder can sometimes have trouble finding its way to a NPC or an object. When it happens, you can choose to have them recorded internally and make sure the AQ doesn't try to reach them again. Grind only - Ignore quests and use the auto grinder only. Continent travels - Will travel through continents. We highly recommend you leave that setting enabled. Abandon unfit quests - Will automatically abandon unfit quests (out of level range or undoable by the AQ). You should leave it enabled, or your quest log will end up being full. Blacklist danger zones - Will try to detect zones with a high concentration of hostile NPCs and blacklist the area. These BL areas are reset at each level up until the zone is not a danger anymore. Turbo loot - Replaces the default WRobot loot state with a custom, faster loot state. Please be aware that it can occasionally miss a few loots. Stop at level - Will stop the AQ as soon as the set level is reached Features - Picks up / completes / turn in quests from NPCs, game objects and items. - Auto grinder - Clears your path against hostile units - Travels through continents (boats, zeppelins, tram...) - Force Spirit Healer resurrection and uses hearthstone when it died too many times - Blacklists dangerous zones and zones where you died - Most elevators are implemented - Extensive GUI - Wholesome plugins compatibility - Automatically extracts the db json file into your Data folder - Automatically updates when a new version is released FAQ I manually sent my character to Outlands before I reached level 60 and now the product doesn't work This is intended. The product will only start questing in Outlands when your character is level 60. Don't bring your character to Outlands manually. Just let the AQ run in Azeroth, and it will automatically travel to Outlands as soon as it reaches level 60. Can I use the AQ in the DK starting zone? No, this zone is too specific and enclosed for the AQ to function. Can I use the AQ on other WoW expansions? No. It only works with WotLK. Where can I get support for this product? We do not offer public support for this product. Please do not contact us about it unless you're actively participating in its development. Which classes are recommended with the AQ? The AQ will try to complete difficult quests. We recommend that you choose a strong botting class who can easily deal with multiple enemies. The least recommended are Mage, Rogue and Warrior. If you use a weak class or a weak fight class, it will die a lot. What server XP rate works best with the AQ? The AQ can work with any server rate, although it seems to work best starting at 2x. At 1x the AQ will travel a lot and occasionally run out of quests to do. The Auto grinder will take over to fill in the gap, but it will not be ideal. With extreme rates like 50x, the AQ is not worth using. Does the AQ work with non-English client? No. It uses in-game strings for a lot of interactions. The AQ will not work at all if your client is not in English. Which plugins work with the AQ? We didn't test all the available plugins and can't guarantee their compatibility. We do recommend that you use the Wholesome plugins (vendors, flight masters and inventory) and only those. We made sure they are compatible with the AQ. Any other plugin can cause undesirable side-effects. HMP has been reported to not work with the AQ, but it has not been tested by our team. Which WoW addons work with the AQ? We recommend that you don't use any WoW addons when botting. Avoid any potential interference. Is the AQ better than a quester profile? No. A well crafted quester profile will always be better. The bot dies a lot, what can I do? Set a lower level range. Make sure you use a strong fightclass. Blacklist problematic quests using the "ADD TO BL" button in the AQ GUI, or contact us to add them to the default blacklist. If a quest is hard but not impossible to do, we can also artificially inflate its level in the product so that it's done at a later level range. What is the auto grinder? If the AQ runs out of quests, or if you enable the setting "Grind only", AQ will search for hostile NPCs of type Beast in your level range to grind. It is not guaranteed to take you to a safe zone. Does it work in Northrend? Northrend is problematic with the AQ. A lot of quests cannot be completed and later level quests are out of reach (northern part). We recommend you switch to auto grind or a quester after level 75. The log is saying "Server has not sent our quests yet". What does it mean? The AQ needs to know which quests you already have completed, and the only way to do it is to request the server you play on to send that list. The response is throttled on most servers, meaning it can take a few minutes for the AQ to receive the answer. At level 1, it won't be a problem. On higher level, if it's the first time you use the AQ, the bot might try to pickup quests you already have completed for a few minutes. Once the message is gone, the AQ list is synchronized with the server and the message will never appear again. Where can I find the source code? https://github.com/Wholesome-wRobot/Wholesome-Auto-Quester Project Wholesome – A quick word The goal of Project Wholesome is to develop, test, and freely share wRobot products. All the code created under the project is transparent, open-source, and then released in the store for free. Nothing released under Project Wholesome is sold for profit, although individual donations are welcome. We are always looking for more testers and developers. If you want to participate, please join our Discord channel. Project Wholesome Discord: https://discord.gg/NEq4VA6 Wholesome team Club: https://wrobot.eu/clubs/9-wholesome-team/ Donation This product is free to use and share, although I have set up a Paypal donation link in case you are happy with my work and want to encourage me with a donation. Special thanks Special thanks to the entire Wholesome team for their help and kindness. Love you guys! @FlXWare for the help, the precious insights and the laughs @Hashira the legendary Italian chef for helping me turning mad spaghet into tasty lasagna @Talamin for the support and help with the testing @Kamogli for the tests and kindness @Energia because you rock Enjoy! -
There's no simple solution for that. The targeting/following behaviors are handled by the party product. Ideally, you'd need a custom made product.
-
LOS Breaking
Zer0 replied to lebthug243's topic in WRobot for Wow Wrath of the Lich King - Help and support
It's possible but hard to implement. You would have to come up with an algorithm that tests positions around you and find one that is both reachable by the pathfinder and out of sight from your target. Once it's done you'd have to stop the rotation and move you character there. You can use TraceLine.TraceLineGo to test LoS between positions and your target. Be aware that it's counterintuitive as it returns false when in sight, and therefore true when out of sight. -
That's a really cool trick for the ObjectManager blacklist, thanks
-
Blacklist events do exist and I checked them, but the "mob seems bugged" thing doesn't fire anything, as far as I know. I confirm that there is a GUID blacklist in wManager, and that's what I'm using, but I need to do it dynamically. I can also confirm that Trinity does not generate GUIDs on the fly, it just extracts preset GUIDs from the database for each creature/game object instance. But I suspect not every private server uses the same GUID for each npc , especially if they run on different cores so that would be unreliable.
-
Thanks for the answer. I thought about that, and that would work but I hope there's a more elegant solution out there.
-
Hey guys, I'm working on a product and sometimes, for various reasons, I'll come across a bugged mob or a mob that cannot be reached (ex: the Volatile Mutation that is in a cage, in the Draenei starting zone). The WRobot Fight method seems to at least detect that there is a problem. I call Fight.StartFight(guid), the character moves to the mob, and if it's bugged, after a while, I'll get a debug message in the log stating "[Fight] Mob seem bugged". Then it stops the fight... and then my product tries to fight it again. No Blacklist message or anything. I've looked everywhere in the forums and can't find anything about it. I've seen a few logs where after this message, the mob gets blacklisted, so I assume this part is handled by the WRobot default products. So in short, when a mob is detected as bugged, is there any way to trigger a guid blacklist? Or maybe it fires an event and I missed it? Thanks in advance.
-
Qui est le vendeur ? Je pense que c'est à lui qu'il faut demander en cas de doute. Sinon j'imagine qu'il s'agit de l'URL de ton profil sur ce site qui est unique et qui permettra au vendeur de t'affecter une clé d'activation chiffrée. Clique sur ton avatar en haut à droite du site puis Profile. Et ton username, mxg87.
