Difference between revisions of "CZCareer"
(→CZCareer Event) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
{{hl1msg|*|Parameters}} | {{hl1msg|*|Parameters}} | ||
{{end-hl1msg}} | {{end-hl1msg}} | ||
| − | {{qnotice|Using an invalid type has no repercussions whatsoever.}}<br> | + | {{qnotice|Using an invalid type has no repercussions whatsoever. Therefore, you can use this to make your own custom communications (you can send any number of arguments of any type after the first string).}}<br> |
| − | {{qnotice|The | + | {{qnotice|The Type argument is case-sensitive.}}<br> |
| + | {{qnotice|This event does nothing in CS and CZ multiplayer.}}<br><br> | ||
The Parameters will change depending on what type you use. Below are the Parameters for the known valid types. Assume that the Type for each one of them is the same as the header for that section. | The Parameters will change depending on what type you use. Below are the Parameters for the known valid types. Assume that the Type for each one of them is the same as the header for that section. | ||
| Line 17: | Line 18: | ||
{{hl1msg|short|Unknown}} | {{hl1msg|short|Unknown}} | ||
{{end-hl1msg}} | {{end-hl1msg}} | ||
| − | Example: | + | Example usage: |
{{begin-hl1msg|CZCareer|string,short}} | {{begin-hl1msg|CZCareer|string,short}} | ||
{{hl1msg|string|START}} | {{hl1msg|string|START}} | ||
| Line 23: | Line 24: | ||
{{end-hl1msg}} | {{end-hl1msg}} | ||
| − | + | ==GOGOGO== | |
| + | Sent at the start of a new Condition Zero singleplayer round (as soon as players spawn, <i>not</i> as soon as freezetime ends). The exact purpose isn't known.<br> | ||
| + | {{qnotice|Has no extra arguments.}} | ||
| + | {{begin-hl1msg|GOGOGO}} | ||
| + | {{end-hl1msg}} | ||
| + | Example usage: | ||
| + | {{begin-hl1msg|CZCareer|string}} | ||
| + | {{hl1msg|string|GOGOGO}} | ||
| + | {{end-hl1msg}} | ||
| + | |||
| + | ==TASKPART== | ||
| + | Used to update task progress. For example, on "kill X many enemy" tasks, Progress would be the amount of enemies killed so far.<br> | ||
| + | {{qnotice|The task will always appear as incomplete, regardless of Progress, until a TASKDONE is sent.}} | ||
| + | {{begin-hl1msg|TASKPART|byte,short}} | ||
| + | {{hl1msg|byte|Task}} | ||
| + | {{hl1msg|short|Progress}} | ||
| + | {{end-hl1msg}} | ||
| + | Example usage: | ||
| + | {{begin-hl1msg|CZCareer|string,byte,short}} | ||
| + | {{hl1msg|string|TASKPART}} | ||
| + | {{hl1msg|byte|2}} | ||
| + | {{hl1msg|short|1}} | ||
| + | {{end-hl1msg}} | ||
| + | |||
| + | ==TASKDONE== | ||
| + | Used to mark the completion of a task. For example, changes INCOMPLETE on the scoreboard to COMPLETE.<br> | ||
| + | {{begin-hl1msg|TASKDONE|byte}} | ||
| + | {{hl1msg|byte|Task}} | ||
| + | {{end-hl1msg}} | ||
| + | Example usage: | ||
| + | {{begin-hl1msg|CZCareer|string,byte}} | ||
| + | {{hl1msg|string|TASKDONE}} | ||
| + | {{hl1msg|byte|2}} | ||
| + | {{end-hl1msg}} | ||
| + | |||
| + | ==TASKUNDONE== | ||
| + | Used to <b>un</b>mark the completion of a task. For example, changes COMPLETE on the scoreboard to INCOMPLETE.<br> | ||
| + | {{begin-hl1msg|TASKUNDONE|byte}} | ||
| + | {{hl1msg|byte|Task}} | ||
| + | {{end-hl1msg}} | ||
| + | Example usage: | ||
| + | {{begin-hl1msg|CZCareer|string,byte}} | ||
| + | {{hl1msg|string|TASKUNDONE}} | ||
| + | {{hl1msg|byte|2}} | ||
| + | {{end-hl1msg}} | ||
| + | |||
| + | ==MATCH== | ||
| + | Sent at the end of a mission, after it is finished. Appears to save the game.<br> | ||
| + | {{begin-hl1msg|MATCH|long,long}} | ||
| + | {{hl1msg|long|CT Wins}} | ||
| + | {{hl1msg|long|T Wins}} | ||
| + | {{end-hl1msg}} | ||
| + | Example usage: | ||
| + | {{begin-hl1msg|CZCareer|string,long,long}} | ||
| + | {{hl1msg|string|MATCH}} | ||
| + | {{hl1msg|long|3}} | ||
| + | {{hl1msg|long|1}} | ||
| + | {{end-hl1msg}} | ||
Latest revision as of 16:33, 30 December 2006
CZCareer Event
This event supplies certain updates to the player regarding Condition Zero singleplayer missions. Here is its basic layout:
| Name: | CZCareer | ||||
| Structure: |
|
Note: Using an invalid type has no repercussions whatsoever. Therefore, you can use this to make your own custom communications (you can send any number of arguments of any type after the first string).
Note: The Type argument is case-sensitive.
Note: This event does nothing in CS and CZ multiplayer.
The Parameters will change depending on what type you use. Below are the Parameters for the known valid types. Assume that the Type for each one of them is the same as the header for that section.
START
Sent at the start of a Condition Zero singleplayer mission. The exact purpose isn't known.
Note: Unknown is always 300.
| Name: | START | ||
| Structure: |
|
Example usage:
| Name: | CZCareer | ||||
| Structure: |
|
GOGOGO
Sent at the start of a new Condition Zero singleplayer round (as soon as players spawn, not as soon as freezetime ends). The exact purpose isn't known.
Note: Has no extra arguments.
| Name: | GOGOGO | |
| Structure: |
|
Example usage:
| Name: | CZCareer | ||
| Structure: |
|
TASKPART
Used to update task progress. For example, on "kill X many enemy" tasks, Progress would be the amount of enemies killed so far.
Note: The task will always appear as incomplete, regardless of Progress, until a TASKDONE is sent.
| Name: | TASKPART | ||||
| Structure: |
|
Example usage:
| Name: | CZCareer | ||||||
| Structure: |
|
TASKDONE
Used to mark the completion of a task. For example, changes INCOMPLETE on the scoreboard to COMPLETE.
| Name: | TASKDONE | ||
| Structure: |
|
Example usage:
| Name: | CZCareer | ||||
| Structure: |
|
TASKUNDONE
Used to unmark the completion of a task. For example, changes COMPLETE on the scoreboard to INCOMPLETE.
| Name: | TASKUNDONE | ||
| Structure: |
|
Example usage:
| Name: | CZCareer | ||||
| Structure: |
|
MATCH
Sent at the end of a mission, after it is finished. Appears to save the game.
| Name: | MATCH | ||||
| Structure: |
|
Example usage:
| Name: | CZCareer | ||||||
| Structure: |
|
