I’d like for the MST 6.0 release to focus on ease of use, and reliability in high-lag environments. I’m open to rewriting pieces, if it makes them easier or simpler to explain. For example getting rid of the concept of boxing/unboxing of the performance engine.
I’ve started to capture the various ideas that may inspire the MST 6.0 release below. I’d love to hear your ideas and your feedback!
- Install the ‘never drop an invite’ system, brought over from the Choreo HUD project.
- Teach movers to register avatars who sit on them to the MST Choreo HUD, not just performance engine.
- Allow movers to be more remote-controlled (remotely set save status, and remotely set home status. Both of these may be handy for HUD control)
- Stop giving out the sync tool by default. I’m thinking this can be an option, which would allow people to choose whether to use synctools.
MST Performance Engine Improvements
- Adopt a new, improved-efficiency event scheduler from MST Choreo HUD project. Should save script time.
- Allow a method of disabling internal animation control, for if you want to use the choreo hud for animations, instead of the engine.
- Prettier texture and size for the engine
- deprecate the box/unbox functionality
- warn when multiple valid centerpoints are present
- warn when no valid centerpoints are preset (report if centerpoints are present but we’re not allowed)
- Fix the precache command so that it can be called by chat command.
- Make the menu auto-reopen after making a choice by default
- Auto stop / start the communication scripts that can be used to project voice on stage, that no everyone uses, to save script time when they aren’t in use.
- Automatically set the centerpoint name to the venue name, and vice versa
General Suite Improvements
- Include the new, mesh MST syncTool in the suite package
- Add a subfolder for venue-owner gear
- Use a new mesh box for the tools
- Document all the possible eventlist commands, similar to the MST choreo HUD.
- See if anyone wants to make quick vid tutorials