ETPub

このページは編集途中です
使用するバージョンは安定版のetpub 0.8.1
0.9.1向けに書き直します...X(
ちなみにomni-botを使ってサーバーにbotを導入したい場合はomni-bot 0.80を使用する必要があるので注意
サーバーのバージョンに対するomni-botのバージョンについての解説は
http://www.omni-bot.com/wiki/index.php?title=Download_Omni-Bot_ET


今回使用する原文
http://etpub.org/e107_plugins/wrap/wrap.php?3
ETPubをダウンロードした際に付属されている解説ファイルを使用します


他のMODの解説でも役に立つ項目が多々あります
困ったときは見てみるのもありです
http://shin.jp.land.to/wiki/index.php?FrontPage


解釈に間違いがあるかも知れないので注意
例はデフォルト値ではありません
英語で書き残されている部分は翻訳できず意味がわからないところです

g_shrubbot [filename]

shrubbotを有効にしたいときは[filename]の部分にファイル名を入れる

 

例

set g_shrubbot "shrubbot.cfg"

 

g_logAdmin [filename]

shrubbotを有効にした状態でshrubbotコマンドのログを取りたいときは[filename]の部分にログファイルの名前を入れる

 

例

set g_logAdmin "admin.log"

 

g_hitsounds [integer]

ヒットサウンド関係
以下の項目を有効にできる

1	ヒットサウンドを有効にする
2	倒れてるplayerに対してのヒットサウンドを無効にする?
4	倒れてるplayerに対してのヘッドショットのサウンドを無効にする
8	チームメイトにダメージを与えたときに"hold your fire"ってならないようになる
16	毒注射のヒットサウンドを無効にする

 

例

set g_hitsounds 17

 

g_shoveSound [string]

プッシュしたときの音を指定できる

 

例

set g_shoveSound "sound/weapons/grenade/gren_throw.wav"

 

g_poisonSound [string]

毒注射を使われた時の音を指定できる

 

例

set g_shoveSound "sound/player/gurp2.wav"

 

g_fightSound [string]

マッチ開始時のFight!って音を指定できる

 

例

set g_fightSound "sound/world/rooster.wav"

 

g_knifeKillSound [string]

ナイフでkillされたときになる音を指定できる

 

例

set g_knifeKillSound "sound/osp/goat.wav"

 

g_firstBloodSound [string]

戦闘が始まって最初のkillをしたときに流れる音を指定できる

 

例

set g_firstBloodSound "sound/misc/firstblood.wav"

 

g_playDead [0:無効 - 1:有効]

死んだふりを有効にするかどうか

 

例

set g_playDead 1

 

g_shove [integer]

プッシュ力

 

例

set g_shove 80

 

g_shoveNoZ [0:有効 - 1:無効]

上方向へのプッシュを有効にするかどうか

 

例

set g_shoveNoZ 0

 

g_dragCorpse [0:無効 - 1:有効]

gibまちの状態のplayerをuse(fキー)で引っ張れる(引きずれる)かどうか

 

例

set g_dragCorpse 1

 

g_classChange [0:無効 - 1:有効]

死んでいる見方から服を取ってクラスチェンジできるようにするかどうか

 

例

set g_classChange 1

 

g_forceLimboHealth [0 - 1]

0なら3発で、1なら5発でgibを取れるようになる？

 

例

set g_forceLimboHealth 1

 

g_privateMessages [0:無効 - 1:有効]

1にするとプライベートメッセージが使えるようになる

 

例

set g_privateMessages 0

 

使用例

/m uniplat konna gameni majininattyatte dousunno?

 

g_privateMessageSound [string]

プライベートメッセージを受け取ったときに鳴らすサウンドを指定できる

 

例

 set g_privateMessageSound "sound/misc/pm.wav"

 

g_XPSave [integer]

XP保存関係

1	ディスコネクト時にXPを保存する
2	シャッフルとかマップリセットとかでXPをリセットしないようにする
4	どんな時でもXPをリセットしない
8	GUIDがかぶってるplayerを切断するようにする IPアドレスが変わってもXPを損失しない? sv_wwwDlDisconnectedが無効になっていればこの値は自動で有効になる sv_wwwDlDisconnectedが有効ならこの値は有効にしないことを推奨
16	restart,nextmap,mapvote,campaignvoteとかの時にXPを保存する

 

例

 set g_XPSave 23

 

g_XPSaveFile [string]

XPをセーブするファイルの指定

 

例

set g_XPSaveFile "xpsave.cfg"

 

g_XPSaveMaxAge_xp [integer]

XPの保存期間

 

例

set g_XPSaveMaxAge_xp "1o" - 1ヶ月
set g_XPSaveMaxAge_xp "2w" - 2週間
set g_XPSaveMaxAge_xp "5d" - 5日
set g_XPSaveMaxAge_xp "36h" - 36時間
set g_XPSaveMaxAge_xp "120m" - 120分

 

g_XPSaveMaxAge [integer]

skills、killrating、playerrating、muteの保存期間

 

例

set g_XPSaveMaxAge_xp "1o" - 1ヶ月
set g_XPSaveMaxAge_xp "2w" - 2週間
set g_XPSaveMaxAge_xp "5d" - 5日
set g_XPSaveMaxAge_xp "36h" - 36時間
set g_XPSaveMaxAge_xp "120m" - 120分

 

g_XPDecay [integer]

XPが減っていく設定関係

1	XP減少設定を有効にする
2	サーバーに接続していないplayerからはXPを減らさない
4	playerが使っているクラスのXPは減らさない
8	specterの時はXPを減らさない
16	warmup中はXPを減らさない
32	playerがどちらかのチームに属していればXPを減らさない
64	プレイ中はBattle SenseのXPを減らさない
128	プレイ中はLight WeaponsのXPを減らさない

 

例

set g_XPDecay 0

 

g_XPDecayRate [float]

XPが減っていく設定が有効な時
XPが減っていくレートを指定できます

 

例

set g_xpDecayRate "5000/o" - 月に5000XP減らす
set g_xpDecayRate "1000/w" - 週に1000XP減らす
set g_xpDecayRate "500/d" - 日に500XP減らす
set g_xpDecayRate "40/h" - 時間ごとに40XP減らす
set g_xpDecayRate "2/m" - 分ごとに2XP減らす

 

g_XPDecayFloor [float]

XPが減っていく設定が有効な時
減っていく最小値を指定できる

 

例

set g_XPDecayFloor 0.0

 

g_maxXP [integer]

XPが指定の量たまるとリセットする設定

 

例

set g_maxXP 10000

 

g_maxXPResetWarn [integer]

XPリセットの値に近づいてきたら警告を出します
リセットの値を超えると秒ごとに警告を出すようになります

 

例

set g_maxXPResetWarn 0

 

g_damageXP [integer]

ダメージを与えるとXPがもらえます

0	無効
1	ダメージをg_damageXPLevelで指定された値与えると1XPもらえます 与えられるXPは使用している武器種によって違います
2	ダメージをg_damageXPLevelで指定された値与えると1XPもらえます 与えられるXPはBattle Senseに分類されます

 

例

set g_damageXP 0

 

g_damageXPLevel [integer]

g_damageXPのXP指定ができます

 

例

set g_damageXPLevel 50

 

g_weapons [bitmask]

shrubmodのg_weaponsと設定が同じ？です
兵器関係の設定

1	レベル0のFOは双眼鏡を持てません
2	水の中でも注射器が使えます
4	水の中でもペンチが使えます
8	空爆が失敗した時はパワーゲージを回復させます
16	空爆が失敗した時はパワーゲージを半分だけ回復させます
32	アーマーを拾った時にヘルメットも回復させます
64	双眼鏡をドロップします
128	レベル4のソルジャーはピストルをなくさない＝SMGを持てない？
256	garandを途中でリロードできます
512	axisとalliesのライフルのバランスをとります
1024	モーター用にヒットボックスを作り窓なんかを通して室内にモーターをぶち込まれるのを防ぎます
2048	死体にナイフを使用してもヘッドがでないようにする？

 

例

set g_weapons 814

 

g_mg42 [bitmask]

MG42関係の設定

1	MGでヘッドショットが出るようになる
2	弾のリロードがいつでもできるようになる

 

例

set g_mg42 2

 

g_goomba [integer]

相手の上に落下した時にダメージを与える設定です

 

例

set g_goomba 5

 

g_goombaFlags [integer]

落下ダメージの詳細設定

1	チームメイトに落下ダメージを与えません
2	飛び乗った方のplayerはダメージを受けません
4	チームメイトに飛び乗った方のplayerはダメージを受けません
8	飛び乗るplayerは両方共ダメージを受けない
16	飛び乗られたほうは蘇生まち状態になる
32	死体が飛んできてもダメージを受けない

31に設定するとshrubetのようになる

 

例

set g_goombaFlags 31

 

g_spawnInvul [integer]

リスしたあとの無敵時間の設定

 

例

set g_spawnInvul 3

 

g_alliedSpawnInvul

リスしたあとのallies側の無敵時間の設定

 

例

set g_alliedSpawnInvul| 0

 

g_axisSpawnInvul [integer]

リスしたあとのaxis側の無敵時間の設定

 

例

set g_axisSpawnInvul 0

 

g_spawnInvulFair [0:無効 - 1:有効]

無敵時間に発砲すると無敵じゃなくなる

 

例

set g_spawnInvulFair 1

 

g_spinCorpse [0:無効 - 1:有効]

有効にすると蘇生まちの状態でくるくる回転することができます

 

例

g_spinCorpse 1

 

g_teamChangeKills [0:無効 - 1:有効]

無効の状態だとplayerがチームをごとに記録がリセットされます

 

例

g_teamChangeKills 1

 

g_ATB [0 - 1 - 2]

オートチームバランス関係
これが入ってると強制的にチームを入替させられたりする？

 

g_ATB_diff [integer]

g_ATB controls the type of active team balancing you want to use. Active team balancing will automatically move one of the top three player(s) from the team more likely to win, to the team more likely to lose. There are currently two versions. One uses XP, the other playerrating. Set g_ATB to choose between them. Note that g_ATB only decides WHEN to move a player, and NOT which player to move. See g_ATB_rating to see how ATB chooses which player to move.

0	No active team balancing.
1	Use team XP to balance the teams. Uses the following cvars:&br ;g_ATB_minXP [integer] g_ATB_minPlayers [integer] g_ATB_axisHoldoff [integer] g_ATB_alliedHoldoff [integer] Active Team Balance watches the team XP during the match and will force one of the top 3 players from the dominant team to switch teams when his/her team hits it's respawn time if the following criteria is met: 1. One team has at least g_ATB_minXP (default 300) team XP. 2. There are at least g_ATB_minPlayers (default 5) players playing 3. The resulting team change will not give one team an advantage by number of players unless: 1. If 16 or more people are playing, the losing team may get up to a 1 player advantage. 2. If 26 or more people are playing, the losing team may get up to a 2 player advantage. 4. The winning team is ahead in team XP by a margin of g_ATB_fidd percent. For example, setting g_ATB_diff 50 a player would be moved if he/she was the top player on the team and his/her team had 750XP and the other team had 500XP. You can also adjust the rate at which ATB moves players with the g_ATB_axisHoldoff (default 5) and g_ATB_alliedHoldoff (default 5) cvars. For example, if g_ATB_axisHoldoff is set to 5 and an axis player is moved to the allied team, ATB will take no other action until the axis spawn timer cycles 5 times. NOTE: this calculation is based on TeamXP NOT the total XP of all the players on the team. TeamXP is the total score earned for the team by all players on the team during the map. When a player changes teams, the TeamXP they earned for their team does not move with them. Default values: g_ATB_diff: 70 g_ATB_minXP: 300 g_ATB_minPlayers: 5 g_ATB_axisHoldoff: 5 g_ATB_alliedHoldoff: 5
2	Use player rating to balance the teams. This will balance the teams by moving one of the the top 3 players when the probability of one team winning exceeds g_ATB_diff. g_ATB_diff is an integer and defaults to 70 meaning 70%. If the Axis team has more than a 70% chance of winning, ATB will move one of its players to the Allies, and this will often instantly lower the probability enough that another move will not be necessary. This version will not use any of the XP version's variables and it uses g_playerRating_minplayers instead of g_ATB_minPlayers as the minimum number of players that must be playing before it will act. It will also not swap players between teams since unbalanced team numbers is fine with player rating. It will actually stack team numbers on purpose to even out the teams unless g_ATB_swap is set. Note: Read g_teamForceBalance_playerrating carefully also. You probably don't want to turn option 2 on until after running your server long enough to learn map and player stats. NOTE: If you set g_ATB to 2, g_ATB_rating must have a value of 4 and g_shuffle_rating must have a value of 4 or 5 or ATB will be hyperactive and ineffective. For this reason, when g_ATB is 2, g_ATB_rating is forced to have a value of 4, and if g_shuffle_rating does not have a value of 4 or 5, it is forced to have a value of 5

g_ATB_swap [1 - 0]

If set to 1, one of 3 loweset scoring players on the losing team will be moved to the winning team when ATB acts (unless the losing team has less players).

g_ATB_offtime [integer]

Sets the time in minutes after the beginning of the map, that ATB should be disabled. Set to 0 to don't disable ATB after a certain amount of time

g_ATB_rating [integer]

Sets the rating system used by Active Team Balance. This is how ATB chooses which players to move, it is NOT how ATB decides WHEN to move them. That is g_ATB. The following options are supported:

1	Use player XP
2	Use the rate at which players have gained XP since connecting.
3	Use the killRating (g_killRating must be nonzero)
4	Use the playerRating (g_playerRating must be nonzero)

NOTE: When g_ATB is set to 2, g_ATB_rating is forced to have a value of 4

g_shuffle_rating [integer]

シャッフルの基準になる設定

1	XPで判断
2	接続して以来playerが獲得しているXPのレートで判断
3	killRatingで判断
4	playerRatingで判断
5	playerRatingUseで判断 ただしmapも考慮する？

注意: ATBが2であるときは4か5に設定しなければならない

 

例

g_shuffle_rating 5

 

g_maxTeamLandmines [integer]

チームで使える地雷の最大数

 

例

g_maxTeamLandmines 10

 

team_maxPanzers [integer]
team_maxMortars [integer]
team_maxFlamers [integer]
team_maxMG42s [integer]
team_maxGrenLaunchers [integer]

チームで使える兵器の最大数の設定
％をつけると少ない人数でも使うことができる？
％ーだと一定の人数までしか使えないようになる？

 

例

team_maxPanzers "1" ( panzが一本使える )
team_maxPanzers "10%" ( 人が少なくてもpanzが一本使える )
team_maxPanzers "10%" ( 人が10人になるとpanzが一本使える )

 

g_mapConfigs [string]

マップコンフィグフォルダの指定

 

例

g_mapConfigs "mapconfig"

 

g_packDistance [integer]

パックが飛ぶ距離
0にするとetmainのようになる

 

例

g_packDistance 200

 

g_dropHealth [integer]

medがgibされたときに放出するパックの数

 

例

g_dropHealth 4

 

g_dropAmmo [integer]

foがgibされたときに放出するパックの数

 

例

g_dropAmmo 4

 

g_tossDistance [integer]

g_dropHealthとg_dropAmmoの射出される速度

 

例

g_tossDistance 200

 

g_logOptions [integer]

shrubmodのg_logOptionsにあわせてある
以下の値をサポート

1	敵を殺した時に画面中央にkillメッセージを表示せず？チャット欄にログを流す？ g_obituary 3である必要がある
2	アドレナリンのカウントダウンを表示する
4	タップのなにかを非表示にする？
8	BANしたやつが接続してきたときのメッセージを表示しない
16	gibの表示(log)を無効にする("<victim> was gibbed by <attacker>")
32	アイテムを拾ったログを取らないようにする
128	GUIDを記録する
256	プライベートメッセージを記録する
512	リアルタイムログ…多分ログファイルに時間を書き込むってことだと思う
2048	Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier.g_obituary 3である必要がある

 

例

g_logOptions 428

 

g_censor [string]

禁止ワードを設定できる

 

例

g_censor "fuck,noob"

 

g_censorNames [string]

禁止ネームを設定できる

 

例

g_censorNames "uniplat,mizo"

 

g_censorPenalty [bitmask]

多分上2つの設定に引っかかったときにどうするか決めれるものだと思う
以下の値をサポート

1	playerをkillさせる
2	g_censorNamesを含んでいるplayerを蹴る
4	killさせる…がgibはしない
8	g_censorMuteTime分だけmuteする
16	g_censorXPで指定している分のXPを減らす
32	燃やす

 

例

g_censorPenalty 56

 

g_censorNeil [0:無効 - 1:有効]

Neil Torontoさんが作ったセンサーを有効にする

 

例

g_censorNeil 1

 

g_censorNeilNames [1

0] |
Neil Torontoさんが作ったネームセンサーを有効にする

 

例

g_censorNeilNames 1

 

g_censorMuteTime [integer]

センサーでのmuteの時間をしていする
g_censorPenaltyで8を有効にしている必要がある

 

例

g_censorMuteTime 60

 

g_censorXP [integer]

センサーで引っかかったときにXPを減らす量を指定できる
g_censorPenaltyで16を有効にしている必要がある

 

例

g_censorXP "9999"

 

g_intermissionTime [integer]

戦闘結果画面の時間

 

例

g_intermissionTime 30

 

g_intermissionReadyPercent [integer]

戦闘結果画面で何人readyしたら次のマップへ移動するかのパーセント

 

例

g_intermissionReadyPercent 100

 

g_skills [integer]

次の値を有効にできる

1	battle senseが4になると敵の地雷を発見できる
2	engのレベルが4になるとengの防弾チョッキを他のクラスでも使える
4	medレベル4なら黄色の注射で蘇生されても体力全快になる

 

例

g_skills 7

 

g_hitboxes [integer]

ヒットボックスの設定
以下の値をサポート
デフォルトでは全て有効になっている
0にするとETMAINとおなじになる

1	lower the standing player's body hitbox to the shoulders.
2	lower the crouching player's body hitbox to the shoulders.
4	lower the wounded player's body hitbox to a reasonable height
8	lower the prone player's body hitbox to a reasonable height
16	lower the playdead player's body hitbox to a reasonable height

 

例

g_hitboxes 31

 

g_misc [integer]

いろんな値を有効にできる
以下の値をサポート

1	二段ジャンプを有効にする
2	双眼鏡マスターを有効にする(結果画面で出てくるあれ) g_weapons 64が有効になっている必要がある
4	殺された時に相手のHPを表示する
8	自分へのダメージを無効にする(地雷とかグレとかパンツとか)
16	スタミナがないときはジャンプできない
32	蘇生まちの状態や死んだふり状態の時のplayerにはヘッドショットを当てれない
64	落下ダメージ無効(クシャってなるのは変わらない)
128	リスタイムをアナウンスする？？？？
256	Considers heads, bodies, and leg boxes in collision detections.
512	Stock Et prone box height.
1024	Old crouch box height (= crouch viewheight).

 

例

g_misc 109

 

g_skipCorrection [0:無効 - 1:有効]

Neil Torontoさんの作ったetproのantiwarpに似たものを有効にする

 

例

g_skipCorrection 1

 

g_maxWarp [integer]

ワープの許容回数？

 

例

g_maxWarp 4

 

g_teamDamageRestriction [integer]

チームメイトに一定以上のダメージを与えると蹴られるようにする？
パーセントで設定する
g_minhitsが設定されてる必要がある
コンソールに/damageと打ちこむと現在自分が見方に与えたダメージが表示される？

 

例

g_teamDamageRestriction 0

 

g_minHits [integer]

ここで設定した値を超えると蹴られる？？

 

例

g_minHits 0

 

g_autoTempBan [bitmask]

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds

1	Tempban when reaching g_teamDamageRestriction
2	Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds
4	Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

 

g_autoTempBanTime [integer]

The number of seconds kicked for when g_autoTempBan is set
Default is 1800

 

g_voting [integer]

Voteのオプションみたいな

1	これを有効にするとVoteの際投票に参加した人数で決定するようになる
2	votes that pass do not count against the vote_limit for the caller.
4	これを有効にするとVoteのメッセージの最後に" (called by NAME)"がつくようになる
8	Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

 

例

g_voting 5

 

g_moverScale [float]

動くものが速くなる
タンクとかトラックとか...

 

例

g_moverScale 1.5

 

g_poison [integer]

毒注射のダメージ設定
ちなみにここで設定されている値/s

 

例

g_poison 20

 

g_poisonFlags [integer]

毒注射の詳細設定

1	打たれた側のプレイヤーの画面が揺れる
2	他のプレイヤーが打たれたプレイヤーを見たときに頭が揺れてるように見える
4	打たれたプレイヤーは周りから見て2秒ごとに屈んでるように見える、ただし打たれた本人からはそう見えない
8	打たれると武器等が使用不可になる、ただし打たれた本人から見ると武器を使用出来ているように見える
16	打たれると視点が逆さまになる

 

例

g_poisonFlags 31

 

g_slashKill [bitmask]

/killの詳細設定

1	/kill後の復活時のパワーゲージが半分になる
2	/kill後の復活時のパワーゲージがなくなる
4	/kill後の復活時に/kill前のパワーゲージを復活させる(死んでいる間の時間は関係なく死亡前のパワーゲージを修復する)
8	Disable /kill when player is frozen
16	毒注射を撃たれたプレイヤーは/killできない

 

例

g_slashKill 4

 

g_maxSelfkills [integer]

1MAP内で/killできる回数
"-1"で無制限
0で/killの無効化

 

例

g_maxSelfkills -1

 

g_ammoCabinetTime [integer]
g_healthCabinetTime [integer]

アモ(ヘルス)ラックの回復速度(秒)

 

例

g_ammoCabinetTime 30000
g_healthCabinetTime 30000

 

g_spectator [integer]

spectatorの設定

1	When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.
2	When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.
4	When the player you're following goes into limbo, don't move to the next available player.
8	When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

g_medics [bitmask]

メディックの詳細設定

1	MEDは自分の毒を治すためにパックを拾うことができない
2	MEDは自分のパックを拾うことができない
4	lv4のMEDは黄色の注射器で組成されてもHP全開になる
16	スキルレベルが上がってもMEDはハンドガンしか選択できなくなる？
32	MEDはハンドガンの状態でリスしてSMGを拾うことができなくなる ただしg_classChangeが有効の時に見方のMEDの服を奪ってMEDになった場合はSMGを所持できる
64	HPが減っている見方に対して注射を使うことができる
128	lv4のMEDは見方にalt-fireボタンでアドレナリンを注射できる or with the /adrenother client command.
256	lv4のMEDは自分にアドレナリンを打てない これを有効にするとMEDがlv4になってもアドレナリンを所持しなくなる

 

例

g_medics 257

 

g_medicHealthRegen [integer]

MEDの自動回復の設定(/s)

0	3/2
1	2/2
2	2/1
3	2/0
4	1/1
5	1/0
6	0/0 (no health regeneration)
7	0/1
8	0/2

 

例

g_medicHealthRegen 0

 

g_coverts [bitmask]

COの詳細設定

1	lv4のCOの武器の集弾がよくなる？
2	lv4FOのみがCOの変装を見破れる？
4	サッチェルを使った後、自動的にメイン武器に入れ替わるようにする
8	Coverts in disguise take half the normal combat damage.
16	Coverts in disguise take no splash damage.
32	撃っているところを見られても変装がとけない？
64	サイレンサーがついていない武器を使っても変装がとけない
128	固定MGを使っても変装がとけない(撃つのとは別)
256	建築物をつくるところに？スモークをたくとXPがたまる
512	敵に武器を使っているところを見られると変装がとける？？
1024	変装している状態で変装できる(服の入れ替え的な？)

 

例

g_coverts 1927

 

g_truePing [0 - 1]

正確なpingを表示するか否か

 

例

g_truePing 1

 

g_dropObj [integer]

オブジェを落とせる回数？？？？？

g_doubleJumpHeight [float]

二段ジャンプの二段目の高さ

 

例

g_doubleJumpHeight 1.3

 

skill_soldier [string]
skill_medic [string]
skill_engineer [string]
skill_fieldops [string]
skill_covertops [string
skill_battlesense [string]
skill_lightweapons [string]

スキルレベルの設定

 

例

skill_soldier "10 20 30 40"

 

g_serverInfo [bitmask]

serverInfoの設定？

1	Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)
2	Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)
4	Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.
8	Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.
16	Starting with 0.5.1, the class charge times will not be present in the server info string unless this flag is set. They were removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.
32	Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.
64	Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

 

例

g_serverInfo 1

 

g_killRating [bitmask]

この値が0じゃないときはELOタイプ統計値?を利用してkillRateを算出する？？

1	Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it.
2	Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall.
4	Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier.

 

例

g_killRating 3

 

未編集部分

g_playerRating [bitmask]

When not set to 0 etpub will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).
Here are the bitflag options:

1	Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it.
2	Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player.
4	Put player rating on the scoreboard instead of the XP. This setting will likely go away when a new version of the etpub client has this built-in
8	Print out extra info at the end of a round that can be used to further refine the playerrating model.
16	The same as flag 8 except a lot more info is output
32	Track player rating changes on a per-skill basis

 

例

g_playerRating 3

 

g_playerRating_mapPad [integer]

On an etpub installation with little statistics history, !howfair will not print out very accurate data. g_playerRating_mapPad is a cvar that attempts to stabilize early !howfair results by adding a number of fake wins to each team. If you set it to 50, it starts with Axis = 50, Allies = 50 wins. This yields a map rating of 50% for both teams on that map. For every 2 real games played, 1 map pad value is ignored. So after 100 games, map pad is ignored (replaced with real games).
The higher map pad, the longer the values will stay near 50-50.

 

例

g_playerRating_mapPad 50

 

g_playerRating_minplayers [integer]

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

 

例

g_playerRating_minplayers 8

 

g_teamForceBalance_playerrating [0..100]

Set to 0 to disable. If this setting is enabled, it overrides g_teamForceBalance. If g_teamForceBalance_playerrating is non-zero, etpub will not allow players to join a team whose chances of winning are already above g_teamForceBalance_playerrating. The winning chance is calculated using 3 things: the average player rating of the team, the number of players on each team, and how often each team wins the current map (e.g. Allies usually win tc_base). If the team being joined rates too highly, a message will tell the player to join the other team.
Important Notes:
First of all, g_teamForceBalance_playerrating WILL allow unbalanced numbers to offset map or team difficulty. If the Axis has VERY good players, it will allow the Allies to have a few more players than Axis, given a map that is equally difficult for both sides to win. Also, given teams equal in skill, g_teamForceBalance_playerrating will force Allies to have a large team if the map is almost always won by Axis.
Because g_teamForceBalance_playerrating uses info tracked over time, it may be best to run through your cycle or campaign a few times without it before turning it on, so that it can learn how good the players are, and how hard the maps are.
If you want an idea why it's working a certain way, use the !listteams command server console (or game). This will show you how many points each team is predicted to win. If a team is going to win less than 4 points, it's too good. The other information shows you the breakdown of how the points are calculated.

Ratings       Win Prob       Win Points
---------------------------------------------
Allies          0.65            5
Axis            0.35           10

The above says that Axis has a 35% chance of winning based on the players and map. It takes into account the number of players per team also. The points are calculated as 16*(1 - win prob). So there you have it.
Remember, g_teamForceBalance_playerrating is contantly adapting, so if it seems dumb at first, give it some time to adapt to your server. Maybe don't turn it on for the first week.
See also !listteams.
See also g_ATB.
Recommended Setting when used: 60

 

例

g_teamForceBalance_playerrating 0

 

g_stats [integer]

This is a bitflag cvar used to control the way statistics are handled. The following flags are supported:

1	When shooting a corpse to gib, do not count it as a hit.
2	When shooting a corpse to gib, do not count it as a shot.

Set this to 3 to use the behaviour of etmain and shrubet.

 

例

g_stats 0

 

g_tyranny [0 - 1]

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.
Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.
g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.
'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.
NOTE: If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting
set g_tyranny 1
in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message
g_tyranny is read only.

 

例

g_tyranny 0

 

g_mapScriptDirectory [string]

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts.
For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'etpub' directory and add:
set g_mapScriptDirectory "etpromapscripts"
to your cfg.
NOTE: It is strongly recommended that you use the map scripts distributed with etpub since these updated scripts fix very important bugs in some of the original map scripts.
Setting g_mapScriptDirectory to "" disables any use of map .script files.

 

例

g_mapScriptDirectory ""

 

g_campaignFile [string]

Similar to ETPro's b_campaignFile. If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored.
This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign. Such information includes:
will not display in the VOTE -> MAP list
map locations will not draw on the map of Europe.
campaign description will not draw in the right panel
total number of maps and current maps order in the campaign will not be shown in the intermission screens.
Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.
Setting this to "" disables it.

 

例

g_campaignFile ""

 

vote_allow_surrender [1 - 0]
vote_allow_nextcampaign [1 - 0]
vote_allow_restartcampaign [1 - 0]
vote_allow_poll [1 - 0]
vote_allow_maprestart [1 - 0]
vote_allow_shufflenorestart [1 - 0]
vote_allow_cointoss [1 - 0]
vote_allow_putspec [1 - 0]

(allow players to vote other player into spec)
Cvars that restrict the rights of players to use the respective /callvote command.

 

例

vote_allow_surrender 1
vote_allow_nextcampaign 1
vote_allow_restartcampaign 1
vote_allow_poll 1
vote_allow_maprestart 1
vote_allow_shufflenorestart 1
vote_allow_cointoss 1
vote_allow_putspec 1

 

g_fear [integer]

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.
As of 0.7.2, g_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.
In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.
Set this to 0 to disable this behaviour.

 

例

g_fear 2000

 

g_obituary [integer]

This cvar controls how player Obituaries are handled. Obituarys are the messages normally printed in the cpm space with a skull next to them to notify all players of another player's death.
Available options are:

0	Obituaries are disabled.
1	All Obituaries will ALWAYS be handled by the client with the EV_OBITUARY event. Since the etmain client does not know about some etpub MODs (e.g. MOD_GOOMBA) the default message will be printed for those deaths.
2	Only those Obituaries that the etmain client knows how to handle will be handled by the client. If someone is killed by a MOD that the etmain client doesn't know about, the Obituary is generated by the server.
3	All Obituaries are handled by the server and the EV_OBITUARY event is never sent to the client. This results in "Instant Obituaries". This comes at the cost of increased network bandwidth and absence of the skull icon in the obituaries. (when using this option, you can use Custom Obituaries starting with 0.6.1)

See also g_logOptions.

 

例

g_obituary 2

 

g_minAirstrikeTime [integer]

The time (in seconds) that must elapse between airstrikes PER TEAM.

 

例

g_minAirstrikeTime 10