Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

facoptere

Members
  • Content Count

    882
  • Joined

  • Last visited

Everything posted by facoptere

  1. No I don't have any setvehicleinit lines during the night.
  2. you are unbanned. the ban list is shared between the 3 gameservers, and sometimes my unban command are overwritten by restarting servers.
  3. Please check your server RPT logs. Maybe a vehicle exploded while spawning. I will check whether the BIS functions (which use setvehicleinit) are overwritten after of before server_monitor (which spawns vehicles&tents). Edit: I checked the code and the server should never trigger setvehicleinit. So I suppose it's a hack.
  4. #205 = setvehicleinit. Restart your server.
  5. facoptere

    Monitoring "Combat log" in 1.7.7.1

    There is currently a bug when player disconnect, and log line is not printed correctly. This will be fixed in next patch.
  6. you should try the one provided.
  7. I don't understand. There is only 1 line in addbackpackcargo.txt, so this can't be restriction #12. Other filters, addmagazinecargo.txt and addweaponcargo.txt, have rules for backpacks, but their figure is already "1" and not "5". So you are not using regular filters.
  8. it's a hack. Restart your server when you see this.
  9. Try to find a 1.7.6 server and drop your BAF_L85A2_RIS_CWS.
  10. I need more information. What is printed on before "restriction"? script? remoteexec? Then I need the log line in the corresponding log file For a "setVehicleInit" related problem (which correspond to script restriction #204), you have to restart your server since it's a persistent hack on the serverside.
  11. You are not using latest BE filters. #10 and #150 correspond to TitleText and are properly addressed. Download latest filters here https://github.com/DayZMod/Battleye-Filters/archive/Release_1.7.7.1.zip
  12. The first lines with isleader and CMD: I don't know what is it, and why it happens for few players and not others. So these logs are not filtered. The lines with AirDestruction and SmallSecondary are linked to a vehicle so damaged that it explodes. Not only helicopters. I was driving a tractor yesterday, it was in a bad shape, I bumped to a wall and it exploded. The same lines appeared. By default I don't consider these lines as cheats.
  13. Few pieces of code are still logged in scripts.log, since all commands have not been reviewed (for example here removeMagazine removeWeapon). So don't ban for everything in this file. I log also intentionally players who drop weapons, players who trigger explosion. There are at least 2 other hacks that reset BIS libs. I have a mission file that fix all this, and I don't have any attacks since even I am not sure it's related. It's on test for now. The best is to restart the server for now.
  14. Could you check that the code above is in init.sqf from your mission file? Then start your server with a password, and log in alone. Are you kicked because setvehiceinit?
  15. this BIS code is overwritten in mission file, since it's has some security issue. in init.sqf: /* BIS_Effects_* fixes from Dwarden */ BIS_Effects_EH_Killed = compile preprocessFileLineNumbers "\z\addons\dayz_code\system\BIS_Effects\killed.sqf"; BIS_Effects_AirDestruction = compile preprocessFileLineNumbers "\z\addons\dayz_code\system\BIS_Effects\AirDestruction.sqf"; BIS_Effects_AirDestructionStage2 = compile preprocessFileLineNumbers "\z\addons\dayz_code\system\BIS_Effects\AirDestructionStage2.sqf"; .... If your players are still using setvehicleinit: 1/ you don't use given mission file 2/ or hackers remotely reset BIS lib with battlefieldclearance hack (or other objects that reset some BIS libs) 3/ or players use hacks. I would like to know when and how this happened to you.
  16. facoptere

    SetPos #0?

    http://dayzmod.com/forum/index.php?/topic/139308-setpos-and-kicking-due-to-battlefieldclearance/#entry1385232
  17. You should contact the authors of your pbo, they should give some suport. The original pbo is for public hives. If your server is public, or is using the same database scheme, it's ok.
  18. use of "hint" command, which is frequently used by cheaters. -OR- You are not running vanilla DayZ mod, but a modified version.
  19. When you get this: 1/ ban player from remoteexec.log. An empty pattern should appear. 2/ restart your server immediately 3/ don't ban players from setpos.log only because they are on setpos.log with this battlefieldclearance entry. They are the victims.
  20. facoptere

    Server admin changes within 1.7.7

    Could you give some examples of logs you don't understand?
  21. So you discovered the hacker and legit players are safe since they are kicked. The safest is to restart the server. Update won't come quickly since cheaters found a another way to execute some code on the serverside with this invisible remoteexec.
×