It looks like a derelict ship – one where the pilot has ejected but the ship didn't blow up, which happens from time to time (the fact that it doesn't say "Clean" or "Offender" next to "Python" is usually a sign that the pilot has skipped out). The appearance on the scanner, as a white dot, is correct – but you should be able to shoot it. When you shoot it, does your laser go right through? Or does it hit the Python but not do anything?
It looks like a derelict ship – one where the pilot has ejected but the ship didn't blow up, which happens from time to time (the fact that it doesn't say "Clean" or "Offender" next to "Python" is usually a sign that the pilot has skipped out). The appearance on the scanner, as a white dot, is correct – but you should be able to shoot it. When you shoot it, does your laser go right through? Or does it hit the Python but not do anything?
I see defending ships from Rock Hermits that don't say "Clean" or "Offender". They appear as regular yellow dots on scanner though. Lasers do not pass through them and ramming them hurts.
Also, I've seen both alive and dead Thargons which prove near-impossible to hit with lasers -- the laser appears to pass through them.
It looks like a derelict ship – one where the pilot has ejected but the ship didn't blow up, which happens from time to time (the fact that it doesn't say "Clean" or "Offender" next to "Python" is usually a sign that the pilot has skipped out). The appearance on the scanner, as a white dot, is correct – but you should be able to shoot it. When you shoot it, does your laser go right through? Or does it hit the Python but not do anything?
I see defending ships from Rock Hermits that don't say "Clean" or "Offender". They appear as regular yellow dots on scanner though. Lasers do not pass through them and ramming them hurts.
Has nothing to do with ghost ships. Civilian defenders don't get scanClass CLASS_NEUTRAL, but CLASS_NOT_SET by default. I consider this an Oolite bug.
Civilian defenders don't get scanClass CLASS_NEUTRAL, but CLASS_NOT_SET by default. I consider this an Oolite bug.
I never wanted to change it because it was a 'feature' that was present for so long. Anyhow, this is corrected in trunk a few months ago. (Not in 1.76.1)