Editing Custinfoparms.txt
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 7: | Line 7: | ||
<font color=green>// Contentflags</font> | <font color=green>// Contentflags</font> | ||
{ | { | ||
− | surfaceparmname | + | surfaceparmname contentflag_HEX_integer |
− | surfaceparmname2 | + | surfaceparmname2 contentflag_HEX_integer |
... | ... | ||
− | |||
} | } | ||
<font color=green>// Surfaceflags</font> | <font color=green>// Surfaceflags</font> | ||
{ | { | ||
− | surfaceparmname | + | surfaceparmname surfaceflag_HEX_integer |
− | surfaceparmname2 | + | surfaceparmname2 contentflag_HEX_integer |
... | ... | ||
− | |||
} | } | ||
− | + | HEX integer are in 0x00000000 format. | |
=== Limits === | === Limits === | ||
Line 26: | Line 24: | ||
* Blood Omnicide Q3map2 allows max 1024 custom surfaceparms | * Blood Omnicide Q3map2 allows max 1024 custom surfaceparms | ||
* Darkplaces engine allows max 256 custom surfaceparms | * Darkplaces engine allows max 256 custom surfaceparms | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− |