Skocz do zawartości

Witamy w Nieoficjalnym polskim support'cie AMX Mod X

Witamy w Nieoficjalnym polskim support'cie AMX Mod X, jak w większości społeczności internetowych musisz się zarejestrować aby móc odpowiadać lub zakładać nowe tematy, ale nie bój się to jest prosty proces w którym wymagamy minimalnych informacji.
  • Rozpoczynaj nowe tematy i odpowiedaj na inne
  • Zapisz się do tematów i for, aby otrzymywać automatyczne uaktualnienia
  • Dodawaj wydarzenia do kalendarza społecznościowego
  • Stwórz swój własny profil i zdobywaj nowych znajomych
  • Zdobywaj nowe doświadczenia

Dołączona grafika Dołączona grafika
Guest Message by DevFuse
 

orsonik1 - zdjęcie

  • Przegląd
  • Status
  • Reputacja
  • Znajomi
  • Posty
  • Katalog linków
  • Steam

orsonik1

Rejestracja: 14.04.2010
Aktualnie: Nieaktywny
Poza forum Ostatnio: 12.06.2010 19:26
-----

Moje tematy

Dziwne logi :o

10.06.2010 22:34

Witam!
Zdaża mi się używać programu HLSW do monitorowania serwera. I tam pokazują w logach pokazuje mi się:
23:30:41 L 06/10/2010 - 17:29:59: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:41 L 06/10/2010 - 17:29:59: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:41 L 06/10/2010 - 17:29:59: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:41 L 06/10/2010 - 17:30:00: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:42 L 06/10/2010 - 17:30:00: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:42 L 06/10/2010 - 17:30:00: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:42 L 06/10/2010 - 17:30:00: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:42 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:42 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:01: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:43 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:02: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:44 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:03: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:45 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:04: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:46 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:05: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:47 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:06: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:48 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:07: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:49 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:08: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:50 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:09: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:10: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits
23:30:51 L 06/10/2010 - 17:30:10: Traffic from 68.142.72.250:27010 was blocked for exceeding rate limits

Co to takiego? Co zrobić aby tego nie było? :o

Hasło na nick

10.06.2010 11:00

Witam!
Mam pytanie, jak założyć zwykłemu graczowi hasło na nick?

Problem z konfiguracją dla danej mapy

08.06.2010 21:00

Witam!
Mam problem z konfiguracją czasową dla danej mapy.
Wykonałem następujące czynności:
1 Stworzyłem katalog maps w katalogu configs (cstrike/addons/amxmodx/configs/)
2 Srworzyłem plik o rozszeżeniu .cfg ( w moim przypadku ka_arena)
3. w pliku ka_arena.cfg wpisałem, co następuje:
mp_timelimit 7

Wszystko pięknie i ładnie :) Jednak jak załaduje się następna mapa, która nie posiada takiej konfiguracji (czyli bierze dane z pliku server.cfg) to czas nie zmienia się - pozostaje nadal 7 minut na mapę...
Proszę mi powiedzieć czy da się wyeliminować ten błąd?

Pytanie dot war3ft - war3menu

07.06.2010 21:16

proszę mi powiedzieć jak usunąć/zabronić opcję wyzerowania XP z war3menu (war3menu -> menu ras -> wyzerowanie XP)?
Mowa oczywiście o War3FT v3.0

Serwer z War3FT i problemy z tym zwiazane

07.06.2010 08:19

Witam!
Mam pewnien problem i zbytnio nie wiem jak go rozwiązać... Mianowicie jak zmniejszyć niewidzialność u human'a? Człowiek z poziomem niewidzialności na 3 lvl i płaszczykiem 39% jest prawie niewidzialny.... Jak można to edytować i w jakim pliku?

Tak samo z Wartownikiem... Jak zmniejszyć częstotliwość występowania kreta? W standardzie prawie co drugą runde ma sie kreta :D


Mam też problem z pluginem CAMPMETER. Mianowicie na mapach de_ campmeter rośnie również dla CT... Jak rozwiązać ten problem?
Moje Cvary (w pliku amxx.cfg) przedstawiają się następująco:
// badcamper cvars
badcamper_punish 12
badcamper_sound 1
badcamper_money 0
badcamper_limit 30
badcamper_display 1
badcamper_show_spec 1
badcamper_check_all 0
badcamper_start 5
badcamper_damage_reset 3
badcamper_damage_restart 4
badcamper_allow 0
badcamper_min_players 4
badcamper_announce 3

Znalazłem pewną wskazówkę dotyczącą mego problemu z pluginem BADCAMPER - nie wiem czy trafną. Pomoc jest tutaj: http://www.forum.wiaderko.com/poradniki-amx-amxx/124005-konfiguracja-serwera-oraz-pluginow-dla-danych-map.html

Więc tworzę katalog maps a w nim plik o nazwie: plugins-de.ini. I teraz zbytnio nie widzę sensu wpisywania cvaru badcamper_check_all 0, skoro jest to samo wpisane w amxx.cfg.
  1. AMXX.pl: Support AMX Mod X i SourceMod
  2. → Przeglądanie profilu: Tematy: orsonik1
  3. Regulamin