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

ziellos2k

Members
  • Content Count

    161
  • Joined

  • Last visited

Everything posted by ziellos2k

  1. Hmm that's odd. Can you try and see what happens when you're using the official RCon client? -> http://battleye.com/downloads/BERCon.exe
  2. Are you talking about the server not sending player login messages to the connected RCon client (BattlEye -> BattleNET)? If so, this is indeed not a problem with BattleNET but with BattlEye. When the server is under (heavy) load it will start dropping packets (which UDP doesn't handle unfortunately) while probably showing a yellow or red chain in game. Data being sent by BattleNET towards the game server (BattleNET -> BattlEye) will probably be dropped as well when it's under (heavy) load. I'm planning to look at this soonish but for now please refer to my previous post. :) EDIT: You can track progress on the latter issue @ https://github.com/ziellos2k/BattleNET/issues/9 :)
  3. I actually did this while I was running my server on linux. I used it to notify users about restarts in a simple bash script. Unfortunately the lib itself doesn't know whether a message has been send and received so you would need to check in your own app the output by the server. send(msg); while(!serverout.Contains(msg)) { sleep(2000); send(msg); } // exit or something like that. :)
  4. ban [player #] [time in minutes] [reason]
  5. If you do go with NAT please don't go with gamespy as it's pretty much broken. Take a look at http://wiki.unrealad...g/UT3_ICMP_Fail.
  6. You're free to do so yourself. ;)
  7. Code & binaries updated, check https://github.com/ziellos2k/BattleNET/commits/master/ for the changes.
  8. Code & binaries updated, check https://github.com/ziellos2k/BattleNET/commits/master/ for the changes.
  9. Binaries updated to contain all changes since 2012-08-21 :)
  10. Sweet job there DomiStyle. :) A few more suggestions: Only auto refresh player list regardless of what tab is open and remove the ban list auto refresh Refresh ban list on need to refresh basis (i.e. manual ban / reload bans) Remove DaRT messages from console (i.e. refreshing players / bans) Also, if you need any changes to BattleNET, you know where to find me. ;)
  11. Small suggestion, move the player count outside the RCon console. Other than that, awesome work! :D
  12. Merged source and binaries into https://github.com/ziellos2k/BattleNET, BattleNET-src is removed.
  13. New version released (20120821), see first post for details. Should be fixed now, somewhat. :D
  14. ziellos2k

    NL 21 hacker(s) atm!

    Can't really do anything about the hacker but I'll check the log files in the coming days. :)
  15. It should disappear after restart. Can't really do anything about the hacker though, but I'll check the log files in the coming days. :)
  16. ziellos2k

    I Found A Dog

    Well, I'm the admin of NL 21 and it wasn't me. :)
  17. ziellos2k

    Graphical bugs

    Here's a possible fix; http://pastebin.com/raw.php?i=1w6rSW59
  18. No idea, zero experience with vb.net. I'm just guessing here but it could be that events in VB.NET are different from C#.NET? Also make sure you put b.MessageReceivedEvent += HandleMessage after Dim b As IBattleNET = New BattlEyeClient(loginCredentials) and before b.Connect(). No idea if it matters but that's all I can think of. :) Who cares... Besides, I didn't pick the name. :P
  19. It's basically a .dll file that programmers can use to communicate with BattlEye (i.e. warn about restarts automatically, etc). For you, I guess, it's not much of use in this state. :) I may release a simple auto restart notifier in the coming days though.
  20. New version available, first post updated. :)
  21. New update available, see first post for details.
×