Hosting and domain costs until October 2024 have been generously sponsored by dumptruck_ds. Thank you!
Editing QuakeC Fields
From Quake Wiki
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
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 2: | Line 2: | ||
.datatype variableName; | .datatype variableName; | ||
.returntype(datatype param1) functionPointer; | .returntype(datatype param1) functionPointer; | ||
− | Note the <code>.</code> as declaring a variable without this will make it global instead of entity-specific | + | Note the <code>.</code> as declaring a variable without this will make it global instead of entity-specific. |
System fields are fields defined within the engine itself and must be present for the game to work. These are always defined after the system global fields. The end of them is denoted by the <code>void end_sys_fields;</code> declaration. System fields must always be declared in the order defined within the vanilla QuakeC files as they are linked by memory offsets internally. Changing the order will break logic. | System fields are fields defined within the engine itself and must be present for the game to work. These are always defined after the system global fields. The end of them is denoted by the <code>void end_sys_fields;</code> declaration. System fields must always be declared in the order defined within the vanilla QuakeC files as they are linked by memory offsets internally. Changing the order will break logic. |