Hosting and domain costs until October 2024 have been generously sponsored by dumptruck_ds. Thank you!
Difference between revisions of "How to edit real-time lights in FTEQW?"
From Quake Wiki
| Line 14: | Line 14: | ||
For a custom variation choose n > 11 to not override lower values, which are already in use, and assign to n the variation you want by calling lightstyle(n, [string]); characters in the string encode luminosity in ascending order, 'a' being no luminosity, 'm' being default luminosity, and 'z' being max luminosity. | For a custom variation choose n > 11 to not override lower values, which are already in use, and assign to n the variation you want by calling lightstyle(n, [string]); characters in the string encode luminosity in ascending order, 'a' being no luminosity, 'm' being default luminosity, and 'z' being max luminosity. | ||
| + | |||
| + | Note: Values for n ranging from 32 to 62 should be avoided as that range is reserved for assignments to switchable lights. | ||
Revision as of 15:44, 9 November 2022
To generate a custom coloreld light around an edict (self) use:
self.pflags = 2 (for glow on edict and models around it) or 128 (for glow on edict and all around it, models and brushes);
self.color = 'R G B';
self.light_lev = intensity/radius;
If you want the glow to vary, set
self.style = n;
For a custom variation choose n > 11 to not override lower values, which are already in use, and assign to n the variation you want by calling lightstyle(n, [string]); characters in the string encode luminosity in ascending order, 'a' being no luminosity, 'm' being default luminosity, and 'z' being max luminosity.
Note: Values for n ranging from 32 to 62 should be avoided as that range is reserved for assignments to switchable lights.