Custinfoparms.txt

From Blood Wiki
(Difference between revisions)
Jump to: navigation, search
Line 7: Line 7:
 
  <font color=green>// Contentflags</font>
 
  <font color=green>// Contentflags</font>
 
  {
 
  {
     surfaceparmname contentflag_HEX_integer
+
     surfaceparmname integer
     surfaceparmname2 contentflag_HEX_integer
+
     surfaceparmname2 integer
 
     ...
 
     ...
 +
    surfaceparmnameX integer
 
  }
 
  }
 
  <font color=green>// Surfaceflags</font>
 
  <font color=green>// Surfaceflags</font>
 
  {
 
  {
     surfaceparmname surfaceflag_HEX_integer
+
     surfaceparmname integer
     surfaceparmname2 contentflag_HEX_integer
+
     surfaceparmname2 integer
 
     ...
 
     ...
 +
    surfaceparmnameX integer
 
  }
 
  }
  
HEX integer are in 0x00000000 format.
+
Integer are HEX values in 0x00000000 format representing surfaceflags and contentflags to be assigned with corresponding custom surfaceparm.
  
 
=== Limits ===
 
=== Limits ===

Revision as of 23:01, 22 July 2012

A script file that defines a custom surfaceparms to be used with surfaceparm keyword in materials.

This file should be created in Gamedir/basepath/scripts

Syntax of custinfoparms.txt:

// Contentflags
{
    surfaceparmname integer
    surfaceparmname2 integer
    ...
    surfaceparmnameX integer
}
// Surfaceflags
{
    surfaceparmname integer
    surfaceparmname2 integer
    ...
    surfaceparmnameX integer
}

Integer are HEX values in 0x00000000 format representing surfaceflags and contentflags to be assigned with corresponding custom surfaceparm.

Limits

  • Stock Q3map2 allows max 64 custom surfaceparms
  • Blood Omnicide Q3map2 allows max 1024 custom surfaceparms
  • Darkplaces engine allows max 256 custom surfaceparms

See also

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox