Rublight "fade speed" should be replaced by "fade time"

[Alasdairbugs]

v0.6.3-beta.1.2-gdb0689f97

This also applies to a lot of things with objects. "speed" has no intrinsic meaning. Who is supposed to know what a "speed" is, this isn't intuitive.

Should be changed to "fade time" as in the time it takes to full fade from its light source to 0. theres other cases where speed makes sense, in platforms, where you might want to keep speed the same, however, it doesn't make sense with some objects, this being one.

High values of fade time would be a direct correlation with longer pulses of light, and not an inverse correlation, which is the opposite of what people normally expect when mindlessly increasing a number, so it brings less hassle.

[Alasdairbugs]

this also occurs with crystallo "radius" which has an arbitrary value.

[KelvinShadewing]

I don't see why this is an issue. It isn't hard to imagine how long a fade would take if you know the speed.

[Alasdairbugs]

? "speed" has no units. its arbitrary. same with crystallo "radius" and wisp despawn "distance". all of these are unintuitive and should be set to standardised units to understand within the editor, like distance should be tiles, speed is tiles per second, and time is in seconds (which it already is). its really hard to understand and sometimes, you get things tripping you up because they mean the inverse of what you were trying to do.

it is an issue because i've constantly ran into this problem while making levels

[KelvinShadewing]

Rather than change the code, they could just assign a unit to it and document it, like say "alpha per second".