[QUOTE=Tom] Great demo, really cool![/QUOTE]
[QUOTE=Arima] I also think you should leave the movement of the object to the person making the game.[/QUOTE]
I wouldn't make the behavior move the object. No matter what you do, for the majority of games it's probably not quite what is needed. For example tile games just want to step a whole cell at a time, and an RTS might use a steering vehicle style. IMO the behavior should just return the list of waypoints by expressions and then the user can make the movement via events... that seems to hit the right balance between "taking care of it for the user" and "not telling the user what they want", which is the balance all of C2 has to strike just right.[/quote]
Well I strongly inspired myself of the rts behavior from CC (which I've had a lot of fun with, but also saw some of the limits).
I was aiming at proposing the maximum options/settings. (as proposing two type of walk: straight in the cell, as previously, and also the current floating one which I see potential in ^^)
Well, I'll just put more options, as well as the "don't move parent" and "return pathlist".
If I had knew this a few days ago, I wouldn't have hurt myself getting it to work
But in the same time this has been very taughtful.
[QUOTE=Ashley]There's definitely no file size limit. I guess there is a mistake in your script the minifier doesn't like. Did you read the section on Google Closure Compiler in the SDK docs?[/QUOTE]
Yep I took a look at it, I'm not sure what have "broke" it though. My runtime went above 1000 lines and the minifier just stopped working, with seemingly no output message (that's frustrating)
Anyway, I'll make sure to clean all the code before releasing the behavior and make it "closure" compliant.
I've read from all the websites and sources you pointed me to and learnt a lot quickly and quite easily.Kyatric2011-08-19 20:41:51