MLPV2 Feature Requests

Please post here for any requests for MLPV2 features. Thanks to the new 'link message button' feature, MLPV2 is easily extended to do a number of things without being an expert MLP scripter.

I'm currently not doing any custom scripting. Anyone is free to respond to any requests posted here. If I do any requested features, they'd most likely be included as part of the free distribution. I encourage others to do the same, but of it's not required.

If anyone implements a feature they'd like added to the free distribution, please post a message on the MLPV2 thread in the Scripting forum.

The ability to support props is a frequently requested feature, and MLPV2.1 (now in beta test phase) will support them. When you click a pose, if a prop is configured, it appears. When you select the next pose or hit STOP, it disappears. At most one object can be configured per pose.

It uses .PROPS* files, similar to .POSITION* files. Each line looks like this:

| mypose | myobject | <position>/<rotation>

'mypose' is the name of the pose (the button name in the POSE config in .MENUITEMS* files). 'myobject' is the name of an object in inventory. <position> and <rotation> are vectors. For a new prop, you can omit position and rotation, and the object will be rezzed at the relative coordinate <1,1,1>, with no rotation.

There are two new buttons: SaveProps and DumpProps, which are equivalent to SavePos and DumpPos (the latter was called Mem Dump in original MLP). There is no PropReset, when you do a PosReset it rereads any .PROPS* files and resets.

There is no AdjustProps button; you just move the prop and hit SaveProp.

OK, now that Mono is out, I'm contemplating new features. MLPV2 now has lots of free memory. I suspect that before it runs out of memory for poses, object inventories will be unmangeably large. (It's already a nightmare with about 100 items.)

The top one on my list is for the OPTIONS menu, a way to rotate all poses by 90 degrees on any axis. It would be similar to the current Z options to adjust the height. This would make it easier to use a pose set in a new MLP prim that's oriented differently. And it only saves one prim (because you can always just put MLP in an "engine" prim).

On a closely related issue, I'm trying to figure out a way to make it so that it's not too difficult to combine modules (config & anim file sets) set up with different prim rotations on the same bed. That gets kinda sticky, though. The hardest part is figuring out how to make it easy for the end customer, who's trying to add a module to an existing item.

Other possibilities are:

- mixed number of avs in a menu, so you could have a couples pose in a 4some menu. The more I think about this, the less I like it. I suppose the unused balls would go to default pose positions, rather than kicking avs off.

- poseball offsets per pose/animation, to work around the 'buried poseball' problem. Scripting and configuration for this might get ugly. One option is another animation suffix. Another option is separate .OFFSETS* files.

- support for more avs; maybe up to 6 or 8.

- Unrelated to Mono, I'll probably be adding LMs for when avs hop on and hop off, to make it easier to add compatibility with things like xcite & sensations.

Any comments or suggestions?

See


/54/77/281237/1.html

for other feature requests that have been made, but please post new ones here.

Thanks!
Jeff