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. download scripts.txt again and restart your server.
  2. Thanks, I will have a look. My bad :(
  3. Tu dois aller sur un serveur public moins sécurisé, ou encore en 1.7.6.1, et lâcher ton BAF_L85A2_RIS_CWS.
  4. facoptere

    EVERYBODY HACKING, ON EVERY SERVER!

    You are replying to a 1 year old comment...
  5. All private hive vehicles (former Bliss) are supported. With unknown vehicles you may experience some problem with vehicle damageable parts. Teleport. There is less and less teleport thanks to the anti-teleport background task on clientside. Former obvious solutions were using setpos command, or attaching your own body to a (far) remote object. Using 'drag body' for example. This can't be done as easily. However, there is still a weakness with the debug area. BE filters can't be an efficient solution to detect that. Your only hope is using scripts.txt, but it's a clientside filter so it can be bypassed. Current filter logs unexpected use of setpos and attachto. Don't expect miracles. Preset Gear. scripts.txt logs unexpected use of addweaponcargo and addmagazinecargo, and players can be kicked. However, this can be bypassed too. If the pattern is always the same, you can detect it in hiveext.log. The Character ID is logged with the pattern. You can match this Character ID (CID) with arma2oaserver.RPT log file. Lines with "LOGIN PUBLISHING" log player's CID UID and name.
  6. You are unbanned, but you will be banned again as soon as you use some unicode hacks for your name.
  7. you have to restart your server when this occurs. Don't set to '1' unless you want cheaters do what they want on client side.
  8. Well, your translator forgot to translate your real IP address, lol.
  9. Dayz Epoch is not DayZ official Mod. You should ask this mod's author for a dedicated filter set. There is no "hint" (messages on upper right corner) or "DZ_Pastor" (dogs) in vanilla DayZ.
  10. I can't find you in the ban list.
  11. facoptere

    Why do I have to adjust BattlEye filters?

    I am using 1.7.7.1 files, and players are not kicked because they built a fireplace.
  12. facoptere

    Server Log Question

    yes that's the point: how fast each part are repaired.
  13. facoptere

    Server Log Question

    Time and date are missing. put the whole lines.
  14. what do you mean by "server control"? Could you give a snapshot? If you are talking about the standard panel where you can enter you admin password, it's properly filtered and you won't be kicked.
  15. You should contact your server admin and give him the same information.
  16. All these are hacks.
  17. facoptere

    Why do I have to adjust BattlEye filters?

    Could you give the restrictions you have?
  18. facoptere

    massive down/upload ingame

    100MB/hour = 27kB/sec, which is a bit higher than average, but quite normal. Try to find a server where netcode parameters are optimized (big datagrams, less fragmentation)
  19. If you do that, you lower the security level to what it was with DayZ Mod 1.7.6.1: cheaters allowed to remote exec anything on any gameclient.
  20. The current problem is that cheaters manage to inject some code to legit players. So you can't trust or blame anybody for a bad log line in scripts.txt. I can't enable pattern #84 because this would reset the security system on all gameclients (it's first thing the cheaters are looking for) and BIS libs. "bis_greetedpeople" pattern is very old, does not belong to DayZ code, and usually is part of a hack (I think). #205 corresponds to a BIS libs reset (cheaters managed to reset security system too). You should see "setVehicleInit" 2 lines below. You have to restart your server when this occurs.
  21. FR 34 FR 129 FR 130 It's a public server and I have no explaination why your character has been reset the public hive.
  22. It's not what I can see in my logs. Inmotion was being camping at the airfield for 1 hour. You were shot twice by Inmotion in 2 seconds from 35 meters. You did not die. Between the 2 shots, hisoka!! logs on at Quarry (very far), so no link with you. You log off 2'20" after last shoot, and you were tagged as 'in combat' according to player public variables.
  23. Gametracker bug. 52 players are playing now and gametracker reports 5 players.
×