@ Chunks
Are you sure it is hard to do in DBC? I thought you can just call the functions in the DLL and get the return values in DBC, and that is basically it. Or am I wrong? Could you describe how the DLL works different in DBP than in DBC?
Also, the reason I don't want to #include the functions for DBC is because they are really slow. 10 enemies is the maximum you can add before the whole game slows down. There is too much processing to do.
Quote: "So depending on your goals, it may be of no benefit to turn the finding of the limbs count and position over to a DLL."
True, there may be no benefit in speed in this specific function, but this is going to be a major plug-in for DBC and DBP. The DLL is specifically designed for anyone to set up complex waypoint systems with an easy-to-use editor and functions. The loading function in the DLL compared to DBC will not be any faster, but the calculations, track tracing, blocking and forcing selections, and angle calculations will be extremely fast compared to DBC. Maybe up to 10000 times faster.

Right now, I have 13 different functions finished or in progress, and that is just the start:
**********************************************************************
Commands list
**********************************************************************
Enable_waypoint_commands()
Disable_waypoint_commands()
Load_waypoint_system()
Set_start_waypoint()
Force_waypoint_selection()
Block_waypoint_selection()
Unblock_waypoint_selection()
restore_waypoint_selections()
Get_nearest_waypoint()
Get_waypoint_system()
Get_waypoint_position_x()
Get_waypoint_position_y()
Get_waypoint_position_z()
Anyway, it will be a pain, mainly for DBP users, to have to check where the limbs are using native commands. That's why I want it all in the DLL so it keeps it's "easy-to-use" personality.
There is one decision I have to make, and it is bugging me. The object I want to import is only to load in where each waypoint is. This is an option you can set in the file. If you don't want it, the editor will save the positions of the waypoints to the file directly, and you won't need the object. This means that I don't really need the X object part of the function anymore, except in very rare occasions. And it is these rare occasions where I will be needing it, and that is why I'm not going to dump it... But maybe I should... I really don't know...
Anyway, thanks for the link, Latch!

I'll have a good look at it!
TheComet

Make the path of your enemies easier with Waypoint Pro!