=OVER= mrPorter #77 32 года - Евгений, Екатеринбург, д/р 05/02 =OVER= SAMLEEru#7737 лет-Олег, г.Москва д/р 16/11 =OVER= REX9895#7733 года - Андрей, г.Москва д/р 24/11 =OVER= sirex#7726лет - Сергей, г. Баку д/р 12/09 =OVER=BARABAK#7724 года - Михаил, Омск, д/р 9/11. =OVER= NOFX#7730лет - Сергей, г. Москва д/р 05/03 =OVER= AleksLee#7726 лет - Александр, г. Москва д/р 04/10 =OVER= Traktor#7730лет - Алексей, г. Москва д/р 07/05 =OVER= diplo80#7730лет - Андрей, г. Москва д/р 02/04 =OVER= hitscan495#7725лет - Александр, г. Москва д/р 12/07 =OVER= ^6Ho-Shi #7731 год - Сергей, г. Москва д/р 18/10 =OVER= =ONE EYE=#7731 год - Денис, г. Днепропетровск д/р **/** =OVER= bjack6290 #7731 год - Илья, г. Москва д/р 26/09 =OVER= Tyman O_o#7721 год - Сергей, г. Москва д/р 17/06 =OVER= Ksordus #7723 года - Сергей, г. Киев д/р 30/09 =OVER= 07 Grom#77Юрий г. Ярославль, д/р 15/03 =OVER= GRIFUS#77Юрий М.О. г. Куровское, д/р 25/10 =OVER= Faceplay.ru #77Евгений г. Москва, д/р 12/04 =OVER=Dianna Ross#77Дмитрий г.Москва
Member
Статус: Не в сети Регистрация: 06.05.2007 Откуда: Москва
во кстати, для тех кто хотел познакомиться с плагином
ProconRulz - 34a.1 Автор: bambam_ofc
ProconRulz Procon plugin You can 'right-click' and select 'Print...' to print this page.
Apply admin commands (e.g. Kill, Kick, Say) to players according to certain 'conditions' (e.g. spawned with Kit Recon) Allows programming of weapon or kit limits, with suitable messages.
actions include kick, ban, or just a warning (yell, say).
conditions include kit type, weapon type, and can be applied at Spawn time or on a Kill.
Each rule has three parts:
Trigger - i.e. when the rule should fire, On Spawn, On Kill, On Teamkill etc Conditions - list of tests to apply before actions are done, e.g. Headshot, Kit Recon etc Actions - list of admin actions to take if all conditions succeed, e.g. Kill, Kick, Say example rule: "On Spawn;Team Attack;Teamsize 8;Kit Recon 2;Say >>%p%<< Max 2 Snipers!!;Kill" which means: If player "X" has
TRIGGER = just SPAWNED CONDITION 1 = on the ATTACKING team (only applies in Rush mode) CONDITION 2 = that team has 8 OR FEWER PLAYERS CONDITION 3 = the player has spawned as a RECON and there are already 2 RECONS ON THE TEAM then ACTION 1 = SAY "Max 2 Snipers!" ACTION 2 = KILL player "X" after 5 seconds
most of these fields are optional, so to limit any team to 2 snipers, just use "Kit Recon 2;Say >>%p%<< Max 2 snipers!;Kill"
Also rules can be added as comments, e.g. "# the following rulz are sniper limits"
Syntax: [..] = optional part * = repeatable part | = separates alternative parts
I.e. trigger is optional (defaults to On Spawn), you can have multiple conditions including zero, and you can have multiple actions (actually including zero actions, but this has no point unless you are debugging conditions in 'Trace Rules' mode). If the first character of a rule is '#' then the rule is a comment. Rule lists can also contain empty lines for clarity (use this to separate sections of your rules).
<trigger> = "On Round" | "On Spawn" | "On Kill" | "On TeamKill" | "On Suicide"| "On PlayerBlock"| "On Join"| "On Leave"| "On Say" (rule with no trigger is the same as using On Spawn)
<condition> = (prefix with "Not " to reverse meaning) "Admin": player is a server Admin - typically use Not Admin "Admins": at least one server admin is on the server "Protected": player is on reservedslots list and protected from ProconRulz kicks and kills "Team Attack": player is an Attacker in Rush mode "Team Defend": player is a Defender in Rush mode "Teamsize <N>": smallest team has N or fewer players "Map <string>": map name or filename contains string, e.g. Map Nelson "MapMode <string>": current map mode contains string e.g. MapMode rush "On Kill;Headshot": kill was with a headshot "Kit <kit> [<N>]": player originally spawned with this kit, >N players on team with this kit incl. player "On Spawn;Weapon <weapon> [<N>]": player has this weapon, weapon limit is >N as for Kit "On Kill;Weapon <weapon> [<N>]": player has killed with this weapon >N times "On Spawn;Damage <damage> [<N>]": player has spawned with weapon that can do this damage, limit N as Kit "On Kill;Damage <damage> [<N>]": player has already done this damage N times "On Spawn;Spec <specialization> [<N>]": player has this Spec, spec limit is N "TeamKit <kit> <N>": team has >N players spawned with this kit not necessarily including current player "TeamWeapon <weapon> <N>": team has >N players spawned with this weapon not necessarily including current player "TeamDamage <damage> <N>": team has >N players spawned with weapons that do this damage not necessarily including current player "TeamSpec <specialization> <N>": team has >N players spawned with this specialization not necessarily including current player "On Kill;Range <N>": the distance of the kill was > N meters. Note BFBC2 +/- 20 meter random error "PlayerCount <N>": player has already triggered rule N times during this round: i.e. succeeds at N+1) - subst text %c% "Count <N>": same as PlayerCount "TeamCount <N>": rule hit count for Team this round, see PlayerCount - subst text %tc% "ServerCount <N>": rule hit count for Server this round, see PlayerCount - subst text %sc% "Rate <N> <M>": player has triggered this rule N times in M seconds "PlayerFirst": player has triggered this rule for their first time this round "TeamFirst": player has triggered this rule for the first time for their team this round "ServerFirst": this is the first time any player has triggered this rule this round "PlayerOnce": player has triggered this rule for the first time since joining server "On Say;Text <key>": player has just entered say text including this key string "On Say;Text <key>;TargetPlayer": A playername can be found in the say text after <key> "Ping <N>": Player ping (from last listPlayers update) is higher than N
Note: "OnSpawn;Kit Recon 2..." is equivalent to "On Spawn;Kit Recon;TeamKit Recon 2..."
<action> = "Say " <message> "PlayerSay " <message>: only the player involved will see message "VictimSay " <message>: On Kill only, the player killed will see message "AdminSay " <message>: only in-game admins will see message "Yell " <message> "PlayerYell " <message>: only the player involved will see Yell message "Log " <message>: log to procon chat log but don't use Say "Both " <message>: Say and Yell same message "All " <message>: Say and Yell and Log same message "Kill [<N>]": Kill after N milliseconds, for default see plugin setting "Kick " <message> "Ban " <message>: perm ban using EA ID "TempBan " <N> <message>: temp ban for N seconds using EA ID "PlayerBlock " <item_name>: e.g. PlayerBlock SniperRifle, PlayerBlock HG-2 "TargetAction "<action> : <action> is applied to target after confirmation "TargetConfirm": confirms target for delayed actions "TargetCancel": cancels delayed actions from this player
<N> = number (defaults to 0)
Rule order is important to avoid unreachable rules: The rules are tested in the order stored and ONLY THE FIRST ONE TO SUCCEED WILL FIRE THE ACTIONS. So it is essential a "Kit Recon 4" (meaning 4 or more Recons) rule appears before a "Kit Recon 2" rule. I.e. Kit Recon 4;Say >>%p%%<< we have more than 4 Recon class already! Kit Recon 2;Say >>%p%%<< we have more than 2 Recon class already! If the rules were reversed, the "Kit Recon 4" rule would never fire (think about it).
Similarly, the "Teamsize N" conditions (current team is smaller or equal to N) have to be in increasing of teamsize (teamsize smaller than 4 will always fire if teamsize smaller than 2 was going to fire, so putting Teamsize 4 first would mean the Teamsize 2 rule would never get fired). Teamsize 2;Kit Recon;Say >>%p%<< you just spawned as Recon with teams <= 2 players!! Teamsize 4;Kit Recon;Say >>%p%<< you just spawned as Recon with teams <= 4 players!!
Kit/Weapon counts are different for Spawn and Kill: for "On Spawn" rules, N is this player plus the number of teammates with this item. For "On Kill|TeamKill|Suicide" rules, N is the number of kills the player has with this item. "On Spawn;Kit Recon 2" means this player is a Recon, and there are more than 2 Recons currently on the team. "On Kill;Kit Recon 2" means this player is a Recon and has accumulated more than 2 kills as a Recon. For the technically minded, "On Kill;Damage SniperRifle 2;" is going to behave the same as "On Kill;Damage SniperRifle;Count 2;" even though in the first example the plugin is counting 'SniperRifle' kills, and in the second example it is counting the number of times the rule has fired - these amount to the same thing in this example.
Message substitutions Anywhere a message appears in a rule, e.g. "Say %p% just spawned", the following substitutions can be embedded in the message:
Subsitute string Meaning %p% Player name (On Spawn, or killer on a kill) %pt% Player team name, e.g. Attackers, US Army %v% Victim name (On Kill|TeamKill|Suicide rules only) %vt% Victim team name %k% Player kit on spawn, e.g. Recon (or kit associated with kill weapon) %w% Weapon (On Kill), e.g. SVU Snaiperskaya Short. Or list of weapons On Spawn. %d% Damage (On Kill) e.g. SniperRifle or VehicleHeavy. Or list of damage types On Spawn %spec% Specializations (On Spawn only) e.g. 12-Gauge Sabot Rounds %r% Range (On Kill) - note each player position is randomised by 10 meters %n% Teamsize of current smallest team %c% Count of the number of times this player has triggered this rule %tc% Count of the number of times this player's TEAM have triggered this rule %sc% Count of the number of times ALL PLAYERS ON SERVER have triggered this rule %h% Headshot (On Kill) - substituted with "Headshot" or blank %m% Map name e.g. Nelson Bay %mm% Map mode e.g. Rush %t% Target found from previous TargetPlayer condition %ping% Ping milliseconds for current player %text% Text from player On Say event in this rule
E.g. "On Kill;Say Player >>>%p%<< killed [%v%] with [%w%] (damage %d%) range %r%."
Some example rules Kit Recon 2;Say >>%p%<< Max 2 Snipers!!;Kill Max 2 Recon players on either team Team Attack;Kit Recon;Say >>%p%<< No snipers on attacking side!!;Kill No Recon players on 'attackers' team in Rush On Kill;Teamsize 4;Damage VehicleHeavy;Say No tanks until >4 players a side;Kill Killing with tank when your team is 4 players or less will be suicidal On TeamKill;Kill Teamkilling is suicidal On Suicide;Yell NOOOOOB %p% Suicided Message yelled when player suicides On Kill;Say >>%p%<< killed [%v%] with [%w%], range %r% Chats a kill message on every kill
Using 'Target' actions The Target condition and actions are designed to allow actions to be applied to players other than the %p% player that triggered the rule, e.g. to support in-game admin.
The plugin has to use a condition to extract the target for the action from somewhere, typically say text by the triggering player using the TargetPlayer condition, which sets up a %t% substitution variable for use in messages and also as the 'target' for TargetAction actions.
The following rules would implement an in-game-admin 'xkill' command:
On Say;Admin;Text xkill;TargetPlayer;PlayerSay did you mean %t% (xyes/xno)?;TargetAction Kill; On Say;Text xyes;TargetConfirm; On Say;Text xno;TargetCancel;
Note that we avoided a rule such as "On Say;Text no;..." because this would fire EVERY time a player say ANYTHING with 'no' as a substring, e.g. "I am from Norway". We used "xno" instead.
List of all weapons, kits and specializations Kits Description Kit key No kit None Assault Assault Special Ops Specialist Engineer Demolition Medic Support Recon Recon
Member
Статус: Не в сети Регистрация: 20.07.2010 Откуда: Киев
2 дня на сервере было такое кишло народу. Сервер битком и 70% птички от 2 и выше. Видимо повлияло что Hard[c0re] сервер пустой был. Эх....нам бы еще мортиры запретить... Надоело их уже "руками" убивать и кикать.
_________________ Чтобы вступить во взрослый разговор, мало выплюнуть соску, надо еще научиться без нее молчать. ---------------------------------
Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 4
Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения