Difference between revisions of "Talk:Enable - ObjectReference"
Jump to navigation
Jump to search
imported>Cipscis (→Parentheses Must Be Left Blank: This note doesn't sound right to me) |
imported>HawkFest |
||
| Line 7: | Line 7: | ||
-- [[User:Cipscis|Cipscis]] ([[User talk:Cipscis|talk]]) 23:38, 13 September 2012 (EDT) | -- [[User:Cipscis|Cipscis]] ([[User talk:Cipscis|talk]]) 23:38, 13 September 2012 (EDT) | ||
:Nope I've tested it myself and it's a plain fact. Don't use anything between parenthesis (leave blank) when the reference is of type Light, else it won't do anything even though it compiles ok. Which doesn't mean to get rid of parenthesis btw if I read correctly, they're still mandatory... | |||
:--[[User:HawkFest|HawkFest]] ([[User talk:HawkFest|talk]]) 21:25, 21 November 2012 (EST) | |||
Revision as of 21:25, 21 November 2012
Parentheses Must Be Left Blank
"Lights will never fade. In order for an enable/disable function to work on a light, the enable() function must be left blank for the light to be enabled or disabled."
This note doesn't seem right to me. I know, from viewing the assembly files generated by the Papyrus Compiler, that calling Enable or Disable without parentheses is *identical* to calling them with the default value specified - the game literally has no way of telling the two apart because the same output is generated for both sets of Papyrus code.
Is it possible this note was added as the result of a false positive in testing? I can't test it myself at the moment but will when I get the chance if no one else has by then.
-- Cipscis (talk) 23:38, 13 September 2012 (EDT)
- Nope I've tested it myself and it's a plain fact. Don't use anything between parenthesis (leave blank) when the reference is of type Light, else it won't do anything even though it compiles ok. Which doesn't mean to get rid of parenthesis btw if I read correctly, they're still mandatory...
- --HawkFest (talk) 21:25, 21 November 2012 (EST)