WolfWiki - User contributions [en]

Configstring

2010-05-30T06:43:40Z

Locki:

__NOEDITSECTION__

Configstrings can be accessed with <code>[[Lua_Mod_API#configstrings|et.trap_GetConfigstring]]</code> and <code>[[Lua_Mod_API#configstrings|et.trap_SetConfigstring]]</code> and the [[Lua_Mod_API#string_utility_functions|String utility functions]].

==What are Configstrings==
* Configstrings are strings that are set on the server, and automatically sent to each client.
* Configstrings are often, but not always, in the form of an infostring (a backslash delimited set of key\value pairs)
* Each configstring is identified by a number, which is usually given refered to by a name #defined in the ET gamecode.
* A group of related configstrings (such as CS_PLAYERS) usually only have a symbolic name for the first value, with a number (entity number in the case of CS_PLAYERS) added to to get a particular value.
* Most configstrings have a specific meaning to the gamecode. You can use the etmain SDK find out what they do, but beware that etpro does not do things exactly the same as etmain.
* A list of configstring numbers and names can be found in [http://www.sonic.net/~rfm/et/lua/etconst.lua etconst.lua]

==User Configstring==
A user Configstring gets written in the log file with a line starting with ''UserInfoChanged'' which mustn't be mistaken for one with ''Userinfo''.

To access a user's Configstring you can't just use <code>et.trap_GetConfigstring(slotNumber)</code> but must use <code>et.trap_GetConfigstring(et.CS_PLAYERS + slotNumber)</code>.

<pitatable columns=3 headlines="key;name;description" widths="40;220;450" headerfontcolor="#FFFFFF">
n;Nick;Player nickname
t;Team;1=Axis, 2=Allies, 3=Spectators
c;Class;0=Soldier, 1=Medic, 2=Engineer, 3=FieldOps, 4=CovertOps
r;Rank;0-10
m;Medals;0=Highest Battle Sense, 1=Best Engineer, 2=Best Medic, 3=Best Field Ops, 4=Highest Light Weapons, 5=Best Soldier, 6=Best Covert Ops
s;Skills;Battle Sense, Engineering, First Aid, Signals, Light Weapons, Heavy Weapons, Covert Operations [0-4]
dn;Disguised name; Covert op disguised as...
dr;Disguised rank; Covert op disguised as rank...
w;Weapon;2=Lugar, 3=MP40, 5=Panzerfaust, 6=Flamethrower, 7=Colt, 8=Thomson 10=Sten, 23=Engineer K43, 24=Engineer M1 Garand, 25=Covert Ops M1 Garand, 31=Mobile MG42, 32=Covert Ops K43 33=FG42, 35=Mortar, 37=Akimbo Colts, 38=Akimbo Lugars, 47=Silenced Akimbo Colts, 48=Silenced Akimbo Lugars
lw;Latched weapon;Weapon on next spawn
sw;Latched secondary weapon;Secondary weapon on next spawn
mu;Muted;0=No, 1=Yes
ref;Referee;Referee status (0=not ref, 1=ref)
p;Privilege level;0=Peon, referee (vote), referee (password), semiadmin, rconauth (ETPro only)
ss;Stat Saver; Stats have been restored by stat saver, etpro only (0=No, 1=Yes)
sc;Shoutcaster;etpro only (0=No, 1=Yes)
tv;ETTV slave;etpro only (0=No, 1=Yes)
lc;?;0=?
</pitatable>

==LUA Example==
et.CS_PLAYERS = 689

-- get the name of client #3 using configstrings
local cs = et.trap_GetConfigstring(et.CS_PLAYERS + 3)
local name = et.Info_ValueForKey(cs, "n")

==Notes==
<code>et.CS_PLAYERS = 689</code> for those of you that don't use [[User:ReyalP|etconst.lua]].

Source: http://bani.anime.net/banimod/forums/viewtopic.php?t=5412

[[Category:ETPro]]
[[Category:Lua]]
[[Category:ETPro:Mods]]

Configstring

2010-05-30T06:42:13Z

Locki:

__NOEDITSECTION__

Configstrings can be accessed with <code>[[Lua_Mod_API#configstrings|et.trap_GetConfigstring]]</code> and <code>[[Lua_Mod_API#configstrings|et.trap_SetConfigstring]]</code> and the [[Lua_Mod_API#string_utility_functions|String utility functions]].

==What are Configstrings==
* Configstrings are strings that are set on the server, and automatically sent to each client.
* Configstrings are often, but not always, in the form of an infostring (a backslash delimited set of key\value pairs)
* Each configstring is identified by a number, which is usually given refered to by a name #defined in the ET gamecode.
* A group of related configstrings (such as CS_PLAYERS) usually only have a symbolic name for the first value, with a number (entity number in the case of CS_PLAYERS) added to to get a particular value.
* Most configstrings have a specific meaning to the gamecode. You can use the etmain SDK find out what they do, but beware that etpro does not do things exactly the same as etmain.
* A list of configstring numbers and names can be found in [http://www.sonic.net/~rfm/et/lua/etconst.lua etconst.lua]

==User Configstring==
A user Configstring gets written in the log file with a line starting with ''UserInfoChanged'' which mustn't be mistaken for one with ''Userinfo''.

To access a user's Configstring you can't just use <code>et.trap_GetConfigstring(slotNumber)</code> but must use <code>et.trap_GetConfigstring(et.CS_PLAYERS + slotNumber)</code>.

<pitatable columns=3 headlines="key;name;description" widths="40;220;450" headerfontcolor="#FFFFFF">
n;Nick;Player nickname
t;Team;1=Axis, 2=Allies, 3=Spectators
c;Class;0=Soldier, 1=Medic, 2=Engineer, 3=FieldOps, 4=CovertOps
r;Rank;0-10
m;Medals;0=Highest Battle Sense, 1=Best Engineer, 2=Best Medic, 3=Best Field Ops, 4=Highest Light Weapons, 5=Best Soldier, 6=Best Covert Ops
s;Skills;Battle Sense, Engineering, First Aid, Signals, Light Weapons, Heavy Weapons, Covert Operations [0-4]
dn;Disguised name; Covert op disguised as...
dr;Disguised rank; Covert op disguised as rank...
w;Weapon;2=Lugar, 3=MP40, 5=Panzerfaust, 6=Flamethrower, 7=Colt, 8=Thomson 10=Sten, 23=Engineer K43, 24=Engineer M1 Garand, 25=Covert Ops M1 Garand, 31=Mobile MG42, 32=Covert Ops K43 33=FG42, 35=Mortar, 37=Akimbo Colts, 38=Akimbo Lugars, 47=Silenced Akimbo Colts, 48=Silenced Akimbo Lugars
lw;Latched weapon;Weapon on next spawn
sw;Latched secondary weapon;Secondary weapon on next spawn
mu;?;0=?
ref;Referee;Referee status (0=not ref, 1=ref)
p;Privilege level;0=Peon, referee (vote), referee (password), semiadmin, rconauth (ETPro only)
ss;Stat Saver; Stats have been restored by stat saver, etpro only (0=No, 1=Yes)
sc;Shoutcaster;etpro only (0=No, 1=Yes)
tv;ETTV slave;etpro only (0=No, 1=Yes)
lc;?;0=?
</pitatable>

==LUA Example==
et.CS_PLAYERS = 689

-- get the name of client #3 using configstrings
local cs = et.trap_GetConfigstring(et.CS_PLAYERS + 3)
local name = et.Info_ValueForKey(cs, "n")

==Notes==
<code>et.CS_PLAYERS = 689</code> for those of you that don't use [[User:ReyalP|etconst.lua]].

Source: http://bani.anime.net/banimod/forums/viewtopic.php?t=5412

[[Category:ETPro]]
[[Category:Lua]]
[[Category:ETPro:Mods]]

Userinfo

2010-05-30T06:36:35Z

Locki:

Userinfo string mustn't be mistaken for [[Configstring]]!

In the logfile lines starting with ''ClientUserinfoChanged'' are [[Configstring]] while lines starting with ''Userinfo'' are actual Userinfo strings.

<table border="1">
<caption>Userinfo contents</caption>
<tr><th>Key</th><th>Example value</th><th>Description</th></tr>
<tr><td>cg_etVersion</td><td>ET Pro, ET 2.60</td><td>[MOD name], [ET Version]</td></tr>
<tr><td>cg_uinfo</td><td>108 0 100 1</td><td>[cg_autoreload / cg_autoactivate / cg_predictitems setting] [cl_timenudge setting] [cl_maxpackets setting] [???]</td></tr>
<tr><td>g_password</td><td>none</td><td>Unused?</td></tr>
<tr><td>password</td><td>serverPass1</td><td>Password the client connects with</td></tr>
<tr><td>cl_guid</td><td>(An ETPro GUID)</td><td>ETPro GUID</td></tr>
<tr><td>cl_anonymous</td><td>0</td><td>?</td></tr>
<tr><td>snaps</td><td>20</td><td>Snaps setting</td></tr>
<tr><td>rate</td><td>25000</td><td>Rate setting</td></tr>
<tr><td>name</td><td>EtPlayer</td><td>Name</td></tr>
<tr><td>cl_wwwDownload</td><td>1</td><td>WWW downloads enabled or not</td></tr>
<tr><td>cl_punkbuster</td><td>1</td><td>Punkbuster enabled or not</td></tr>
<tr><td>ip</td><td>127.0.0.1:27960</td><td>[IP]:[PORT]</td></tr>
<tr><td>protocol</td><td>84</td><td>82 - 2.55, 83 - 2.56, 84 - 2.60/b/d</td></tr>
<tr><td>qport</td><td>616</td><td>Randomly chosen as startup</td></tr>
<tr><td>challenge</td><td>-1865210525</td><td>Random positive 31bit integer?</td></tr>
</table>

Userinfo

2010-05-29T06:24:42Z

Locki:

Userinfo string mustn't be mistaken for [[Configstring]]!

In the logfile lines starting with ''ClientUserinfoChanged'' are [[Configstring]] while lines starting with ''Userinfo'' are actual Userinfo strings.

<table border="1">
<caption>Userinfo contents</caption>
<tr><th>Key</th><th>Example value</th><th>Description</th></tr>
<tr><td>cg_etVersion</td><td>ET Pro, ET 2.60</td><td>[MOD name], [ET Version]</td></tr>
<tr><td>cg_uinfo</td><td>108 0 100 1</td><td>[?] [?] [?] [?]</td></tr>
<tr><td>g_password</td><td>none</td><td>Unused?</td></tr>
<tr><td>password</td><td>serverPass1</td><td>Password the client connects with</td></tr>
<tr><td>cl_guid</td><td>(An ETPro GUID)</td><td>Client's ETPro GUID</td></tr>
<tr><td>cl_anonymous</td><td>0</td><td>?</td></tr>
<tr><td>snaps</td><td>20</td><td>Client's snaps setting</td></tr>
<tr><td>rate</td><td>25000</td><td>Client's rate setting</td></tr>
<tr><td>name</td><td>EtPlayer</td><td>Client's name</td></tr>
<tr><td>cl_wwwDownload</td><td>1</td><td>WWW downloads enabled or not</td></tr>
<tr><td>cl_punkbuster</td><td>1</td><td>Punkbuster enabled or not</td></tr>
<tr><td>ip</td><td>127.0.0.1:27960</td><td>[IP]:[PORT]</td></tr>
</table>

Configstring

2010-05-27T06:32:45Z

Locki:

__NOEDITSECTION__

Configstrings can be accessed with <code>[[Lua_Mod_API#configstrings|et.trap_GetConfigstring]]</code> and <code>[[Lua_Mod_API#configstrings|et.trap_SetConfigstring]]</code> and the [[Lua_Mod_API#string_utility_functions|String utility functions]].

==What are Configstrings==
* Configstrings are strings that are set on the server, and automatically sent to each client.
* Configstrings are often, but not always, in the form of an infostring (a backslash delimited set of key\value pairs)
* Each configstring is identified by a number, which is usually given refered to by a name #defined in the ET gamecode.
* A group of related configstrings (such as CS_PLAYERS) usually only have a symbolic name for the first value, with a number (entity number in the case of CS_PLAYERS) added to to get a particular value.
* Most configstrings have a specific meaning to the gamecode. You can use the etmain SDK find out what they do, but beware that etpro does not do things exactly the same as etmain.
* A list of configstring numbers and names can be found in [http://www.sonic.net/~rfm/et/lua/etconst.lua etconst.lua]

==User Configstring==
A user Configstring gets written in the log file with a line starting with ''UserInfoChanged'' which mustn't be mistaken for one with ''Userinfo''.

To access a user's Configstring you can't just use <code>et.trap_GetConfigstring(slotNumber)</code> but must use <code>et.trap_GetConfigstring(et.CS_PLAYERS + slotNumber)</code>.

<pitatable columns=3 headlines="key;name;description" widths="40;220;450" headerfontcolor="#FFFFFF">
n;Nick;Player nickname
t;Team;1=Axis, 2=Allies, 3=Spectators
c;Class;0=Soldier, 1=Medic, 2=Engineer, 3=FieldOps, 4=CovertOps
r;Rank;0-10
m;Medals;0=Highest Battle Sense, 1=Best Engineer, 2=Best Medic, 3=Best Field Ops, 4=Highest Light Weapons, 5=Best Soldier, 6=Best Covert Ops
s;Skills;Battle Sense, Engineering, First Aid, Signals, Light Weapons, Heavy Weapons, Covert Operations [0-4]
dn;Disguised name; Covert op disguised as...
dr;Disguised rank; Covert op disguised as rank...
w;Weapon;2=Lugar, 3=MP40, 5=Panzerfaust, 6=Flamethrower, 7=Colt, 8=Thomson 10=Sten, 23=Engineer K43, 24=Engineer M1 Garand, 25=Covert Ops M1 Garand, 31=Mobile MG42, 32=Covert Ops K43 33=FG42, 35=Mortar, 37=Akimbo Colts, 38=Akimbo Lugars, 47=Silenced Akimbo Colts, 48=Silenced Akimbo Lugars
lw;Latched weapon;Weapon on next spawn
sw;Latched secondary weapon;Secondary weapon on next spawn
ref;Referee;Referee status (0=not ref, 1=ref)
p;Privilege level;0=Peon, referee (vote), referee (password), semiadmin, rconauth (ETPro only)
ss;Stat Saver; Stats have been restored by stat saver, etpro only (0=No, 1=Yes)
sc;Shoutcaster;etpro only (0=No, 1=Yes)
tv;ETTV slave;etpro only (0=No, 1=Yes)
</pitatable>

==LUA Example==
et.CS_PLAYERS = 689

-- get the name of client #3 using configstrings
local cs = et.trap_GetConfigstring(et.CS_PLAYERS + 3)
local name = et.Info_ValueForKey(cs, "n")

==Notes==
<code>et.CS_PLAYERS = 689</code> for those of you that don't use [[User:ReyalP|etconst.lua]].

Source: http://bani.anime.net/banimod/forums/viewtopic.php?t=5412

[[Category:ETPro]]
[[Category:Lua]]
[[Category:ETPro:Mods]]

Configstring

2010-05-27T06:32:15Z

Locki:

__NOEDITSECTION__

Configstrings can be accessed with <code>[[Lua_Mod_API#configstrings|et.trap_GetConfigstring]]</code> and <code>[[Lua_Mod_API#configstrings|et.trap_SetConfigstring]]</code> and the [[Lua_Mod_API#string_utility_functions|String utility functions]].

==What are Configstrings==
* Configstrings are strings that are set on the server, and automatically sent to each client.
* Configstrings are often, but not always, in the form of an infostring (a backslash delimited set of key\value pairs)
* Each configstring is identified by a number, which is usually given refered to by a name #defined in the ET gamecode.
* A group of related configstrings (such as CS_PLAYERS) usually only have a symbolic name for the first value, with a number (entity number in the case of CS_PLAYERS) added to to get a particular value.
* Most configstrings have a specific meaning to the gamecode. You can use the etmain SDK find out what they do, but beware that etpro does not do things exactly the same as etmain.
* A list of configstring numbers and names can be found in [http://www.sonic.net/~rfm/et/lua/etconst.lua etconst.lua]

==User Configstring==
A user Configstring gets written in the log file with a line starting with ''UserInfoChanged'' which mustn't be mistaken for one with ''Userinfo''.

To access a user's Configstring you can't just use <code>et.trap_GetConfigstring(slotNumber)</code> but must use <code>et.trap_GetConfigstring(et.CS_PLAYERS + slotNumber)</code>.

<pitatable columns=3 headlines="key;name;description" widths="40;220;450" headerfontcolor="#FFFFFF">
n;Nick;Player nickname
t;Team;1=Axis, 2=Allies, 3=Spectators
c;Class;0=Soldier, 1=Medic, 2=Engineer, 3=FieldOps, 4=CovertOps
r;Rank;0-10
m;Medals;0=Highest Battle Sense, 1=Best Engineer, 2=Best Medic, 3=Best Field Ops, 4=Highest Light Weapons, 5=Best Soldier, 6=Best Covert Ops
s;Skills;Battle Sense, Engineering, First Aid, Signals, Light Weapons, Heavy Weapons, Covert Operations [0-4]
dn;Disguised name; Covert op in disguide as...
dr;Disguised rank; Covert op disguised as rank...
w;Weapon;2=Lugar, 3=MP40, 5=Panzerfaust, 6=Flamethrower, 7=Colt, 8=Thomson 10=Sten, 23=Engineer K43, 24=Engineer M1 Garand, 25=Covert Ops M1 Garand, 31=Mobile MG42, 32=Covert Ops K43 33=FG42, 35=Mortar, 37=Akimbo Colts, 38=Akimbo Lugars, 47=Silenced Akimbo Colts, 48=Silenced Akimbo Lugars
lw;Latched weapon;Weapon on next spawn
sw;Latched secondary weapon;Secondary weapon on next spawn
ref;Referee;Referee status (0=not ref, 1=ref)
p;Privilege level;0=Peon, referee (vote), referee (password), semiadmin, rconauth (ETPro only)
ss;Stat Saver; Stats have been restored by stat saver, etpro only (0=No, 1=Yes)
sc;Shoutcaster;etpro only (0=No, 1=Yes)
tv;ETTV slave;etpro only (0=No, 1=Yes)
</pitatable>

==LUA Example==
et.CS_PLAYERS = 689

-- get the name of client #3 using configstrings
local cs = et.trap_GetConfigstring(et.CS_PLAYERS + 3)
local name = et.Info_ValueForKey(cs, "n")

==Notes==
<code>et.CS_PLAYERS = 689</code> for those of you that don't use [[User:ReyalP|etconst.lua]].

Source: http://bani.anime.net/banimod/forums/viewtopic.php?t=5412

[[Category:ETPro]]
[[Category:Lua]]
[[Category:ETPro:Mods]]

Configstring

2010-05-27T06:30:46Z

Locki:

__NOEDITSECTION__

Configstrings can be accessed with <code>[[Lua_Mod_API#configstrings|et.trap_GetConfigstring]]</code> and <code>[[Lua_Mod_API#configstrings|et.trap_SetConfigstring]]</code> and the [[Lua_Mod_API#string_utility_functions|String utility functions]].

==What are Configstrings==
* Configstrings are strings that are set on the server, and automatically sent to each client.
* Configstrings are often, but not always, in the form of an infostring (a backslash delimited set of key\value pairs)
* Each configstring is identified by a number, which is usually given refered to by a name #defined in the ET gamecode.
* A group of related configstrings (such as CS_PLAYERS) usually only have a symbolic name for the first value, with a number (entity number in the case of CS_PLAYERS) added to to get a particular value.
* Most configstrings have a specific meaning to the gamecode. You can use the etmain SDK find out what they do, but beware that etpro does not do things exactly the same as etmain.
* A list of configstring numbers and names can be found in [http://www.sonic.net/~rfm/et/lua/etconst.lua etconst.lua]

==User Configstring==
A user Configstring gets written in the log file with a line starting with ''UserInfoChanged'' which mustn't be mistaken for one with ''Userinfo''.

To access a user's Configstring you can't just use <code>et.trap_GetConfigstring(slotNumber)</code> but must use <code>et.trap_GetConfigstring(et.CS_PLAYERS + slotNumber)</code>.

<pitatable columns=3 headlines="key;name;description" widths="40;220;450" headerfontcolor="#FFFFFF">
n;Nick;Player nickname
t;Team;1=Axis, 2=Allies, 3=Spectators
c;Class;0=Soldier, 1=Medic, 2=Engineer, 3=FieldOps, 4=CovertOps
r;Rank;0-10
m;Medals;0=Highest Battle Sense, 1=Best Engineer, 2=Best Medic, 3=Best Field Ops, 4=Highest Light Weapons, 5=Best Soldier, 6=Best Covert Ops
s;Skills;Battle Sense, Engineering, First Aid, Signals, Light Weapons, Heavy Weapons, Covert Operations [0-4]
dn;Disguised name;
dr;Disguised rank;
w;Weapon;2=Lugar, 3=MP40, 5=Panzerfaust, 6=Flamethrower, 7=Colt, 8=Thomson 10=Sten, 23=Engineer K43, 24=Engineer M1 Garand, 25=Covert Ops M1 Garand, 31=Mobile MG42, 32=Covert Ops K43 33=FG42, 35=Mortar, 37=Akimbo Colts, 38=Akimbo Lugars, 47=Silenced Akimbo Colts, 48=Silenced Akimbo Luagrs
lw;Latched weapon;Weapon on next spawn
sw;Latched secondary weapon;Secondary weapon on next spawn
ref;Referee;Referee status (0=not ref, 1=ref)
p;Privilege level;0=Peon, referee (vote), referee (password), semiadmin, rconauth (ETPro only)
ss;Stat Saver; Stats have been restored by stat saver, etpro only (0=No, 1=Yes)
sc;Shoutcaster;etpro only (0=No, 1=Yes)
tv;ETTV slave;etpro only (0=No, 1=Yes)
</pitatable>

==LUA Example==
et.CS_PLAYERS = 689

-- get the name of client #3 using configstrings
local cs = et.trap_GetConfigstring(et.CS_PLAYERS + 3)
local name = et.Info_ValueForKey(cs, "n")

==Notes==
<code>et.CS_PLAYERS = 689</code> for those of you that don't use [[User:ReyalP|etconst.lua]].

Source: http://bani.anime.net/banimod/forums/viewtopic.php?t=5412

[[Category:ETPro]]
[[Category:Lua]]
[[Category:ETPro:Mods]]

Extended ASCII

2009-11-01T10:43:34Z

Locki:

== Extended ASCII Characters in ET Pro 3 ==

In ET Pro 3.0.1, you are finally able to use extended ASCII characters and quotation marks in chats.

Not all of these characters exist in all of ET's fonts. The following table shows which characters can be used in each area.

<table>
<th>Console</th><th>Chat</th><th>Popup</th><th>/name</th>
<tr>
<td>00 - FF</td><td>00, 0A, 0D, 20-7E, A0-FF</td><td>?</td><td>?</td>
</tr>
</table>

You can use a two-character hex code preceeded by ''='' (as shown in the script below) to represent the ASCII character. If you try to use these in game (e.g. ''/vsay =aaHELLO=ab'') you'll soon find that it won't display them right away. This is because the in-game commands automatically convert the extended ascii characters. To bypass the automatic encoding (and allow the use of the raw hex characters), you'll have to run them through ''cmd'' - such as ''/cmd vsay hi =aaHELLO=ab''. Without the essential ''cmd'', your characters will come out completely normal.

The following script displays every available ASCII character in the chat and console area. You must have a map running for the "say" command to work, ''b_floodKickBurst'' at least ''22'' and ''b_floodMaxCommands'' at least ''18'' due to the length of the script.) :

<pre>
cmd say "=20=20=20=20^z0 1 2 3 4 5 6 7 8 9 a b c d e f"
cmd say "=20=20=20=20^?-------------------------------"
cmd say "^z0 ^?| ^2=00 =01 =02 =03 =04 =05 =06 =07 =08 =09 =0a =0b =0c =0d =0e =0f"
cmd say "^z1 ^?| ^2=10 =11 =12 =13 =14 =15 =16 =17 =18 =19 =1a =1b =1c =1d =1e =1f"
cmd say "^z2 ^?| ^2=20 =21 =22 =23 =24 =25 =26 =27 =28 =29 =2a =2b =2c =2d =2e =2f"
cmd say "^z3 ^?| ^2=30 =31 =32 =33 =34 =35 =36 =37 =38 =39 =3a =3b =3c =3d =3e =3f"
cmd say "^z4 ^?| ^2=40 =41 =42 =43 =44 =45 =46 =47 =48 =49 =4a =4b =4c =4d =4e =4f"
cmd say "^z5 ^?| ^2=50 =51 =52 =53 =54 =55 =56 =57 =58 =59 =5a =5b =5c =5d =20 =5f"
cmd say "^z6 ^?| ^2=60 =61 =62 =63 =64 =65 =66 =67 =68 =69 =6a =6b =6c =6d =6e =6f"
cmd say "^z7 ^?| ^2=70 =71 =72 =73 =74 =75 =76 =77 =78 =79 =7a =7b =7c =7d =7e =7f"
cmd say "^z8 ^?| ^2=80 =81 =82 =83 =84 =85 =86 =87 =88 =89 =8a =8b =8c =8d =8e =8f"
cmd say "^z9 ^?| ^2=90 =91 =92 =93 =94 =95 =96 =97 =98 =99 =9a =9b =9c =9d =9e =9f"
cmd say "^za ^?| ^2=a0 =a1 =a2 =a3 =a4 =a5 =a6 =a7 =a8 =a9 =aa =ab =ac =ad =ae =af"
cmd say "^zb ^?| ^2=b0 =b1 =b2 =b3 =b4 =b5 =b6 =b7 =b8 =b9 =ba =bb =bc =bd =be =bf"
cmd say "^zc ^?| ^2=c0 =c1 =c2 =c3 =c4 =c5 =c6 =c7 =c8 =c9 =ca =cb =cc =cd =ce =cf"
cmd say "^zd ^?| ^2=d0 =d1 =d2 =d3 =d4 =d5 =d6 =d7 =d8 =d9 =da =db =dc =dd =de =df"
cmd say "^ze ^?| ^2=e0 =e1 =e2 =e3 =e4 =e5 =e6 =e7 =e8 =e9 =ea =eb =ec =ed =ee =ef"
cmd say "^zf ^?| ^2=f0 =f1 =f2 =f3 =f4 =f5 =f6 =f7 =f8 =f9 =fa =fb =fc =fd =fe =ff"
</pre>

Extended ASCII

2009-11-01T09:46:44Z

Locki:

== Extended ASCII Characters in ET Pro 3 ==

In ET Pro 3.0.1, you are finally able to use extended ASCII characters and quotation marks in chats. Not all of these characters exist in all of ET's fonts (e.g. some will display properly in the console while others will not.)

You can use a two-character hex code (as shown in the script below) to represent the ASCII character.

If you try to use these in game (e.g. /vsay =aaHELLO=ab) you'll soon find that it won't display them right away. This is because the in-game commands automatically convert the extended ascii characters. To bypass the automatic encoding (and allow the use of the raw hex characters), you'll have to run them through ''cmd'' - such as ''/cmd vsay hi =aaHELLO=ab''. Without the essential cmd, your characters will come out completely normal.

The following script displays every available ASCII character in the chat area (you must have a map running for the "say" command to work, and flood-protection CVAR's disabled due to the length of the script) :

<pre>
cmd say "=20=20=20=20^z0 1 2 3 4 5 6 7 8 9 a b c d e f"
cmd say "=20=20=20=20^?-------------------------------"
cmd say "^z0 ^?| ^2=00 =01 =02 =03 =04 =05 =06 =07 =08 =09 =0a =0b =0c =0d =0e =0f"
cmd say "^z1 ^?| ^2=10 =11 =12 =13 =14 =15 =16 =17 =18 =19 =1a =1b =1c =1d =1e =1f"
cmd say "^z2 ^?| ^2=20 =21 =22 =23 =24 =25 =26 =27 =28 =29 =2a =2b =2c =2d =2e =2f"
cmd say "^z3 ^?| ^2=30 =31 =32 =33 =34 =35 =36 =37 =38 =39 =3a =3b =3c =3d =3e =3f"
cmd say "^z4 ^?| ^2=40 =41 =42 =43 =44 =45 =46 =47 =48 =49 =4a =4b =4c =4d =4e =4f"
cmd say "^z5 ^?| ^2=50 =51 =52 =53 =54 =55 =56 =57 =58 =59 =5a =5b =5c =5d =20 =5f"
cmd say "^z6 ^?| ^2=60 =61 =62 =63 =64 =65 =66 =67 =68 =69 =6a =6b =6c =6d =6e =6f"
cmd say "^z7 ^?| ^2=70 =71 =72 =73 =74 =75 =76 =77 =78 =79 =7a =7b =7c =7d =7e =7f"
cmd say "^z8 ^?| ^2=80 =81 =82 =83 =84 =85 =86 =87 =88 =89 =8a =8b =8c =8d =8e =8f"
cmd say "^z9 ^?| ^2=90 =91 =92 =93 =94 =95 =96 =97 =98 =99 =9a =9b =9c =9d =9e =9f"
cmd say "^za ^?| ^2=a0 =a1 =a2 =a3 =a4 =a5 =a6 =a7 =a8 =a9 =aa =ab =ac =ad =ae =af"
cmd say "^zb ^?| ^2=b0 =b1 =b2 =b3 =b4 =b5 =b6 =b7 =b8 =b9 =ba =bb =bc =bd =be =bf"
cmd say "^zc ^?| ^2=c0 =c1 =c2 =c3 =c4 =c5 =c6 =c7 =c8 =c9 =ca =cb =cc =cd =ce =cf"
cmd say "^zd ^?| ^2=d0 =d1 =d2 =d3 =d4 =d5 =d6 =d7 =d8 =d9 =da =db =dc =dd =de =df"
cmd say "^ze ^?| ^2=e0 =e1 =e2 =e3 =e4 =e5 =e6 =e7 =e8 =e9 =ea =eb =ec =ed =ee =ef"
cmd say "^zf ^?| ^2=f0 =f1 =f2 =f3 =f4 =f5 =f6 =f7 =f8 =f9 =fa =fb =fc =fd =fe =ff"
</pre>