set path_hive=C:\Server\dayz_1.chernarus
set hive_night=HiveExt_night.ini
set hive_day=HiveExt_day.ini
:init
set /p "x="<"C:\batch\counter_1.txt"
echo Iteration: %x%
if %x% == 5 (
cd /d %path_hive%
xcopy %hive_night% %hive_normal% /Y
echo START SERVER WITH NIGHT SETTINGS
set...
the problem with this approach is, that is doesnt block map -> unit -> gear.
u can also bypass it by selecting gear via menu and press at the same time ur gear (g) key.
only a matter of time until ur players are finding out.
i already tried many things with the current and the previous script.
this script helps very well dealing with people talking accidentally in sidechat.
but if someone double presses shift he can spam as much as he wants. lowering the sleep timer doesnt help obv.
so for that case insta kick by...
thank you for that, but it doesnt help against double tap.
iam running the version you released some days for 2 days now.
my experience is that these fags trying to annoy the other players are feeling challenged by the script and spam even more.
i have the 'bug' that the names are not displayed...
yeah i said thats it not the greatest samplesize.
iam going wait for other logs and decide then if i finish my post with q.e.d.
i really like your anticheat. it makes dayz playable. peace!
lol, these logs (ok not the greatest samplesize) proof that this code affects the seagull issue and your still calling it placebo?
so either you have to say the logs are faked or you have to deal with this.
i hope other share a grep of their createvehicle.log after adding this.
i never told that this code in the server_cleanup.fsm doesnt work... it just getting too rarely called.
ur just telling that this is redundant and doesnt work... but it does work.
i can send you my createvehicle log before and after adding this.
deal with the miracle :cool:
i never said that i edit it with notepad.
this way is just easier. i understand your point, but just search for seagul / createvehicle... u find thousands of threads about this issue. the builtin cleanup doesnt work properly.
i have seen many servers changing the seagul line from 5 to 1 to avoid...
iam talking about this syntax:
item0[] = {"init",0,250,-75.000000,-400.000000,25.000000,-350.000000,0.000000,"init"};
item1[] = {"true",8,218,-75.000000,-175.000000,25.000000,-125.000000,0.000000,"true"};
item2[] =...
batch:
set path_sql=C:\MySQL\bin
set path_sql_query=C:\foo
set db_host=127.0.0.1
set db_port=3306
set db_name=
set db_user=
set db_pass=
:mysql
echo executing sql queries...
cd /d %path_sql%
echo remove foo
@mysql.exe -u %db_user% -p%db_pass% -D%db_name% < %path_sql_query%\foo.txt...
the group cleanup happens too rarely.
when the seagul issue happens the general cleanup could take hours to fix it.
you can either mess around with the complex fsm syntax or do it handy with this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.