MML Content Requests

[MetaZoneio]

1. Sticky platforms instead of sliding off including rotation:
   1. <m-cube friction=”1”> 100% sticky, player stays on platform (ideally default)
   2. <m-cube friction=”0”> 0% sticky, player slides off platform no matter platform speed
2. Colors with alpha channel color="#rgba" or color="rgba(r,g,b,a)" for making transparent objects, or fading out objects
   1. <m-sphere color="#ffffff00"> invisible white sphere
   2. <m-sphere color="rgba(255,255,255,150)"> partially transparent white sphere
3. PNG transparency support in <m-image>
4. Collision layers specified for <m-model>
   1. Ideal default any mesh with _collider in the name should be collision enabled, anything without that is not collision enabled.
   2. Alternate dynamic specified desired collision mesh naming <m-model collide_mesh="*_collide">
5. Click or not click enabled via new attribute interact by default true
   1. interact="true" click actions are absorbed, a button behind it would not be clicked
   2. interact="false click actions are passed through object, a button behind the object would be clickable
6. MML content in <m-frame> should allow to be limited to a cube, auto hides any content outside the limit cube:
   1. <m-frame limit=”[width,height,depth]”> a cube with width for x axis, height for y axis, and depth for z axis
7. UI capable within MML content <m-ui src=”…/uifile.html”>
   1. No src link provided, instead uses inner html as the UI

     <m-ui>
          <div>Hello world!</div>
     </m-ui>
   

   2. Alternative from displaying this directly on the web view is to display in world just for a client in a floating pane that perhaps follows the player.

[MetaZoneio]

Marcus L — 01/15/2024 2:53 PM via Discord
Thanks for all of these. We're thinking about a lot of the same things 😄

1. I'm currently implementing "sticky" platforms in the 3D web experience (independent of any changes to MML) such that any moving surface you're standing on will move you. Do you have a use case that I can use to explore the zero friction (non-sticky) surfaces?

2. This is currently mostly achievable using opacity and it can be animated alongside color. The one thing I'd add is that opacity is consistent across other non-primitive elements like m-model. Is there a reason you'd like the alpha/opacity to be in color?

3. This is actually a bug and has been fixed and is awaiting release in the next version: Fix m-image transparency support (#140) #141 🎉

4. This is a feature that can go in a lot of directions. I'd initially say that I'd look to make it customizable with attributes rather than a naming convention, and ideally have the room for options such as specifying a different file/mesh as well as some filter/modifier on the src-provided mesh(es).

5. I think this is necessary, but not sure about the name. "interact" is potentially overloaded/generic, but touch/click are too prescriptive about how the pointing and triggering was done.

6. We're on the same page about this. I've just added something along the lines of your comment above to the existing issue: m-frame constraints (Schema + Web) #59

7. The main challenge with 2D HTML UI is cross-platform support. Based on some preliminary exploration it seems a lot harder to get 2D HTML into the 3D render, but it makes sense to at least support floating / popup windows triggered by MML so I'd propose starting there. There's an issue here: Open Link / Popup on click #143.

If you can, please open discussions here with any additional context: https://github.com/mml-io/mml/discussions which will be easier to keep track of.

[MetaZoneio]

1. Looking great. Only zero friction scenario is if you make a platform at an angle you could customize that the player cannot climb it due to no friction. Customizing how slippery a surface is would allow for Ice like platforms where the player slides from their own momentum. Basically allowing for more customizable games/experiences.

2. Oh didn't notice opactiy, that works! Would be great if we could get this in <m-model> as well.

3. Great its been fixed.

4. I would be careful with external file for collision mesh because one it makes it harder for artists to manage, and two because of animations may need to be synchronized with the collision layer. I like the filter/modifier that could be specified in code.

5. Perhaps just onPointerDown="false" could work, so click down actions would be ignored and passed through object.

6. Great, yes this one is one of the important ones.

7. I imagine there is a way to stream a backend rendered HTML file screenshot to a 3D client, hmm would need to be per player so client side rendered is better. But yes floating / popup windows could work, also being able to attach them to the player somehow in preparation for VR, like on the player's wrist.