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
It would be nice to be able to have effect presets in either of two forms:
A way to set default properties for a given effect. Ex: <preset wave height=30 speed=1.2>
After reading this in, all future uses of a plain <wave> will use height=30 and speed=1.2
A way to create a tag that applies a set of given effects when used. Ex: <preset dave_scared><shake size=4><smaller></preset>
After reading this in, user can use the <dave_scared> tag and anything within the tag will have the <shake size=4> and </smaller> tags applied
Notes: This can be done fairly easily by adding code for a CompoundEffect that just applies multiple effects in its own apply() function. A dev can then just register a new effect with a name for the full preset.
Doing it this way means code would have to be written for each new effect preset, whereas doing the parsing method allows non-coding individuals to create effects without assistance from development (other than, of course, the devs having to initially pass a 'preset' file into LucidText)
The text was updated successfully, but these errors were encountered:
It would be nice to be able to have effect presets in either of two forms:
<preset wave height=30 speed=1.2>
<wave>
will useheight=30
andspeed=1.2
<preset dave_scared><shake size=4><smaller></preset>
<dave_scared>
tag and anything within the tag will have the<shake size=4>
and</smaller>
tags appliedNotes: This can be done fairly easily by adding code for a
CompoundEffect
that just applies multiple effects in its ownapply()
function. A dev can then just register a new effect with a name for the full preset.Doing it this way means code would have to be written for each new effect preset, whereas doing the parsing method allows non-coding individuals to create effects without assistance from development (other than, of course, the devs having to initially pass a 'preset' file into LucidText)
The text was updated successfully, but these errors were encountered: