Papyrus Naming Conventions

Revision as of 02:32, 29 June 2016 by imported>Domius (Created page with "== Naming Convention used in Events: == ---- *Generally: * a --> function argument * k --> object * b --> boolean * i --> integer * f --> float * s --> string * p --> pointe...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Naming Convention used in Events:


  • 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)

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