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

domistyle

Members
  • Content Count

    661
  • Joined

  • Last visited

Everything posted by domistyle

  1. I will try to find out what exactly is crashing the server soon. I had a few users who had the same problem already, I couldn't figure out what is causing it though.
  2. We will be supporting DayZ standalone from the first second the server files are available. Our mod server will stay online if there are enough players. Since it's a server with official Hive it doesn't really matter if it goes down anyway.
  3. v0.8 will come out in a few hours. Just need to get home before I can upload it. The parameter is in seconds, not minutes. So 1 minute = 60. As ziellos2k said, it's not possible via RCon. v0.8 comes out in a few hours, can you try again with v0.8? edit: Could upload it earlier then I thought. v0.8 is out. If you have any problems, v0.7 is still available. Feedback is appreciated.
  4. From what I tested it seems like a too big ban list can crash the server once you request it via RCon. Not sure if a problem with BattleNET, DaRT or RCon in general. Tested with my banlist: http://forum.swisscraft.eu/DaRT/Bans/bans.txt?dart=2&banz=yes&dwarden=yes&community=yes Not sure if it's caused by the length or only happens for me but I will check again. Beside that the new version is running fine and is making it alot easier to check if BattleNET is connected instead of just waiting 1 second.
  5. Didn't have time to test it yet but will do soon.
  6. There will be a player sync option in 0.9. You will be able to share your player list with everyone who has DaRT and allows the sync.
  7. You can connect to your server from any PC. You don't need to run it on the server. However, Linux support will probably come once 1.0 is done.
  8. Yes, you can open the database under data/db/players.db with a program like Navicat. From there you can query the database with everything you want.
  9. Do you mind if I use BanZ for DaRTBans? http://forum.swisscraft.eu/DaRT/Bans/bans.txt?dart=2&banz=yes&dwarden=yes&community=yes Take a look at the parameters in the url.
  10. Restarting a mission is not recommended with DayZ. Since "Shutdown" shuts the server down (as the name suggests) there is no way to turn it back on via RCon. Only way to do it is with an auto restarter on the server. Depending on where you host the server you may have one.
  11. Yes, Execute...Shutdown. Restart will only reload the mission.
  12. Will be fixed in the next version. February to March?
  13. Fix for the ban list should be in the next version. BattleNET got improved and I didn't have any ban list problems with the new version. Dropdown probably won't make it in the next version but I will see what I can do.
  14. I will see if I can get it in the next version. There are timestamps already, enable them in the settings under "Show timestamps in log".
  15. Nice, that should make it alot cleaner. Will test it out very soon.
  16. How about adding a ConnectEvent instead of it? Could be more useful to check if BattleNET successfully connected. You could add the return types there (Login invalid, Connected, Host offline, ...).
  17. Yes, I currently filter every message by BattleNET as I do not need them.
  18. Yes, only global chat gets always transmitted.
  19. Only global chat gets always sent to the server. All other channels only get transmitted to the server (and RCon) when players are near.
  20. domistyle

    All Servers Down?

    Server got shutdown.
  21. Open up remoteexec.txt and delete line #0 and line #36. Reload the script/event files via RCon or restart the server.
  22. DisconnectEvent gets triggered 2 times too, making it output the disconnect message 2 times. Didn't have any problems with that yet, I just filtered the disconnect messages. DaRT sometimes displays a disconnect message 2+ times in a row because of this though.
×