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!
So has anyone had your server go to unknown? I stopped my server went to dayz tools adjusted the timezone then went back to my server to adjust there and it was unknown. Been off for a few hours now. Put in a ticket but who knows how long that will take to get a response on. Any help would be great, tired of not having a smooth functioning server is getting real old real fast.
I'm assuming we are still getting the patch for the new Bliss and Rmod. My server has been down now for four hours with no CPU usage but I am at a steady 1% memory usage. And I can still not log on nor do I see the new Bliss in my mod manager. How long should the uploading of the files take to receive on our server side mod manager?
I agree with that post by SanctifiedDevil about the servers being down. Mine is also one of the ones down and has been since Friday morning. I would just really like an ETA or at least a rough estimate on when I might be able to play again. It is getting very aggravating with the slow to no response from tickets and the no idea of when this problem will be fixed. I think they are understaffed and overwhelmed with this problem. I'm grateful that they are gonna credit us the time lost but I have a good feeling they will be loosing some customers. I myself have already been shopping around for a new provider. I have had my server for less then 3 weeks now and it has already been down for a third of that time. That's not a good outlook on there part. If the problem is truly with the Bliss 3.5 update then why not revert back to Bliss 3.4 so the paying customers can continue to play while you continue to test the problem with the new Bliss version. Then when you get it all worked out update at that point. Seems like an easy fix to me.