Adding entirely new "slots" to AO's (running against a wall, standing on a ledge, running at various inclines, swimming in system water) is one of the things you can only do do programmatically. But a base "animation replacer" client AO to get rid of the official animations is still handy. A script can just handle all the extra, where it's actually necessary.
On Apr 13, 2012, at 10:14 AM, Stickman <stick...@gmail.com> wrote: >> Agree. I'm one of the ones who's written a scripted AO. I tried the >> client-side AO in Firestorm and went back to my own because of the >> feature set. A server-side AO would like be even worse. > > I've written scripted AOs, and while I'm not familiar with the > clientside AOs, I know that a scripted AO is significantly more > powerful than a clientside AO on one very important point: > > A scripted AO can be quickly and easy be changed. Features can be > added or removed. Say someone has the bright idea to add extra > "one-shot" animations, such as a stumble to break up a repetitive > running cycle, it can be added without much fuss. While a clientside > AO built into the viewer, unless built in a way to support it, > couldn't do such a thing. > > More support for a clientside AO wouldn't be a bad thing. But it > couldn't, and probably shouldn't completely replace scripted AO. > > Stickman > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting privileges > _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
