Simple marker fix for 1.4

[aintaro]

Hello,

Can you check the player height when a player hits a marker.

The problem now is that when a player is flying above the marker the marker still gets triggered.

Thanks in advance,

Greetz Aintaro

[manve1]

you can simply fix that by making a small if statement that checks the dimensions of the marker.

[DakiLLa]

Are you talking about checkpoints?

[Arnold-1]

Well, actually for checkpoints, if you go under them, you will be considered as you hit the marker.

EDIT: i think it should be reported as an issue, not suggested.

[manve1]

It's not really an issue if you can easily fix it by getting dimensions of the marker.

[aintaro]

It's not really an issue if you can easily fix it by getting dimensions of the marker.

thats not the way to write your code...

If they would fix it , than my code would look a lot cleaner and spares me some time.

[manve1]

you do realize you could make a simple function, then do something like ' if markerDimension(marker) == true then ' nothing messy about that.

[Arnold-1]

Why would we do that?

The marker is mainly made to do things when it gets hit, Not to check if he is actually in the marker or no then do things, this is a serious issue, things must stay logical, you have to trigger onMarkerHit only when the marker is actually hit.

[manve1]

if mta "fixed" that, some people replace the looks of the marker which could ruin the way they work, while you could make a simple if statement that doesn't hurt, does it?

[DiSaMe]

I don't know if this issue is serious enough, but the fact that markers work incorrectly still remains true. Events are supposed to be triggered when the player enters the marker. Now they can be triggered when the player doesn't really enter the marker. That's obviously incorrect behavior. Now the best workaround is creating a collision tube. Adding the conditional statement based on height will prevent the actions from taking place when player enters the marker from above. Doesn't happen often, but still possible, and using collision tube for detection is more accurate.

As for keeping the old scripts working, maybe some compatibility option could be provided (like 'legacy' argument for 'getElementMatrix'), but it's very unlikely that there are any scripts which rely on such incorrect and unintuitive behavior.

So this is it, I'm not the one to decide if fixing the markers is worth it, but that would do more good than bad.

[manve1]

I think editing the old scripts is better and simply add an argument for the dimensions.

[denny199]

Manve1, he wasn't talking about dimensions, he was meaning if you are under(or above) the marker (instead of inside) the event "onMarkerHit" or "onClientMarkerHit" will trigger.

[manve1]

Manve1, he wasn't talking about dimensions, he was meaning if you are under(or above) the marker (instead of inside) the event "onMarkerHit" or "onClientMarkerHit" will trigger.

I am neither talking about dimensions of gta sa, i am talking about getting the height,width and length of the marker and adding that into the function so you could set easily the size of a hit box on the marker you want to have.

[manve1]

Manve1, he wasn't talking about dimensions, he was meaning if you are under(or above) the marker (instead of inside) the event "onMarkerHit" or "onClientMarkerHit" will trigger.

I am neither talking about dimensions of gta sa, i am talking about getting the height,width and length of the marker and adding that into the function so you could set easily the size of a hit box on the marker you want to have.

You have said in other reply "if getElementDimension(...",

So You were talking about that.

Please tell me where i said "getElementDimension", i can see that i talked about marker dimensions and i said "if markerDimension..."