Hello!

I have been using targetless plugin for years. It worked flawlessly.
Since a while the plugin does not record any newly scanned ore.

Is there any known issue or bug concerning targeltess?

Does it not save it at all or does the new information disappear when you logout/switch characters.

Hello Inevitable, thanks for reply!

The problem started with being unable to navigate to already-stored roids. I suspect the devs changed the roid IDs within the last year or so.

That's why I cleared the roid table and rescanned the roids at Dau L-10. Worked fine!

However, the same procedure in Azek I-4 did not work in the first three attempts. The fourth worked. Then, at Pelatus O-15, this procedure never worked.

The scanned-roids counter stays at 0. Each time you press "unroid" it says "new roid selected" but there is no navigation to that roid. Really strange...

targetless is currently unmaintained. roid id's changing is entirely dev work.

You do know the roid has to be in radar range to select it, even with targetless?

perialfire:
Not maintained? :-( OK, I will dig into it and try to identify the problem.

yodaofborg:
Yes, I know. The problem must be something else...

interesting... I'd mostly agree targetless is currently unmaintained, mostly... I still keep an eye on it from time to time. I'll look into this more when I have time, but can't promise when that might be.

In the meantime, can you please clear ALL your system notes (manually backup the entire system-notes directory and delete/empty the original [on line this is located in ~/.vendetta/settings/, not sure where on windows/osx but I imagine similar]), and try to reproduce? Also, zip/tar the backup system notes and email them to drazed [@] gmail and I'll see if I can reproduce on my end this coming weekend.

Last time I checked, it worked here. Will test it again after I resub.

Even if the roid IDs had been changed, targetless should still be able to add the roid with its new ID.

I think the problem here is that targetless assumes that the node id of a roid will always be 2, and in the sectors where it is not working, this is not the case. Whether this is a feature or a bug in VO, I do not know because of a lack in documentation on how the node id is supposed to work.

A workaround is that if you find that targetless stops working, leave the sector and let the sector reset, which will make the node id of all the roids 2 again.

Yeah, assuming the sector is always node id 2 doesn't work. There's plenty of times where it isn't.

This just started happening to me too.