Why .net sorts bools as false then true for ascending order is beyond me. It may have something to do with the fact that false = 0 and true = 1, shrug.
few more fixes for the boolean sort
RAH!! I win. Couple more fixes to targetting and priority.
more tweaking to unlock selection
Hopefully
Fix the NullReference
stop trying to target things that are already dead
SortBy bool values correctly, who knew that c# sorted bool values false then true (how screwy ffs)

Change questor to compare the Priority Level type not the active EWAR type. this should make sure better ewar killing generally
Nico, notice the comment out section(s). something like that should work (possibly... that exactly...). I have previously had issues with IsValid though so we may need to verify its use case.
this should do it and not have to resort to using isvalid.
Small fixes should give major impact :D
Make sure we will unlock low value targets to make room for the preferred if we need ot
First iteration for better movement for non speed tanking vessels
Second Iteration of better movement for TurretVessels
Stop bouncing tagerts so much FFS!
bugfixes, better handling
nullexception fix
Just a little bit nicer
Merge branch 'DevDaxten' of git://github.com/Daxten/Questor into BleedingEdge
make sure we do not (ever) attempt to target something that we are already actively targeting