Jump to content

Matenia

Elite user
  • Posts

    2232
  • Joined

  • Last visited

Everything posted by Matenia

  1. 10 sessions is the MONTHLY price you're seeing. For one year (like the others are) it's 80€
  2. wRobot is a PRIVATE server bot for vanilla to legion, BfA is NOT supported
  3. das funzt nicht, haben schon viele versucht Im Endeffekt musst du alles von Hand nacharbeiten bzw neu machen
  4. Version 1.0.0

    593 downloads

    This is not a quester useful in itself. It uses 2 positions in Wetlands as an example on how to use such a timer to make grinding random and switch between areas every x minutes. Keep in mind, this heavily depends on the functions in the Custom Scripts part, where I added a QuestHelper class. It is meant as an educational file to help users create better grinders for themselves.
  5. That's an error with HMP because you didn't follow the readme
  6. You can't really RayCast for "non-liquid" areas. At least when I tried the LoS check that Droidz has implemented for it, it never worked (probably not in vanilla), so you can't find a spot that's not liquid and therefore can't navigate out of water.
  7. You need Lua: DoEmote('SIT') if you don't have the buff "Enrage". Assuming you're using the fightclass editor. There are many topics explaining how to enter Lua instead of a spell name and set the editor to "Is Lua, not spell".
  8. This method exists in 1.12 wRobot but not in 2.4.3
  9. What do you mean there aren't any fightclasses doing this? Mine certainly does...
  10. https://classicdb.ch/?item=2516 You buy Light Shot from vendors. In wRobot's vendor database, you can add vendors that sell ammo. Then you can enter the buy/sell tab in advanced settings and set it up to re-buy ammo.
  11. Enter the advanced wRobot settings, you can set it up there
  12. Contact the owner. Considering it says it's a 1-60 grinder, I'm pretty sure it won't be doing quests after that level. With a good fightclass, you should be able to handle the grind. It's best you familiarize yourself with how wRobot works in general so you understand what is actually managed by the profile and what isn't. For example, if your bot gets stuck in a high level zone pathing through it while trying to get to a lower level zone, that is not the profile's fault. wRobot will generally fight back against high levels, if they attack you, even if they're "Skull" enemies.
  13. Since it's not a buff in vanilla, no.
  14. https://wrobot.eu/search/?q=facing
  15. Battlegrounder has no healer option. You need to put everything in your fightclass in C# and overwrite wRobot behavior if that's what you want. Regarding queue pop, trying finding an addon that auto accepts. Don't really have another solution. There's a BG helper plugin somewhere (i believe in the MoP section) you can look for. Not sure if it still works, but probably should.
  16. I do clear the current SESSION blacklist in HMP, when this happens: I will remove that part in the next HMP update, so no more of this: wManagerSetting.ClearBlacklistOfCurrentProductSession();
  17. That tool is probably a render blocker. It saves CPU/GPU but does not prevent models from being loaded into RAM.
  18. Yep, that's the Lua to move bug. Make sure your profile doesn't deactive it and make sure you're not using any conflicting plugins like SmoothMove (my edit should work).
  19. By crash do you mean the client freezes with deadlock? This could be cause by your profile or a plugin deactivating Use Lua to move. Otherwise I doubt it's my fightclass causing crashes. You can try deactivating frame lock in the fightclass settings though
  20. Install SlimDX, install Visual C++ 2010 (or w/e is linked). I just went through this myself on my laptop. Start wRobot normally and not with Quick Launch. You will need to re-enter your license key. Follow that threat, it works.
  21. It's one of the auth errors of the quester you use. It doesn't affect functionality at all.
  22. The bot will not avoid certain areas just because mobs are there. HMP's smart pull can at least avoid pulling groups if your bot tries to actively attack them. But it doesn't stop the bot from pathing through groups. You will need to blacklist the general area and that way the pathfinder will *generally* try to avoid it - this isn't 100% reliable. AvoidIt does this automatically and then forces the bot to generate a new path. It doesn't really work (well) which is why nothing like that has been implemented in the bot. I've fixed compilation errors before and posted it in the vanilla section, but I'm pretty sure it's broken again now. Even when it "was working" - not reliable enough in any way.
  23. wManager.Wow.Bot.Tasks.MountTask.Mount(); // no conditions required
  24. Because all conditions are combined (if you look at Spell Conditions and the way he entered them) through AND operators. You can only use OR operators, if you create your very own condition from scratch. But the way the fightclass editor adds up conditions that are set separately is through AND. You can do it in the form you wanted before (if you set brackets the way Droidz/Bambo explained), but it's really, really slow and inefficient.
  25. All conditions in wRobot are combined with a && operator. In the fightclass editor, you can only create "or" scenarios, but using one sole C# or Lua condition OR creating a second spell with the same name and different conditions. I recommend you just look into how to use C# to write a fightclass from scratch and don't use the editor. Also what Droidz said - wrap your C# conditions in brackets like this: ( <condition> ) You can do everything in one C# conditon too: ObjectManager.Me.Level < 25 && !ObjectManager.Me.IsCast && ObjectManager.Me.HaveBuff("Power Word: Shield") && Usefuls.ContinentId < 2
×
×
  • Create New...