Difference between revisions of "Papyrus Naming Conventions"
Jump to navigation
Jump to search
imported>Domius |
imported>Domius |
||
Line 9: | Line 9: | ||
* p --> pointer (carryover from internal code, inconsistency, should not be used) | * p --> pointer (carryover from internal code, inconsistency, should not be used) | ||
* r --> reference (carryover from internal code, inconsistency, should not be used) | * r --> reference (carryover from internal code, inconsistency, should not be used) | ||
Example: | |||
Function MyFunction(int myNum, akActionRef) | |||
ak = Function Argument Object. | |||
SmkViper helped flesh out this list. | SmkViper helped flesh out this list. |
Revision as of 07:53, 29 June 2016
- Generally:
- a --> function argument
- k --> object
- b --> boolean
- i --> integer
- f --> float
- s --> string
- p --> pointer (carryover from internal code, inconsistency, should not be used)
- r --> reference (carryover from internal code, inconsistency, should not be used)
Example:
Function MyFunction(int myNum, akActionRef) ak = Function Argument Object.
SmkViper helped flesh out this list. There doesn't appear to be any conformity to conventions with regard to local and script variables.
However:
- Properties tend to be upper CamelCase.
- Script variables tend to be upper CamelCase.
- Local variables tend to be lower camelCase.
- ReferenceAlias properties always have the "Alias_" prefix.
source: http://afkmods.iguanadons.net/index.php?/topic/4417-papyrus-naming-conventions/ There might be more in Fallout 4, these are from Skyrim