This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
4rpl:commands:movetowardscellandavoid [2021/01/08 16:01] – external edit 127.0.0.1 | 4rpl:commands:movetowardscellandavoid [2025/02/14 14:57] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 6: | Line 6: | ||
===== Description ===== | ===== Description ===== | ||
- | Takes a starting 3D position (a vector) and generates a new 3D position that is moved towards the target | + | Takes a starting 3D position (a 3-vector) and generates a new 3D position |
- | the delta argument. | + | * The minHeight argument restricts how close, height wise, the resulting point can be to the terrain and/or creeper. |
- | The checkRange argument is an integer that specifies how many cells outward to inspect when inforcing | + | |
- | target lands on. | + | |
- | The checkCreeper argument is a boolean | + | |
- | The checkAC argument is a boolean | + | |
- | The checkPseudoTerrain argument is a boolean | + | |
+ | :NOTE:\\ | ||
+ | To clarify, the only difference in this API and [[MoveTowardsAndAvoid]] is that you can independently specify an X coordinate variable and an Z coordinate variable while not needing a Y coordinate variable. The generated next position will not be limited to the X and Z axis unlike how other TowardsCell API's like [[RotateUnitTowardsCell]] tend to behave.\\ | ||
+ | So be sure to avoid thinking of this API as being similar in behavior to the other TowardsCell API's or it will get very confusing very quickly.\\ | ||
+ | If you came to this API thinking it could generate a next position on only the X-Z axis' | ||
===== Examples ===== | ===== Examples ===== |