Matenia

Trial doesn't use meshes and hasn't since like 2016 when wrobot was cracked briefly - which is also the only version still requiring to download meshes.

TraceLine.TraceLineGo returns false when there is no collision and true if there is a condition. You need to negate the condition. You need to use hitflags WMO for spells.

No offense to Droidz, but it's pretty much laziness. He'd have to add everything for every expansion and then maintain it manually if pathfinding for the expansion ever changes. I do pretty much the same thing for some connections in HMP. A few Droidz added after being given the info so I could remove them. Others I still struggle with due to large distances. It's really not as reliable as I'd like it to be.

I just want to say, that I do not use table.unpack in the fightclass and I am getting no freezes, hence why I haven't been able to reproduce this. I'm also 99% certain that the lua error is not related to the freezes, because apparently a plugin doing ReloadUI() is not fixing it - so it isn't a GC issue

The API docs are outdated or incorrect and that sentence is a reference to TBC, where you couldn't see ANY durations (no timeLeft either) if it's not casted by you. I thought it was pretty common knowledge that in WotLK you can see all durations at all times. This is exactly what the default UI does - how do you think it draws cooldown frames or addons like OmniCC wrap timers over them? So to take my original post from weeks ago: local _, _, _, _, _, duration, expiration = UnitDebuff("player", "Polymorph") local timeLeft = expiration - GetTime() -- timeLeft in seconds local timeAlr

Because duration is 5 if the poly is on DR, etc.

I literally gave you the full solution. You have the time left, you have the full duration. From that you can do the math to get the the starting time in GetTime() value.

It's CTM, it's used for everything movement related, interaction, targeting etc. That's what the WoW client uses it for under the hood. Precision is how close you have to be to the target vector for movement to stop.

Lol, Lapewpew von Landoflegends? Manche Leute lassen auch nie die Finger von dem Spiel 😂

You'll have to take that up with Droidz, I only gave you an explanation from what I understood. You paid for a product for retail servers. That lifetime license expired because the product does not exist anymore. That's usually how things worked with bots in the past.

You seem to have paid for wrobot (retail), retail wrobot was discontinued in 2018 when Blizzard came up with their new warden and pretty much all public bots ceased to exist.

If you're using HMP it uses its own resurrection state, which you can disable in the settings. There's also a bunch of debug logging surrounding that. Anyway, that's what log files are good for.

If you use code, you can use polyarea_water and roads, which should help general navigation to avoid water and prefer roads

Can you just use my code example and see if it works? Another example: ExpirationDate = 2020-11-11 18:48:30 (static point in time) CurrentTime = 2020-11-11 18:48:20 (this obviously changes) FullBuffDuration = 10 seconds TimeLeft = ExpirationDate - CurrentTime (this will get lower and lower with time, at the start here, it's 10 seconds) TimeAlreadyPassed = FullBuffDuration - TimeLeft (this is 10-10 = 0) Now as time passes on, the result of TimeAlreadyPassed gets HIGHER and HIGHER until it reaches 10 eventually. So if you look at my condition in my original post, you will see