Triggers

Kartenspezifischen eigenen Skript-Code unten eingeben. Dieser Text wird in das Karten-Skript nach der Deklaration der Variablen und vor jeglichem Auslöser-Code eingefügt.

This is quite straightforward. The first part gives the colour strings to be used in the whole game, used in the Chat trigger.
The next part adds each player to his/her own private chat group, so that they can see their own private chat.
The next part is entirely self explanatory. It simply displays commands and features of the system, and their function.
The next part of it is for a "quest" displaying each player's number, to be used for the -add#/-remove# command, for the private chat list. Not everyone knows each player's number, which is why this "quest" exists, as well as the -nl/-nlist command.

The triggering of this system is quite simple.
Event: obvious. When any player types anything, the trigger runs a check if the message did not have any of the messages in the string (substrings referring to a part of a string, ie. sub of a string. The substring takes the first number and begins the substring there and ends at the second number). Should this pass, the first check is if the message contains a -p at the start (first two letters), which is the command for a private chat. Should this condition be true, the message displayed to the players inside the variable player group PrivateGroup[number of triggering player(ie. person saying something)] will be the following 'formula':

[ |cffD6AE12(Private) - |r ] - the first concenate string (concenate strings are a series of strings). The text in front of the bracket is the colour code in which (Private) will be coloured, (Private) refers to the fact that this is a private message. |r displays the end of the colour string.
[ + ColourString[(Player number of (Triggering player))]) ] - the second concenate string. This will decide the colour of the player's name in the private message. ColourString[] is an array variable (ie a 'stack' of variables of the same type) which has 12 values. Each of these 12 values is set at the very beginning of the game, player 1 (red)'s, [1], is set to red, player 2 (blue)'s, [2], is set to blue and so on. This way, the trigger takes the player's number and puts it into this array, giving the correct colour for the player name.
[ + Name of (Triggering player) ] - this is the third part. The name of the player in the message will be decided by it - its colour already decided by the string before this one.
[ + (|r: ] - this is a simple colour string stop and :, displaying the end of the player name (and the colour of it) and the start of the message, with a : and a space (giving a less cluttered look)
[ + Substring(Entered chat string), 3, 90) ] - this is the most important part of the action. It displays the actual message.

(last line) ... [ + Substring(Entered chat string), 3, 90) ] - this is the most important part of the action. It displays the actual message. ...
This message will be displayed to the player group already decided and explained earlier on, along with the rest of the string, the 3, 90 is deciding the start and end of the message. 3 is after -p (which are 1, 2) and 90 is the maximum amount of characters allowed in a message, thus giving a quite long message length limit.

The All and Allies chat follow the same rule, with some exceptions:
- Player group displayed to - All displays the message to, well, ALL players. Allies only displays it to allies of the typist.
- The last part of the concenate strings (Substring(Entered chat string), #, #) - varies as in the All chat, only a . is needed to cause this, while allies is the default chat and displays all characters entered.

As you may notice, the system also does not display normal WC3 chat in game. This is because of the fact that in Advanced > Game Interface, the 5 Chat Recipient message fields have been filled with spaces, this many:
' '
If you wish to export this system to a different map, you will need to change those fields as well.

NOTE: The only difference between the normal Commands trigger and this trigger is that this one returns a confirmation message when an -add or -remove command is carried out.

The triggering of this is extremely simple as well. If you know anything about substrings, it will come quite naturally, if not, the Chat comments should be enough.
The first command is the -add: -add1-12 or -addall. -addall is the first check, and will simply take all players from 1-12 and do the actions that if they are playing and are a user (ie, not computer), they will be added to the triggering player's PrivateGroup, to which private chat is displayed with -p. -add# is simply that it will take the 5th letter of the chat command, the number being added, and run the checks for playing & user and then add this player to the triggering player's group. The next action is simply the confirmation return message, which also displays the player's colour, should the person make a mistake.
The next part, -remove, is the precise same, other than the fact that it removes players instead of adding them. During the -removeall command, ALL players are first removed, then the triggering player is put back, so that this player can see their own chat once again. For the single number removal, it also checks that the number is not the triggering player's number.
-privlist takes all the players in the triggering player's PrivateGroup and displays a message with their colour string & name to the triggering player, showing all the people in their private chat list.
-nl/-nlist simply displays the 2nd quest during Initialization.
And that's already it! :- )!