"Target immobilized" but I shouldn't know

[HAARP]

1. Target enemy, no line of sight.
2. Have someone else leg him
3. Betty says "target immobilized", although I shouldn't have any way of knowing that.

[(TLL)Sky_walker]

*REPORTED*

(just cause I wanted to steal kit's work )

[Ingrater]

Maybe your sensors are pickung up that something very heavy is hitting the ground very hard?

[HAARP]

Maybe your sensors are pickung up that something very heavy is hitting the ground very hard?

"It's not a bug, it's a feature!" ?

[(TLL)KitLightning]

1. Target enemy, no line of sight.
2. Have someone else leg him
3. Betty says "target immobilized", although I shouldn't have any way of knowing that.

Yes you would since you have locked the Target and your TC is being fed by that Targets status.

[HAARP]

1. Target enemy, no line of sight.
2. Have someone else leg him
3. Betty says "target immobilized", although I shouldn't have any way of knowing that.

Yes you would since you have locked the Target and your TC is being fed by that Targets status.

Not if I don't have line of sight.

[(TLL)KitLightning]

The current targeting designator does not take into account if the Client has the target identified, the Client will be notified of any changes regardless of the Targets ID status for the Client.

[(TLL)Sky_walker]

well, it should have - this is what makes it a bug.

[Ingrater]

No it's a bug if it is not working as intended by the programmer.
In this case it is simply a wish to make something work differently.

If you are in line of sight it is "Mech immobilized"
if you are not in line of sight it is "Target immobilized" because you can't know what hit the ground, but you do know that something hit the ground.
So everything is working as inteded.

[(TLL)Sky_walker]

It's a bug, cause you know things you shouldn't know.
No LoS == No damage data known == not known that target is immobilized

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.

so it's not that the bug isn't a bug if programmer intended it to work in this way

[7.[WD]Ragor]

It's a bug, cause you know things you shouldn't know.
No LoS == No damage data known == not known that target is immobilized

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.

so it's not that the bug isn't a bug if programmer intended it to work in this way

Sky_guy, read it again. With LoS you see it is a mech which drops down -> Betty: 'Mech immobilized'
Without LoS your senors detect some seismic stuff, something hit the ground -> Betty: 'Target immobilized'

IMO this is made with a plan, call it 'intended'.

-> Your last post is invalid. 

I know, i just repeated Ingraters post... but it seemed necessary.

[HAARP]

Oh. A big seismic "thump". It must mean that the mech I am currently targeting is immobile now!
Are you telling me this is really intended? Because it doesn't make much sense.

[7.[WD]Ragor]

Argh, I got the feel now I'm in a dicussion I don't wanna have because its leads to nothing.
But yes, Haarp, you right.
Mech sensors can detect the exact location of that big thump.
In BTU the mech senors can recognize a mech by its chassis and its location by just one detected footstep.
(thx to the database, a bit the same like military identification works since over 30 years)

But anyway, I'm quite sure someone will go on here and bring in some real life stuff together with the his own logic and some dreamed stuff and this thread goes on and on and on...

Childish try to end the starting discussion: Yes, you two are right.

-> Ragor, signing out.

[Ingrater]

Well you could also argue then from what you know if your taret is a light, medium or heavy mech. Because if you can't know if it was immobilized, you also would not know what mech class it is.

This is working as intended, and was programmed after the guidelines I was given. I might rediscuss this with our lead programmer, until then this is a invalid request for me.

[HAARP]

OK then. It's not like it's a big issue.

But you might wanna add a nice "immobile" indicator next to the target then