You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling a blueprint function with a return value results in having to syntax it as follows:
newvar = uobject.somefunction()[0]
Even if there is only one return value, a tuple is returned.
I also ran into an issue with input arrays always being return as out parameters, so the previous function would need to be written differently to get the return value:
Is there some way to disable this at the expense of allowing multiple return values? I'm okay with losing that functionality considering I'm using this plugin to allow users to create mods, and I think the awkward syntax caused by returning tuples will only lead to confusion among modders.
The text was updated successfully, but these errors were encountered:
(I'm not a project dev, so take the following as unofficial)
If you don't mind applying a couple of patches, give #626 and #635 a try - with them you don't need to do the [0] syntax and they add support for multiple output parameters, which get passed back as additional return values.
Calling a blueprint function with a return value results in having to syntax it as follows:
newvar = uobject.somefunction()[0]
Even if there is only one return value, a tuple is returned.
I also ran into an issue with input arrays always being return as out parameters, so the previous function would need to be written differently to get the return value:
newvar = uobject.somefunction(['listelement1', 'listelement2'])[1]
Is there some way to disable this at the expense of allowing multiple return values? I'm okay with losing that functionality considering I'm using this plugin to allow users to create mods, and I think the awkward syntax caused by returning tuples will only lead to confusion among modders.
The text was updated successfully, but these errors were encountered: