Combat - Phase 1 Testing

[John Adams]

As I am sure you all are aware, almost nothing about actual class abilities is implemented yet; only the base system in preparation for script creation. So no, nothing about your abilities will be live-like until Faux let's us know. What you likely see is a basic damage component (generic ability) for casting right now. Sorry if that was not clear earlier.

[Amnath]

We did not anticipate anything working, so we had just wanted to mention a couple of things that do, a little bit better than they are supposed to.

For the most part, anything you are able to cast, is animation only, except for those two.

[Amnath]

I see the group encounter list starting to work, at the same time something messed with mob behavior. You can kill them in one spot, but if you take just a couple of steps, they bug--follow you at zero distance but are out of range. Your encounter list shows aggro, but it isn't real, as you can log out.

[Galladicus]

Yeah, I can also confirm what Amnath said. If you can remember where you pulled the mob and return to that point, the mob is in range again.

It seems the only point that matters for determining range from a target is the point you pulled it at.

[zippyzee]

There were some recent changes to npc movement code that might have created this issue. I'll look into it. Thanks!

[John Adams]

Ahh, I was thinking it was my new damage and Lua code, because I attacked something and it ran off, then returned and stood right on top of me (the Podlings). Hopefully that wasn't my doing. I had some attacker/target/defensive objects mixed up but fixed it before I committed. And NT does not have my new code.

[zippyzee]

This is fixed in my latest commit.

I don't know exactly why, but the other code works (worked?) fine on my home pc. The bug involved calculating the difference in time between movement updates. On my office PC, significant digits were getting cut off and it was basically calculating the change in time as 0 when using floats. I switched it around a bit (back to doubles, as I originally had it) and it seems to be fine, now, properly calculating the change in time.

[Amnath]

Are you talking about another server?

I still see the same quandry, however, on the plus side...the camera can now be rotated without making the arrow in the rangefinder flicker all over the place.

[Xinux]

He committed the change to the dev branch which isn't on New Telon yet.

[zippyzee]

Yes, I should have made that clear. It's been committed to our servers for testing and will go live whenever John is ready to do so. And you can thank Xinux for the flicker-fix.