As happy as I am (OR NOT ) with the motion planning system (there are some lacking functionalities that could added
CHANGES::
to
USAGE: the optional value could be used as cost for other motion planning functions!
(as gml uses only real/string types... this would not create that much of a memory usage... true is actually a real! I could be wrong! Let me know!) Default = -1 (unpassable)
USAGE: Would set the cost value to 1.
ADDITIONS::
USAGE: the optional value could be used as cost for other motion planning functions!
(as gml uses only real/string types... this would not create that much of a memory usage... true is actually a real! I could be wrong! Let me know!) Default = -1 (free).
USAGE: Lets you select a range (using the cell cost) that would limit the path... return a bool... if the goal was reached or not... if it was limit by range (returns false) else (returns true)
USAGE: Returns a 2D array (1st dimension - the number of clear cells within range; 2nd dimension - [0] cell horizontal value and [1] cell vertical value). This would let people define a starting point but no ending point. Useful for tactical grid based games. Ignore would make every free cell cost be 1 (limiting only by range).
USAGE: As default cost value is added it allows for the existence of this other function.
What do you think!!?
Sure there are some other functionalities (what would be your suggestions?)
built in A* algorithm (it's widely used... it's sad it isn't implemented by YoYo, yet)
CHANGES::
Code:
mp_grid_add_cell(id, h, v);
Code:
mp_grid_add_cell(id, h, v, [value]);
(as gml uses only real/string types... this would not create that much of a memory usage... true is actually a real! I could be wrong! Let me know!) Default = -1 (unpassable)
Code:
mp_grid_clear_cell(id, h, v);
ADDITIONS::
Code:
mp_grid_set_cell(id, h, v, [cost]);
(as gml uses only real/string types... this would not create that much of a memory usage... true is actually a real! I could be wrong! Let me know!) Default = -1 (free).
Code:
mp_grid_path_ranged(id, path, xstart, ystart, xgoal, ygoal, allowdiag, range);
Code:
mp_grid_range(id, xstart, ystart, allowdiag, range, [ignore]);
Code:
ds_grid_to_mp_grid(source, destination);
What do you think!!?
Sure there are some other functionalities (what would be your suggestions?)
built in A* algorithm (it's widely used... it's sad it isn't implemented by YoYo, yet)
Last edited: