A huge problem I’m noticing with Verse is that fact that you still heavily rely on preconfiguring devices in the workspace prior to runtime. It baffles me that this is strictly necessary to do basic things, like determine if a player is holding a certain item. Currently, you would have to make a conditional_button, and preconfigure it ahead of time to be able to use the IsHoldingItem function to determine whether a player is holding a certain item or not in Verse code. This is not ideal.
I suggest implementing a way to directly instantiate devices during runtime, and then throw it away. This way, we’d be able to write stuff in code directly without having to bring a bunch of random devices in and tie them together.
For example, the IsHoldingItem function is directly tied to conditional-buttons. Instead of having to make a conditional-button and have it floating somewhere in my game preconfigured, I should be able to make a new one in the code directly. And I don’t mean manually. I mean it should automatically happen if IsHoldingItem is called directly on the player. The engine should know it needs to make a conditional_button to check this, and do it itself with my given Params. Then the device should be nuked after the code block is done running.
This would make programming games in UEFN and Verse alot more intuitive.
2 posts - 2 participants