WolfWiki - User contributions [en]

User:Nano

2007-04-29T12:46:37Z

Nano:

== LUA Modules ==

* '''[http://nano.fooo.org/lua/advancedref.lua Advanced Referee 0.1]'''
** Allows you to give players referee status without sharing the referee password
** Referee login without an announcement (e.g. xyz is now a referee)
** Clients may automatically get referee status on connect
** Possibility to disable certain referee commands
** The GUID this script uses can be spoofed. An attacker may get referee rights by connecting with your GUID.

* '''[http://nano.fooo.org/lua/adrenaline.lua More Adrenaline for Medics 0.1]'''
** A small module for trickjump servers
** Gives medics on spawn a specified amount of adrenaline needles

== Tools ==

* '''[http://nano.fooo.org/etminpro/ ET Min Pro 0.1]'''
** Enemy Territory Minimizer for Windows
** Two hotkeys: ALT+Z and CTRL+ALT+M
** Gamma switching when minimizing and maximizing
** Functionality to restore default gamma after ET crashed

== Contact ==

* '''E-Mail:''' nano -at- fooo.org
* '''IRC:''' [irc://irc.quakenet.org:6667/iostream #iostream @ QuakeNet]

[[Category:ETPro:Mods]]

User:Nano

2007-04-02T19:54:42Z

Nano:

== LUA Modules ==

* '''[http://nano.fooo.org/lua/advancedref.lua Advanced Referee 0.1]'''
** Allows you to give players referee status without sharing the referee password
** Referee login without an annoucement (e.g. xyz is now a referee)
** Clients may automatically get referee status on connect
** Possibility to disable certain referee commands

* '''[http://nano.fooo.org/lua/adrenaline.lua More Adrenaline for Medics 0.1]'''
** A small module for trickjump servers
** Gives medics on spawn a specified amount of adrenaline needles

== Tools ==

* '''[http://nano.fooo.org/etminpro/ ET Min Pro 0.1]'''
** Enemy Territory Minimizer for Windows
** Two hotkeys: ALT+Z and CTRL+ALT+M
** Gamma switching when minimizing and maximizing
** Functionality to restore default gamma after ET crashed

== Contact ==

* '''E-Mail:''' nano -at- fooo.org
* '''IRC:''' [irc://irc.quakenet.org:6667/iostream #iostream @ QuakeNet]

[[Category:ETPro:Mods]]

User:Nano

2007-02-10T17:01:18Z

Nano:

== LUA Modules ==

* '''[http://nano.fooo.org/lua/advancedref.lua Advanced Referee 0.1]'''
** Allows you to give players referee status without sharing the referee password
** Referee login without an annoucement (e.g. xyz is now a referee)
** Clients may automatically get referee status on connect
** Possibility to disable certain referee commands
** Based on PunkBuster GUID

* '''[http://nano.fooo.org/lua/adrenaline.lua More Adrenaline for Medics 0.1]'''
** A small module for trickjump servers
** Gives medics on spawn a specified amount of adrenaline needles

== Tools ==

* '''[http://nano.fooo.org/etminpro/ ET Min Pro 0.1]'''
** Enemy Territory Minimizer for Windows
** Two hotkeys: ALT+Z and CTRL+ALT+M
** Gamma switching when minimizing and maximizing
** Functionality to restore default gamma after ET crashed

== Contact ==

* '''E-Mail:''' nano -at- fooo.org
* '''IRC:''' [irc://irc.quakenet.org:6667/iostream #iostream @ QuakeNet]

[[Category:ETPro:Mods]]

User:Nano

2007-01-04T15:11:29Z

Nano: new module (adrenaline.lua)

User:Nano

2006-12-09T14:34:20Z

Nano:

Headshot Mode

2006-11-19T12:39:52Z

Nano:

A '''headshot mode''' is included in [[ETPro]]. It’s controlled by the [[bitmask-cvar|bitmask cvar]] <tt style="color: green;">b_headshot</tt>:

0 = disabled
1 = only headshots do damage
2 = instagib headshots : hit = kill
4 = only clients can be damaged, not world entities (e.g. barrels)
8 = you can only receive damage from other clients, you can't receive damage from the world, e.g. from an exploding barrel

The instagib damage is controlled by the cvar <tt style="color: green;">b_instagibdamage</tt> (default: 400).

[[Category:ETPro:Server_Cvars]]

ETpro:Gameplay Changes

2006-11-16T20:53:19Z

Nano:

Gameplay changes between etmain and [[:Category:ETPro|ETPro]]:

* Players may now open doors silently by crouching and pressing <tt>+activate.</tt>
* Players may notice when they are wounded and waiting for medic, that freelook is no longer lagged. Also, the wounded freelook camera should no longer 'lock on' to non-medics.
* Players will hear "prepare to fight" when the warmup countdown begins, and "fight!" when the round starts. Players may disable this with the cvar <tt>cg_announcer</tt>.
* When a player gets a knife kill, both the attacker and the victim hear the 'OSP goat' sound. Players may disable this with the cvar <tt>b_goatsound</tt>. (sounds used from OSP with permission)
* For weapons without an alternate fire mode (non-silenced pistol, sten, thompson/mp40, etc) players may use the <tt>weapalt</tt> button to reload.
* If the server admin has enabled shoving (<tt>b_shove 1</tt>, default), players are awarded kills for shoving enemies to their death. Likewise, players are penalized with a teamkill for shoving teammates to their death.
* ETPro has now [[Hitsounds|hitsounds]] that are like those from Quake 3 Arena, which are sounds that are played when you hit somebody.
* ET Pro implements an [[AntiWarp|antiwarp system]] to keep players from "warping" or "teleporting" around, accidentally or intentionally.

User:Nano

2006-11-16T20:50:06Z

Nano:

User:Nano

2006-11-16T20:46:13Z

Nano:

Hitsounds

2006-11-14T14:35:02Z

Nano: added server configuration

'''Hitsounds''' are sounds that are played when you hit another player. There are three different sounds:

* when you hit an enemy
* when you hit an enemy in the head hitbox
* when you hit a teammate

==Client configuration==

The hitsounds are controlled by the cvar <tt style="color: green;">b_hitsounds</tt>. There are three different settings that can be used with this cvar:

0 = off, no sounds are played
1 = all sounds are played
3 = a sound occurs only when you hit the enemy's head

Of course you can also configure hitsounds using the ingame ETPro menu.

==Server configuration==

Server administrators may disable hitsounds on their server using the cvar <tt style="color: green;">b_sv_hitsounds</tt> (default 1, enable).

0 = server globally disables hitsounds
1 = server allows clients to use hitsounds

[[Category:ETPro:Client_Cvars]]

Configstring

2006-11-14T13:51:17Z

Nano: added lua example

__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 from 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.collectivecomputing.com/~reed/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;
t;Team;1=Axis, 2=Allies, 3=Spectators
c;Class;0=Soldier, 1=Medic, 2=Engineer, 3=FieldOps, 4=CovertOps
r;Rank;
m;Medals;
s;Skills;
dn;Disguised name;
dr;Disguised rank;
w;Weapon
lw;Latched weapon;Weapon on next spawn
sw;Latched secondary weapon;Secondary weapon on next spawn
p;Privilege level;0=Peon, referee (vote), referee (password), semiadmin, rconauth - etpro only
ss;Stat Saver; Stats restored by stat saver;etpro only
sc;Shoutcaster;etpro only
tv;ETTV slave;etpro only
</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]]

SemiAdmin

2006-11-07T18:18:08Z

Nano:

'''Semi Admins''' are admins who can perform only certain commands without having full referee or rcon access.
The commands each semiadmin can perform and the password each needs for logging in are defined via cvars.

==cvar overview==

{| cellspacing="2" cellpadding="2"
|- style="background: #CCCCFF;"
!width="200"|cvar
!width="100"|default
!description
|- style="background-color: #F4F4F4;"
|<tt style="color: green;">b_semiAdminLevels</tt>
|align="center"|0
|The number of semiadmin levels.
|- style="background-color: #EEEEEE;"
|<tt style="color: green;">b_semiAdminPass#</tt>
|align="center" style="color: gray;"|undefined
|Defines the password for each semiadmin level, where # is the level to set the password for.
|- style="background-color: #F4F4F4;"
|<tt style="color:green;">b_semiAdminCmds#</tt>
|align="center" style="color: gray;"|undefined
|A space-seperated list of commands a level # semiadmin can use.
|}

==cvar descriptions==

===b_semiAdminLevels===

Defines the number of semiadmin levels to use. Valid values are 0–999. The default value of 0 disables semiadmin functionality.
set b_semiAdminLevels 3 // you will have 3 semiadmin levels

===b_semiAdminPass#===

Sets the password for each semiadmin level. # is the level to set the password for. Every level must have its own password.
set b_semiAdminPass1 "foo" // foo is the password to log in as a level 1 semiadmin

===b_semiAdminCmds#===

A space-seperated list of commands a semiadmin with level # is allowed to perform. Be carefull with commands like <code>set</code>, <code>exec</code>, <code>vstr</code> etc.
set b_semiAdminCmds1 "clientkick say kick"

==Example configuration==

set b_semiAdminLevels "3" // we will have 3 semiadmin levels
set b_semiAdminPass1 "foo" // foo is the password for level 1
set b_semiAdminPass2 "bar" // the password for level 2
set b_semiAdminPass3 "foobar"
set b_semiAdminPass4 "wrong" // will not work since we have only defined 3 semiadmin levels
set b_semiAdminCmds1 "say map_restart"
set b_semiAdminCmds2 "kick say clientkick g_friendyfire" // level 2 is allowed to change the cvar g_friendlyfire
set b_semiAdminCmds3 "set kick clientkick exec"

The above lines will create 3 semiadmin levels. Each level has its own password and an own list of commands which can be used by a semiadmin with that level.

==Usage of the semiadmin functionality==

To log in as a semiadmin use the command <code>/semiadminlogin <password></code> or the shorter one <code>/sal <password></code>. Performing a command is done via the commands <code>/semiadmin <command></code> or <code>/sa <command></code>.

Some commands send information back, like the rcon command <code>status</code>. These information will not be sent back to the semiadmin.

Typing <code>/sa</code> without any parameters will give you a list of commands you’re allowed to perform.

/sal baz // login with the password baz
/semiadmin say Hello all // perform the command "say Hello all"
/sa // shows you a list of commands you’re able to perform

[[Category:ETPro]]

XP Settings

2006-11-07T16:04:22Z

Nano:

==cvar overview==

{| cellspacing="2" cellpadding="2"
|- style="background: #CCCCFF;"
!width="200"|cvar
!width="100"|default
!description
|- style="background-color: #F4F4F4;"
|<tt style="color: green;">b_statsaver</tt>
|align="center"|1
|Enables or disables the statsaver feature
|- style="background-color: #EEEEEE;"
|<tt style="color: green;">b_defaultskill</tt>
|align="center" style="color: gray;"|empty
|New players will spawn with these skill levels in each class.
|- style="background-color: #F4F4F4;"
|<tt style="color:green;">b_noskillupgrades</tt>
|align="center"|0
|Enables or disables the gaining of skill or rank upgrades.
|- style="background-color: #EEEEEE;"
|<tt style="color:green;">b_levels_<class></tt>
|align="center" style="color: gray;"|empty
|Configures the number of XP required for each class upgrade.
|}

==cvar descriptions==

===b_statsaver===

If ''b_statsaver'' is 1, then player XP, skills, medals, weaponstats, team, class, and weapon selection are all saved across disconnects. These stats will still be reset whenever the server would normally reset them (e.g. at the beginng of a new campaign).
set b_statsaver 1

===b_defaultskills===

New players start with these skill levels in each class. The classes in order are:
* battle sense
* explosives and construction (engineer)
* first aid (medic)
* signals (field ops)
* light weapons
* heavy weapons (soldier)
Therefore, to start everyone with level 2 battle sense and level 3 light weapons, you could use the following setting:
set b_defaultskills "2 0 0 0 3 0 0"
Leaving this setting blank or using 0s for each class uses the normal behavior. Valid values are 0–4 for each skill.

===b_noskillupgrades===

When set to 1, players may still score XP, but they will no longer gain skill or rank upgrades. This is especially useful in combination with [[XP_Settings#b_defaultskills|b_defaultskills]] to even out gameplay when playing in non-campaign mode.

===b_levels_<class>===

Configures the number of XP required for each class upgrade. Setting a skill level to 0 means that a player will start with that skill level, while setting a skill level to -1 or omitting it means that a skill level is disabled. A blank value means that the default values (20, 50, 90, 140) are used. Examples:
set b_levels_battlesense "20 30 60 100" // upgrade battle sense faster
set b_levels_medic "20 50 90" // disable level 4 medics

<class> is: "battlesense" or "engineer", "medic", "fieldops", "lightweapons", "soldier" or "covertops"

==XP Save==
Please note that [[ETPro]] ''does not'' contain an XP save function. It only has [[XP_Settings#b_statsaver|Stat-Saver]]

[[Category:ETPro:Server_Cvars]]

Main Page

2006-09-17T18:56:13Z

Nano: replaced table with some div layers

Welcome to
[[WolfWiki]]


<div>
<div style="width: 59%; float: left; border: 1px solid #FABD23; background-color: #FCFAE3;">
<div style="padding: .5em .9em .9em;">
__NOTOC__
==About==
[[WolfWiki]] is a collaborative site for the ETPro / ETTV / BayonET community.

==Getting Started==
Anyone with a [http://bani.anime.net/banimod/forums/ Banimod Forums] account may edit pages. If you do not have an account, you may [http://bani.anime.net/banimod/forums/profile.php?mode=register apply] for one. Please follow the [[Help:Editing]] guidelines when editing pages.
----
<center>There are currently {{NUMBEROFARTICLES}} [[:Special:Allpages|articles available]].</center>
</div>
</div>
<div style="width: 39%; float: right; border: 1px solid #3E48FB; background-color: #C5DAEB;">
<div style="padding: .5em .9em .9em;">
==[[:Category:ETPro|ETPro]]==
{{ETPro_Topics}}
==[[:Category:ETTV|ETTV]]==
[http://bani.anime.net/banimod/forums/viewforum.php?f=18 Discussion Forums] 
[[ETTV:Server Configuration|Server Configuration]] 
[[ETTV:Viewer's Guide|Viewer's Guide]] 

==[[:Category:BayonET|BayonET]]==
[http://bani.anime.net/banimod/forums/viewforum.php?f=10 Discussion Forums]

</div>
</div>
 
</div>

__NOEDITSECTION__

Banners

2006-09-17T17:47:06Z

Nano: new style, do you like it?

Admins may display banners to the clients on their server.

==cvars==

{| cellspacing="2" cellpadding="2"
|- style="background: #CCCCFF;"
!width="200"|cvar
!width="100"|default
!description
|- style="background-color: #F4F4F4;"
|<tt style="color: green;">b_banners</tt>
|align="center"|0
|Defines the number of banners you would like displayed in rotation. The default value of 0 disables banners altogether.
|- style="background-color: #EEEEEE;"
|<tt style="color: green;">b_banner<n></tt>
|align="center" style="color: gray;"|undefined
|Define the banner text, where n is 1 to whatever number you set <tt style="color: green;">b_banners</tt> to.
|- style="background-color: #F4F4F4;"
|<tt style="color:green;">b_bannerlocation</tt>
|align="center"|128
|A bitmask cvar with the locations where banners are printed. See [[Banners#Locations|Locations]] for a list.
|- style="background-color: #EEEEEE;"
|<tt style="color:green;">b_bannertime</tt>
|align="center"|0
|The time in seconds between the display of banners.
|}

==Locations==

* <tt>'''8'''</tt> - player chat area
* <tt>'''16'''</tt> - left popup area (not recommended)
* <tt>'''32'''</tt> - centered above the chat area
* <tt>'''64'''</tt> - console only
* <tt>'''128'''</tt> - banner area (recommended)

<tt style="color: green;">b_bannerlocation</tt> is a bitmask cvar. That means, you can mix the options. For example, setting the cvar to 136 will display banners at the banner area and the player chat area.

For compatibility, the old-style locations (from 0-4) are also supported.

The client defaults <tt style="color: green;">b_logbanners</tt> to 1, which effectively adds 64 to the locations list if it's not already present, so adding 64 isn't necessary unless you want to force the messages to be logged in the console.

[[Category:ETPro:Server_Cvars]]

Banners

2006-09-17T15:51:17Z

Nano: made it more fancy and hopefully semantic correct

Admins may display banners to the clients on their server.

==cvars==

;b_banners
:Defines the number of banners you would like displayed in rotation. The default value of 0 disables banners altogether. 
:(valid values: 0-999, default: 0)

; b_banner<n>
: Define the banner text, where n is 1 to whatever number you set b_banners to. For example, you could set b_banners to 2 and use the following commands to define the banner text:
: <code>set b_banner1 "This is the first banner" set b_banner2 "This is the second banner"</code>
:(default: not set)

;b_bannerlocation
:Defines the locations where banners are printed. Add together the following values:
:*'''8''' - player chat area
:*'''16''' - left popup area (not recommended)
:*'''32''' - centered above the chat area
:*'''64''' - console only
:*'''128''' - banner area (recommended)
:For compatibility, the old-style locations (from 0-4) are also supported. The client defaults to <code>b_logbanners 1</code>, which effectively adds 64 to the locations list if it's not already present, so adding 64 isn't necessary unless you want to force the messages to be logged to the console.

;b_bannertime
:The time in seconds between the display of banners.
:(default: 0)

[[Category:ETPro:Server_Cvars]]