Telegraph mechanics

[HeroXx]

Hi all,

I have a working CC that I'm happy with, the only thing that I don't have implemented is telegraph management. Is there a good approach in WB to deal with telegraphs?

Also, are compiled class libraries not accepted by WB? I can get pure .cs classes to be imported but it doesn't appear to pickup the dll if I put in the routine folder.


Edit: I should add that I understand that Telegraph has a method Contains(Vector3 position) that I can tell whether or not a position is in a danger position. What I'm not sure on is the most effective way to get a safe position.

 

[Apoc]

I'll have to make an "at-length" post at some point about telegraphs in Wildstar, as well as do some more wrapping to make API easier.

https://www.assembla.com/code/wilds...ion-2/nodes/41/trunk/Omnibus/Dodge/Evading.cs This may be helpful to get you started.

Contains just does some math based on the telegraph size/shape params. It's only going to be useful for things like "I'm in a bad spot, time to calculate where is a good spot to be".

 

[HeroXx]

I'll have to make an "at-length" post at some point about telegraphs in Wildstar, as well as do some more wrapping to make API easier.

https://www.assembla.com/code/wilds...ion-2/nodes/41/trunk/Omnibus/Dodge/Evading.cs This may be helpful to get you started.

Contains just does some math based on the telegraph size/shape params. It's only going to be useful for things like "I'm in a bad spot, time to calculate where is a good spot to be".

Cheers, I did run that through to begin with but it doesn't seem to be able to generate a candidate and without breakpoint it's pretty hard to debug.

CommonBehaviors.MoveTo(Vector3) also gives some weird issues, it basically causes the bot to just run towards the position and then through it forever, similar to the issue I reported with the default routine.

 

[Apoc]

Cheers, I did run that through to begin with but it doesn't seem to be able to generate a candidate and without breakpoint it's pretty hard to debug.

CommonBehaviors.MoveTo(Vector3) also gives some weird issues, it basically causes the bot to just run towards the position and then through it forever, similar to the issue I reported with the default routine.

How are you calling MoveTo? (You should probably use MoveWithin, as MoveTo has fairly different logic applied to it)

 

[HeroXx]

How are you calling MoveTo? (You should probably use MoveWithin, as MoveTo has fairly different logic applied to it)

I'll give MoveToWithin, I managed to get a workaround by using Pulse to stop the navigator.

I assume CommonBehaviors.MoveWithin(closest, 1f, true); is ok for 'I want to move within 1 unit from the given location' ?