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

  • Content Count

    213
  • Joined

  • Last visited

Everything posted by [email protected]

  1. Hey Ryahn, I'd be willing to test it for you now that I have my dedicated box running. Shoot me a skype message!
  2. Could you provide more info for us? who do you pay for hosting? slotted/dedicated?
  3. I put in a ticket yesterday and got approved today..
  4. OR, if you are on rcon simply type: say -1 blahblahblahblah
  5. The main reason for me doing this is that the Dedicated server version will have SOOO many more features that I just don't want to pollute ftp users with. For the FTP version users are going to be limited to file scanning/rcon options anyway.. What i've got planned for my Dedicated version includes so much more that I really do need to seperate them out. Also I have an update to release tomorrow or over the weekend for dedicated and ftp.
  6. unfortunately there are 2 seperate logs. There's the RPT log file which logs players when they join/update to hive/ and disconnect, this has nothing to do with battleye. So if they are running a bypass they will show up in the RPT the exact same as everyone else.
  7. scripts.log is so broken right now it's not even worth using IMO. The current default scripts.txt that they give you to tell what to log and what not to log is worthless.. and now there's a BE bypass (which just makes it so you can join a server and never get 'scanned' by the servers battleye. Anyone running this bypass will never get scanned or logged at all. So even if they do run a detected script you'll never know about it. I welcome you to check out my progress here: http://dayzmod.com/forum/index.php?/topic/39628-dayz-server-suite-name-pending-alpha002-on-pg-3/#entry377033
  8. Well as I said, it's already simple enough to set up... for slotted servers you can just log in to CP and set up scheduled restarts, and for dedicated servers it's best to run them as a service and set up scheduled restarts that way.
  9. Then Host Altitude has automatic server restart on crash detection. On my dedicated box if I rcon the command #shutdown it physically shuts down the server and it does not come back. There are workarounds that I can put in place but I'm afraid that if I included this as a feature it won't work for everyone, as far as #shutdown is concerned
  10. Then the user would have to login to their control panel to turn the server back on.
  11. pepperkorn@gmail.com

    Hacking

    besides ban them and home they don't come back? not really.
  12. reboot will be hard for hosted servers as the only "restart" rcon command only restarts the mission. However if you log on to your server's control panel you should have scheduling options to set up auto-restarts. For dedicated server people, if they don't already have it set up you can set up manual/auto-restarts quite easily.
  13. If you have a non-hive server there is nothing DayZ can do except blacklist your servers IP from their hive so you can never run the official mod. You'd have to google on it as it's not supported here though.
  14. DO NOT get a slotted hosted server if at all possible. try and grab a virtual dedicated server or physical dedicated server, you'll have WAY more control over your server.. But if you do go with a hosted option, check through the threads in the server section, a lot of hosts have been having issues the with the game control panel and people haven't gotten their servers set up until 3-5 days later. From personal experience.. I had ordered a 40slot server from HFB about 2 months ago. My server was set up and running with hours, updates and beta patches were released within a day to the control panel, and I never had any down time. I now have a Virtual Dedicated Server via Host Altitude and couldn't be happier.
  15. Yes, because spamming them with 5 tickets will definitely put you first in line.
  16. Squad.xml has nothing to do with DayZ. It's for squad use "imagine that" and the decal just shows up on the side of some vehicles and in the mission briefing window/player list tab. It's perfectly ok for you to set that up.
  17. You can do it yourself if you didn't want to wait for them to. I'd put in a support ticket just in case though.
  18. Have you updated your scripts.txt to the new requirements since the BattlEye update? Check this: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins&p=2192402&viewfull=1#post2192402 And here is one pre-made: http://pastebin.com/uDy2Hae6
  19. you didn't hear this from me, but one of my *friends* had it enabled on "their" server for the whole time it was running and never got black listed. */cough*
  20. 4days to two weeks? I just applied for mine as well but you must be patient.
  21. Good news and bad news. Good: I just got a dedicated server. Bad: Now I have to wait for DayZ whitelisting. Only one instance of this program can run per server, or the other instance won't function properly. Another reason to split this into a dedicated and FTP version XD
  22. Depending on how much they reduce from the RPT will affect the usefulness of half the functions I'm working on, but hopefully it's JUST the coords lol.
  23. I'll be using the split and replace functions to bring that "easy to read" view for people. I'll probably even create a method of double clicking on a player and it replicating the inventory system the exact way it looks in ARMA2. should be quite easy with a screenshot of the inventory and images for each item, but that's a long way down the road. I feel the need to focus more on the RPT file now that BattlEye has been updated and logs more efficiently. That way if a player DOES have hacked items or irregular movement you can tell right away from the RPT. I'll be implementing a way to just "click and kick/ban" players that are found with hacked items. The reason I'm pulling away from parsing the Scripts.log is now more and more battleye bypasses are being released.. rendering those logs useless. Just the fact that hive updates get logged in the RPT is perfect for an anti-cheat (as far as items are concerned)
×