3 Commits

Author	SHA1	Message	Date
Răzvan C. Rădulescu	1baed58659	Review smart agents ... I made minimal changes, mostly cosmetic like so: - rename KinematicMovementType to MovementType since GSTKinematicBody2DAgent.KinematicMovementType.COLLIDE for example is really more than a mouthful with repeated Kinematic in the name - add optional movement_type parameter to the constructor, otherwise we'd be forced to construct the object and then specify as an aditional step the type of movement if we want something else than the default - rewrote the constructor to yield on ready and removed _on_body_ready - renamed _apply_steering to apply_steering as this is a public method - renamed _on_SceneTree_frame to _on_SceneTree_physics_frame	2020-02-07 12:29:45 +02:00
Francois Belair	2ae06d3da3	Split agent types into specialized classes	2020-02-06 16:30:53 -05:00
Francois Belair	85784791ec	Add and have most demos use specialized agents ... The agents auto-update themselves and can calculate their velocities. This keeps the user from having to create an update_agent function. It can also save the user from having to keep track of and update velocities at all by using the provided `apply_steering` method. Closes #15, closes #16	2020-02-06 16:00:41 -05:00