[X] I searched for the issues, and made sure there were no duplicates.
[X] I agree the terms, and understand that my suggestion is not guaranteed to be added or addressed.
What problem motivated you to submit the suggestion?
Currently, trying to use a variable in a comment command results in an error.
Suggestion / Solution
Porting them over to custom methods would allow variables to be used as custom methods already allow usage of them.
I believe it'd be most useful for the ()=>trueCameraMove and ()=>create commands as they seem to be the only (known) commands that can use numbers and don't have a custom method equivalent (unlike ()=>shockwave and their equivalent custom methods)
Alternatives & Workarounds
both ()=>trueCameraMove(0, f0, 0, 1, Linear) and ()=>trueCameraMove(0, {f0}, 0, 1, Linear) throw an error, the one shown higher up. There doesn't seem to be a trueCameraMove custom method yet either.
Please Check
What problem motivated you to submit the suggestion?
Currently, trying to use a variable in a comment command results in an error.
Suggestion / Solution
Porting them over to custom methods would allow variables to be used as custom methods already allow usage of them.
I believe it'd be most useful for the
()=>trueCameraMoveand()=>createcommands as they seem to be the only (known) commands that can use numbers and don't have a custom method equivalent (unlike()=>shockwaveand their equivalent custom methods)Alternatives & Workarounds
both
()=>trueCameraMove(0, f0, 0, 1, Linear)and()=>trueCameraMove(0, {f0}, 0, 1, Linear)throw an error, the one shown higher up. There doesn't seem to be a trueCameraMove custom method yet either.Demo & Mockup
No response
Note
No response