[Pelipoika]

Originally Posted by FlaminSarge You might be able to improve the tracking behavior by storing the target client's last known position for each mine, and having the mine continue to move towards that location after it loses line of sight. If it regains line of sight during that time, it could start tracking the client again. I recall some old homing rocket plugins did this.

Not sure how i should do the arrays for that

[Chdata]

You could use adt_arrays or decide on a maximum number of save points.

[Pelipoika]

Originally Posted by Chdata You could use adt_arrays or decide on a maximum number of save points.

Well yeah but what i meant was:

Each rollermine needs their own array, how do i associate an array for that one rollermine, how do i know what array is this specific mines

[Chdata]

Well with adt_arrays you could use multiple blocks.

So let's say you have

g_flPosArrayForFirstMine[3]

and

g_flPosArrayForSecMine[3]

In an adt_array I'd just have an array of mines like

a_blockMineEntRef = 0
a_blockMinePositionsArray = 1
a_blockMineMaxIndices

g_hMines = CreateArray(a_blockMineMaxIndices);


MinePositionsArray could either be the handle to an adt_array containing the positions or just a normal array, I'd have to look up the syntax for storing a normal array in an adt_array but you can.

[Misc]

I'm still learning with plugins but does anyone have any hints for how to spawn these at specific coordinates on a map rather than where I'm aiming?

[FlaminSarge]

@peli Just store the last target position in any of the vector datamaps/netprops on the entity. I was thinking m_vecViewOffset. The alternative is to find 3 unused and irrelevant netprops to commandeer and put the floating-point values of the 3 vector components into those.