Please add native Vector and Point datatypes
Please add native vector and Point datatypes, along with all the proper logic to add, subtract, multiply, cross product, etc..
It's silly to have to work all this stuff out by hand.
Also please give us a behavior Directed Force, it'd be like Change Velocity except it runs constantly, like Constrain Attribute mixed with Change Velocity. As it is now I need to constrain both the linear velocity x and linear velocity y and work out all the math on both of them.
Ideally:
New Behavior:
Apply Force, takes one Param: Vector
See, now isn't that pretty?![:) :)](http://forums.gamesalad.com/plugins/emojiextender/emoji/twitter/smile.png)
Another New Behavior:
Change Location: takes one parameter: Point
You guys need to think higher level abstractions, GameSalad is supposed to be "Game Design for the rest of us" Right? Well, why are we mucking around with ints and floats and angles then? All the behaviors should be in relation to objects and how they interact with each other. Parameters for behaviors should be other objects.
I know you guys know this already, you couldn't have made this software without some basic OOP skills, but why did you leave basic OOP out of the tool?
Thanks, Please keep up the good work!
It's silly to have to work all this stuff out by hand.
Also please give us a behavior Directed Force, it'd be like Change Velocity except it runs constantly, like Constrain Attribute mixed with Change Velocity. As it is now I need to constrain both the linear velocity x and linear velocity y and work out all the math on both of them.
Ideally:
New Behavior:
Apply Force, takes one Param: Vector
See, now isn't that pretty?
![:) :)](http://forums.gamesalad.com/plugins/emojiextender/emoji/twitter/smile.png)
Another New Behavior:
Change Location: takes one parameter: Point
You guys need to think higher level abstractions, GameSalad is supposed to be "Game Design for the rest of us" Right? Well, why are we mucking around with ints and floats and angles then? All the behaviors should be in relation to objects and how they interact with each other. Parameters for behaviors should be other objects.
I know you guys know this already, you couldn't have made this software without some basic OOP skills, but why did you leave basic OOP out of the tool?
Thanks, Please keep up the good work!
![:) :)](http://forums.gamesalad.com/plugins/emojiextender/emoji/twitter/smile.png)
Comments