Hosting and domain costs until October 2024 have been generously sponsored by dumptruck_ds. Thank you!
Difference between revisions of "Talk:Map based hacks"
From Quake Wiki
(Created page with "Should this page be purely about tricks that involve using info_notnull and calling various functions in the qc for different effects? Or should we also include other tricks s...") |
(→info_notnull: new section) |
||
| Line 1: | Line 1: | ||
Should this page be purely about tricks that involve using info_notnull and calling various functions in the qc for different effects? Or should we also include other tricks such as getting something to float in the air by using a temporary platform that is killed at startup? There are probably quite a lot of tricks of both types. | Should this page be purely about tricks that involve using info_notnull and calling various functions in the qc for different effects? Or should we also include other tricks such as getting something to float in the air by using a temporary platform that is killed at startup? There are probably quite a lot of tricks of both types. | ||
| + | |||
| + | == info_notnull == | ||
| + | |||
| + | You can't actually create every other possible entity out of an info_notnull, for example it's impossible to create a monster using one. The section about using them needs to take a less bombastic tone, and emphasise that as a blank slate you have freedom to set every field as you choose, but observe that without the appropriate QC functions setting fields may not be sufficient. Examples include setting a model or a bounding box on an entity; setting the corresponding fields does not update the necessary internal engine state and fails to have the desired effect. | ||
Latest revision as of 02:28, 19 November 2015
Should this page be purely about tricks that involve using info_notnull and calling various functions in the qc for different effects? Or should we also include other tricks such as getting something to float in the air by using a temporary platform that is killed at startup? There are probably quite a lot of tricks of both types.
info_notnull[edit]
You can't actually create every other possible entity out of an info_notnull, for example it's impossible to create a monster using one. The section about using them needs to take a less bombastic tone, and emphasise that as a blank slate you have freedom to set every field as you choose, but observe that without the appropriate QC functions setting fields may not be sufficient. Examples include setting a model or a bounding box on an entity; setting the corresponding fields does not update the necessary internal engine state and fails to have the desired effect.