Ordush
-
Posts
1165 -
Joined
-
Last visited
Content Type
Forums
Articles
Bug Tracker
Downloads
Store
Everything posted by Ordush
-
That is weird. Does it only do it with my FC? Also isn't turtle wow like a totally custom server with completely different skills etc?
-
Hmm The thing is. It's set to check the range between you and the target. if it's too close it should move out. But for some odd reasons, it seems that the range checker is off. Usually, it's because of the target size. But apparently that didn't change anything. So if your char is in the deadzone and the pet gets aggro it doesn't move away? Because that should be handeled by the backtracking code. 😮 HOWEVER the backtracking code is actually checking for a safe spot to stand. If it can't find any it won't move. Perhaps for some odd reason that code is severely slowed down or somewhy canceled. It used to just walk backwards. But that often resulted in backpedeling into other mobs. etc. which is why i changed to look 360 degrees around itself to find a safe spot to run to. This is actually one of the cool features of vanilla version vs TBC version. But seems to be bugging for you. I will see if I can revise the code for you and remove the check safe spot. However it does come with the caveat that it might run into danger and pull even more. -
That is sooo weird. I am not sure how to fix it though. As I am using the distance checker made by wrobot. And It's something I have not ever heard of before. Apparently there is some incompatibility with the server you are playing on. Pm me your email that you used to buy it, and I will refund you.
-
That is the one.
-
Now I think I understand what you mean by deadzone. In advanced settings of wrobot there should be a button to change something with hitbox sizes. I think the hitbox sizes are different on the server you are playing than wrobot thinks. I am absoultely positive there is a setting in there to change how it calculates the hit-boxes I just can't remember what it is called.
-
That sounds really weird. Is this a cave that is not on all other servers? Perhaps it's not meshed by wrobot? Movement control is not controlled by the fightclass. But by wrobot. The only moment my fightclass overrides the movement is to move away from the mob if it gets in melee range and you do not have aggro on the mob. Otherwise it's 100% cotrolled by the bot. Edit: Try turning off backtracking or change the combat range see if it makes any difference.
-
deadzones? Can you specify? What does the Fightclass do or not do?
-
This topic was last posted on 5 years ago, and apparently the user is also banned. So I don't think you will get any answer tbh. 🙂
-
Personally I do a ton of my 'heavy' checks in tasks that aren't looped. But rather fires once every loop over my overall rotation. Do care about how many threads you open though especially if you plan to keep more than one on a loop.
-
I very very highly doubt that it has anything to do with auto-attack, since it would not be seen from outside your client. If you are teleported it's more likely that a GM is watching your bot and teleporting you to see how it reacts. Unfortunately, there is no work-around for the auto-attack because neither wrobot nor the LUA api for vanilla has any other way to do it. Albeit the sound is a tad annoying if you are playing with sound. But it's simply because the bot puts the spell on your action bar then removes it, which is client-sided.
-
I will look into it, it's been a while since it was updated.- 6 comments
-
- 1
-
-
- in-game settings
- in-game interface
- (and 2 more)
-
Either that or they are doing the classic. "Collect data and make a ban-wave". 🙂
-
They are probably watching this forum, but it could be fun to make a script that writes "WTF??" then stands still or something, if a mob with x GUID changes from hostile to passive. 😛
-
Hello mate, that is because of how vanilla wow works. There are a lot of things you can't do with lua in the vanilla version of wow, so you have to take some other routes. One of these is getting whether or not auto shot is going, this can't be checked normally, so it has to pick up the spell and put it back down to check. Unfortunately, there is no workaround for this, so I suggest playing without sound. The melee issue sounds very very weird. Try changing the range in the settings pane to something else then back again. (Remember to press enter). If this doesn't resolve it, then it sounds like a wrobot issue. Because melee "spells" are only supposed to be cast when the mob is 5 yards or less from the player. If it does cast it then it seems that wrobot thinks you are in melee range. That's unfortunately something I can't do anything about. 😞
-
It doesn't, or it does. But you WILL get banned. 🙂
-
I am afraid to say it, but your account is probably already banned. Mine wasn't banned till i relogged. 😕
-
Haha, and there goes my account. Just after I posted this. 😛 Yeah, it's pretty likely it's detected. 🙂 Too bad, I was 1/3 done with a 1-90 quester rofl. 😛
-
It's weird because I'm leveling using quester (I made myself) I'm level 34. We'll see if any ban hits. 🙂
-
On the "rotation status box" press the little + icon on the top right, to get all the controls. 🙂
-
Yeah it's because of the Lua engine for private classic servers doesn't have any easy way to do some of the checks on abilities, so the sound you hear is the bot opening the spell book picking up a spell making a check then removing the spell again and closing the spellbook. It just goes so fast that you don't see it. Unfortunately that is not something I can make any workarounds for, so my only suggestion is to turn off your sound while botting. 🙂
-
I do not currently support PVP, as I do not endorse botting content that upsets the PVP balance.
-
[Free] [A/H] Nagrand - The Twillight Ridge - Cobra Scales, Knothide
Ordush commented on Ordush's file in Grinder - TBC
https://wrobot.eu/forums/forum/7-tutorials-wrobot/ -
-
You need to be closer to interact with that target
Ordush replied to Pudge's topic in General assistance
In advanced settings, try ticking off the calculate hitbox button, see if it makes a difference. 🙂 -
I googled "Connection not allowed by ruleset (2)". The very first hit comes with the answer. 🙂 It's because you have forgot to change your proxy type to socks instead of http. I believe it's been discussed in this thread somewhere earlier that it HAS to be socks5, not http, otherwise you are not routing around the protocol and it would be the same as connecting without a proxy (risking to get all your accounts connected) however luckily for you it seems that the current version of ProxyCap throws the error "Connection not allowed by ruleset (2)" instead of you routing you through. 🙂
