YaPB2 Updates

[jeefo]

Originally Posted by ViBE@

damn, it was an early bird. sometimes they don't leave. so sadly not :/

special names? you mean i need to create "lang_names.cfg" file? cause it's already done. with the last stable release this function partially but worked. when they connected it took about 8-10 secs to get their ping and sometimes disappeared. with the debugging version this is completely dead.

generally all weapons are available in gunmenu (with CSDM's /guns command). but i wanted to restrict them to use for example AWP with YaPB built-in command but they still can choose. is this normal behaviour? my settings:
yb_restricted_weapons "00000000000000000000011101"

UPDATE
sometimes only some bots leave but they stuck or what and stop leaving. for example i set 12 bots with autovacate. then 4 human arrive and only 2 bots leave. and then they stop leaving when players arrive.

damn... well will try tomorrow again..

bot's should be affected by amxx restrictions (amx_restrweapons).
yb_restricted_weapons has different format f.e. yb_restricted_weapons "ak47;m4a1;etc"

the names.cfg should contains nickname\t\tcommunity_id pair. where \t - tab character.

Bloodlust 76561197983068151

etc.

But, someone reporeted that valve disabled this feature in recent steamclient updates.

[trololoshka]

Originally Posted by ViBE@

UPDATE
sometimes only some bots leave but they stuck or what and stop leaving. for example i set 12 bots with autovacate. then 4 human arrive and only 2 bots leave. and then they stop leaving when players arrive.

We need ammx plugin for control players connect\disconnect and add\kick bots
Or automatic in bot_module

But standart - bad, because leave (kicking) alive bots too .
Need kicking dead bots only

Example:
plugin checked to number bots (ex. every 30 sec) :
if need add = adding
if need kick = ex. 5 bots .
3 bots are dead = kick now
2 bots are alive = write to buffer
and when bot's will be killed - kick.

Sorry my bad eng.

[jeefo]

Originally Posted by trololoshka

Использую как метамод плагин . Билд 6153 бетка , АМХХ 1.8.3
Yet Another POD yapb.dll v2.7.2

Пару нюансов есть по ним:
1. Не дружат с glow rendering ( fm_set_rendering(id,kRenderFxGlowShell,200,200,100 ,kRenderNormal,; // goldenish) - перестают стрелять по игроку у которого есть или был рендеринг (да, даже сброс fm_set_rendering(id); // reset back to normal ) не помогает .
2. с SG550 и Scout только с далека валят. если на средней дистанции то бегут один к одному и в ступор ..
3. С ножа практически не реально убить даже на 1 из 5 сложности.
4. При коннекте игрока боты выходят а вот когда игрок выходит - бот не присоеденяется.
Но это не критично ибо мне все равно придется писать плагин который будет кикать ботов когда они мертвые.
5. На KNIFE MOD CS 1.6 сервер поставил ботов - на таких картах как 35hp они спрыгивают и разбиваются .. бегут в воду и там смотрят друг на друга .. кошмар ..
ПодБоты бегут по вейпоинтам, а если и прыгают то используют парашют . Но подботы юзают много ЦП и тупят по своему.
6. Нет детальной настройки ботов (стрельбы) . Очень большой % хедшотов.

1. По рендерингу, не включено ли часом yb_check_enemy_rendering?
2. Демка есть?
3. ну ... хз whoose_your_daddy отклчить мб?
4. Да сейчас пытаемся исправить это.
5. Ага, попробую поправить.
6. Туда никто не лазил никогда. Опять же whoose_your_daddy , у меньшит количество хэдов.

[trololoshka]

Originally Posted by jeefo

1. По рендерингу, не включено ли часом yb_check_enemy_rendering?
2. Демка есть?
3. ну ... хз whoose_your_daddy отклчить мб?
4. Да сейчас пытаемся исправить это.
5. Ага, попробую поправить.
6. Туда никто не лазил никогда. Опять же whoose_your_daddy , у меньшит количество хэдов.

1. yb_check_enemy_rendering 0 стоит
2. Этим вечером запишу и выложу
3. whoose_your_daddy - нету такой команды

[jeefo]

Originally Posted by trololoshka

1. yb_check_enemy_rendering 0 стоит
2. Этим вечером запишу и выложу
3. whoose_your_daddy - нету такой команды

1. проверю.
3. yb_whose_your_daddy 0

[ViBE@]

Originally Posted by jeefo

damn... well will try tomorrow again..

bot's should be affected by amxx restrictions (amx_restrweapons).
yb_restricted_weapons has different format f.e. yb_restricted_weapons "ak47;m4a1;etc"

the names.cfg should contains nickname\t\tcommunity_id pair. where \t - tab character.

Bloodlust 76561197983068151

etc.

But, someone reporeted that valve disabled this feature in recent steamclient updates.

so to restrict weapons i should use the weapons short name not their numbers?

that's sounds difficult :S

this ping thing works perfect with latest PB, so i guess it's not disabled with latest update.

[jeefo]

Originally Posted by ViBE@

so to restrict weapons i should use the weapons short name not their numbers?

that's sounds difficult :S

this ping thing works perfect with latest PB, so i guess it's not disabled with latest update.

AMXX restrictions doesn't works ?

[ViBE@]

Originally Posted by jeefo

AMXX restrictions doesn't works ?

i would only ban bots usage cause they are maniacs with AWP for example. but i don't want to restrict human players. that's why i asked.

[jeefo]

Originally Posted by ViBE@

i would only ban bots usage cause they are maniacs with AWP for example. but i don't want to restrict human players. that's why i asked.

well i can add podbot-like cvar for restricting, but... maybe better to use what we already have ? it's not hard really

[ViBE@]

Originally Posted by jeefo

well i can add podbot-like cvar for restricting, but... maybe better to use what we already have ? it's not hard really

it's fine. i just did not find any description in the cfg file about how to restrict and i thought you using PB like.