Overall Feature Request/ Game Engine Functionality

General Feedback & Requests
, ,
1

Hey guys,

So to start things off i’m going to list somethings (in my opinion) that I believe need to be changed/or added into VERSE programming language to make the overall game development experience a better one

I will be starting with VERSE and its integration with UEFN in general- I will list the issue and follow it with a solution

#1 Problem. FIRSTLY I very much dislike the fact that in order to run Verse Scripts you need a DEVICE that runs inside of your level somewhere.

#1 Solution. I believe that Verse scripts should have their own section inside UEFN that run on Runtime without the need of creating a Device.

#2 Problem. This leads to the second problem. The way you have to reference objects in the outliner from a device is tedious and a drag. Creating a @editble Platform in the script then grabbing the part from the outliner and syncing it to the device.

#2 Solution. VERSE Should be able to reference all parts in the outliner (ex. game.Outliner.Platform or game.Outliner.Button) to easily find parts and or folders you want to reference in your Verse

As it currently stands Verse is missing a lot of functionality, I will just list all the things I believe It needs

  • Verse should be linked with all of UEFN and able to reference anything in the level (I.e, Outliner)
  • Verse should have the capability of Creating Objects/Parts During Runtime
  • Verse Shouldn’t even be running from MS Code and should be Running From UEFN
  • Verse Should have its own Dedicated section that runs on runtime without the need of Devices

Overall I believe Verse Should be integrated Globally throughout UEFN. Being able to spawn Items/ Objects next to the player without having to have an item spawner in the level. and able to reference objects/create objects right from the verse code.

Sorry if this is kinda all over the place, Running on 3 hours sleep. But I hope you can see the direction I’m pointing in

2

Thanks very much for your feedback.

You actually can spawn new Props from Verse, but only existing FN Props at the moment (not custom Props, made from your own meshes). There is also a limit on the number you can spawn. We hope to fix that in the future. For now, you can create a ‘pool’ of Props and Teleport them when needed.

# Spawns a `creative_prop` at the specified `Position` and `Rotation`. `Position` and `Rotation` units are in cm.
    # Returns tuple:
    #  0: Instance of a `creative_prop`. False if no `creative_prop` could be created. See `spawn_prop_result` for failure cases.
    #  1: Success or failure results.
    SpawnProp<native><public>(Asset:creative_prop_asset, Position:vector3, Rotation:rotation)<transacts>:tuple(?creative_prop, spawn_prop_result)