ive used and gotten the cliff leel validators to work appropriately. but i dont know how easy it would be to use for your medivac, becauswe from my uses its been when you validate, you are comparing 2 points. the points usually handled are source/unit point and target/unit point. you can also use persistents as target/unit etc... (to not force just the target mouse point but maybe x frames ahead of you (say for a blink ability)). if what you want is for the medivac to never be able to unload at the highest cliff level say, then youve got 2 options off the top of my head *(but maybe some1 will come up with a better solution). being its based off COMPARING 2 point cliff values and not just comparing a static value for the cliff level;
1) make all the 'cliff level' area you want a single location and when unit enters removed unload ability, unit leaves, add unload ability (not sure how this would work in real time if units are loaded inside)
2) you could set a point or some 'dummy thing' when you 'load' a unit, then when you try to unload compare the position of the 'dummy unit/point' vs the current unload location.
these are shoddy work arounds but to do cliff level validations i believe you have to COMPARE 2 location points.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
ive used and gotten the cliff leel validators to work appropriately. but i dont know how easy it would be to use for your medivac, becauswe from my uses its been when you validate, you are comparing 2 points. the points usually handled are source/unit point and target/unit point. you can also use persistents as target/unit etc... (to not force just the target mouse point but maybe x frames ahead of you (say for a blink ability)). if what you want is for the medivac to never be able to unload at the highest cliff level say, then youve got 2 options off the top of my head *(but maybe some1 will come up with a better solution). being its based off COMPARING 2 point cliff values and not just comparing a static value for the cliff level;
1) make all the 'cliff level' area you want a single location and when unit enters removed unload ability, unit leaves, add unload ability (not sure how this would work in real time if units are loaded inside)
2) you could set a point or some 'dummy thing' when you 'load' a unit, then when you try to unload compare the position of the 'dummy unit/point' vs the current unload location.
these are shoddy work arounds but to do cliff level validations i believe you have to COMPARE 2 location points.