Jump to content

Ordush

Elite user
  • Posts

    1178
  • Joined

  • Last visited

Everything posted by Ordush

  1. @Droidz Okay so it works in a way. It shows the correct range now, however it does not do it based on the target size. My aciton bar is "white" meaning the game even thinks i'm far enough away. But with a mob with a big target size, you have to go further than 8 yards away to use ranged abilities. Is there any way i can get target size into my calculation?
  2. Cheers Droidz. I will test it out! Just another thing. WRobot thinks that hunter range is 5 yards. in Vanilla it's 8 yards. At least it was like that last i tested. :)
  3. Update is out, should fix Lifebloom. And as a bonus i have increased the speed at which it casts. :)
  4. And that is exactly what it does :P
  5. Unfortunately i haven't been able to do any updates to any of my fightclasses for a while now. I have been in bed most of the time, i just made a small update for the hunter fightclass. I will ofc. look into the other issues as soon as i can.
  6. Aight, i will look out for people reporting. Cheers. :)
  7. I have compiled a dll file with MemoryRobot. If i recompile with the new dll file, will it work? Or have you changed how the methods work?
  8. I can't seem to find which Methods you have changed, am i blind or can you list affected methods? :)
  9. This does not fix anything? The first one just tells if a auto-shot is in range, the other one checks attack. It's nice that we can check if a spell is in range. However, this does not give the range. We need the number (Range as a number). The methods listed above will make a shit ton of noise if you play with sound, and it uses lua which will slow down the fightclass. Also try and look at what i wrote above.. I wrote EXACTLY that code. To me it's clear that what is not working is the mob size calculator.
  10. Partybot makes sense, because there movement is controlled by bot. But it should not be a problem for the druid. However, i will look into it. :) Note: I am currently very sick, and have been since november 2017. I'm getting better for every day, and as soon as i'm fully myself again, i will do a lot of updates to all my fightclasses.
  11. Sounds weird. I will look into it. Are you using movement control in wrobot?
  12. The fightclass will attack what the bot tells it to attack, if your quester/profile is not telling it to kill adds, then it wont.
  13. You need some kind of plugin for that.
  14. You are seriously stating here that it doesn't seems to work? :O Ofc. it works. Please refer to the FAQ. If this does not solve your issues, please don't hesitate to visit my discord channel for more help. That error you see there is not actually an error, it's just WRobot that thinks there is a format exception.
  15. There is no trial version of this fightclass
  16. @Droidz Sorry bout the late answer, i was hospitalized. This prints 11,3342 as range, when it's 8 yard range. So not better. =/
  17. Imagine your fightclass being a text with instruments, where each instrument can't be read without reading the other instruments coming before it first. So it reads form top to buttom, then it repeats. (Loop). The amount of instructions it has to read through determines how fast it reads the page. So if you have a shit ton of conditions, it'll slow down the reading process. Reading from memory goes faster than looking for in-game lua conditions. So if you want the 'reading speed' to increase, you want to decrease the amount of in-game lua conditions or make your overall conditions smarter. I will make an example here for you on how you can make your conditions smarter (faster). Say you have 4 spells after eachother. Spell1 (Cast this if if not in combat, cast this if mana is x%) Spell2 (Cast this if not in combat, cast this if mana is y%) Spell3 (Cast this if not in combat, cast this if mana is z%) Spell4 (Cast this if not in combat, cast this if mana is w%) You change this to be smarter like this: My4Spells (Cast this if not in combat) { Spell1 (Cast this if mana is x%) Spell2 (cast this if mana is y%) Spell3 (cast this if mana is z%) Spell4 (cast this if mana is w%) } this is a very very rough and stupid example, but it should get the point out. So in short, to speed up the condition reading. You want: 1. Memory > Lua conditions 2. Smart code 3. If you look at my Vanilla/TBC hunter fightclasses (or any fightclass i have made) you will see right away that i have used TONS of Lua. So it can be done, but you want to read through lua as few times as possible. :) 4. The higher FPS your fightclass has the faster it reads through the page (FRAMES). So increasing the FPS both for the fightclass AND in-game will add a little speed (just like Droidz said it). Hope this helps.
  18. The problem is that wrobot range calculator is bugged. I am working on a work-around. I will release the long awaited update tomorrow.
  19. Yes, this is a bug in WRobot's range calculation. I will fix this asap. I have been sick for almost 2 months now. So i haven't gotten much coding time. :( When i have not been sick, i have been working.
  20. Still no word? @Droidz
  21. @Droidz Pretty please look into this <3
  22. It works fine in the way that i am using it. In my TBC profile, this works perfectly, no bugs etc. The issue here is the range being off, which is what i started saying. :) I think i've produced enough evidence. :) Also, the range needed for ranged attacks is set to 5 yards. in vanilla it's not 5 yards it's 8 yards. :)
  23. wManager.Events.FightEvents.OnFightLoop += (unit, cancelable) => { var unitsAffectingMyCombat = ObjectManager.GetUnitAttackPlayer(); var unitsAttackMe = unitsAffectingMyCombat.Where(u => u != null && u.IsValid && u.IsTargetingMe).ToList(); LuaUtils.wrPrint("GetDistance:" +ObjectManager.Target.GetDistance); LuaUtils.wrPrint("DistanceGood:" + _AutoShot.IsDistanceGood); if (ObjectManager.Target.IsAttackable && unit.IsValid && !ObjectManager.Me.IsCast && ObjectManager.Target.GetDistance < 8 && !ObjectManager.Target.IsTargetingMe && !ObjectManager.Target.GetMove && unitsAttackMe.Count <= 0) { Move.Backward(Move.MoveAction.PressKey, 3000); } }; However, it's not so much the refresh rate of the distance calculation, because as you can see in my screenshot, i am standing completely still at 7yard range from the mob, and WRobot thinks i'm 9 yards away. Edit: When a mob is melee hitting me WRobot thinks it's 3 yards away.
×
×
  • Create New...