Hierarchy list on world build menu. A visual list where you can see and select objects and gizmo blocks from the build menu. Bonus of being able to select an object from the list and get moved to it (focus). Multi selecting of objects and operations such as lock , delete, mass properties, etc.

Script toolbox/saves for use in additional worlds without recreating or importing every time

Frequently, I want to refer to code in one script gizmo when writing another script gizmo. But you are only allowed to have one script gizmo open at a time. Opening another closes the one you currently have open. Please allow at least two open at once so that you can refer to the other code.

I would like to request that Player Persistent Variables be global (able to reference it in any world they are in, if you know the persistent variable's ID#)

Single line or block comments to temporarily disable code sections.

It gets confusing when you have multiple triggers in a world so having an option to color code trigger boxes or change the color of a trigger box to stay organized would be cool.

Allowing Horizon World creators to utilize Local Transformation space will instantly bump up the creative quality within worlds and save time for creators as well. Not providing these blocks limits a lot of creativity to only those familiar with the math required to perform local transformations.

Right now you can only store number data as a player persistent variable. If we could store other forms of data, we could create far richer experiences for returning players:

• Number (Already Amazing)
• Boolean (Save a state)
• Vector (Save positions)
• Rotation (Save orientations)
• Color (Save player's color)
• String (Save messages and much more)

If it is an option, saving a list of a single data type would also be incredible, this could enable save points that could be resumed and so much more. Thank you for considering. 😁💜

Would like to be able to set the object collidability for each player, the same way we can now set object visibility. Would make it easy to unlock areas of a map without having to use a respawn (that would reset player gravity and speed), for elligible players. I would use it to make a wall non-collidable after a player earned his/her way to another part of a world. Would couple it with a text marker/magic collapse gizmo visible only to elligible players to indicate that entrance location.

With the latest feature that allows us to attach a script to multiple objects via the selection tool, we are exteemely grateful, and wish we could also reference object variables simultaneously as well. Ie. sounds, visual effects, or even respawn points, control objects, and much more. :)

For usability and organization purposes for scripts we produce, it would be useful to be able to reorder the script variables of the script. This could be just to group similar variables together, put important variables at the top (so easier to wire), or to put internal variables at the bottom.

It would be SUPER useful if we could rename script variables after they have been created. Currently, you need to delete the variable, breaking any objects that had set values for it, and then create a new variable, and fix all the references in the script.

Add call backs for some script blocks. For instance when updating a leaderboard force a check on pass/fail if(status == success)
Do something
Else
Do something else

Ability to limit the range of the grab function.

To enable us to manage dynamic spawning within a world, please expose via scripting the capacities in each capacity area for assets, and for current world capacity in each area. So, please give us something like get <object|simulation|geometry|sound> complexity of world and another get <...> complexity of <asset>. Return a number between 0 and 1. Would also be really nice if assets details UI showed their capacity percentage factors (to several decimal places).

Currently, all object coordinate manipulation (with the exception of physics push and spin) is in global coordinates. This makes things unnecessarily complicated when dealing with objects in groups. Please allow setting position, rotation, scale based on the local coordinate system of grouped objects.