Difference between revisions of "CZCareer"

From AlliedModders Wiki
Jump to: navigation, search
(CZCareer Event)
 
(One intermediate revision 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 types are case-sensitive.}}<br><br>
+
{{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 24: Line 25:
  
 
==GOGOGO==
 
==GOGOGO==
Sent at the start of a new Condition Zero singleplayer round. The exact purpose isn't known.<br>
+
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.}}
 
{{qnotice|Has no extra arguments.}}
 
{{begin-hl1msg|GOGOGO}}
 
{{begin-hl1msg|GOGOGO}}

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:
string Type
* Parameters


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:
short Unknown


Example usage:

Name: CZCareer
Structure:
string START
short 300


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:
string GOGOGO


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:
byte Task
short Progress


Example usage:

Name: CZCareer
Structure:
string TASKPART
byte 2
short 1


TASKDONE

Used to mark the completion of a task. For example, changes INCOMPLETE on the scoreboard to COMPLETE.

Name: TASKDONE
Structure:
byte Task


Example usage:

Name: CZCareer
Structure:
string TASKDONE
byte 2


TASKUNDONE

Used to unmark the completion of a task. For example, changes COMPLETE on the scoreboard to INCOMPLETE.

Name: TASKUNDONE
Structure:
byte Task


Example usage:

Name: CZCareer
Structure:
string TASKUNDONE
byte 2


MATCH

Sent at the end of a mission, after it is finished. Appears to save the game.

Name: MATCH
Structure:
long CT Wins
long T Wins


Example usage:

Name: CZCareer
Structure:
string MATCH
long 3
long 1