xiuide

Well.. Glad that US23 isn't a host managed server. I'd consider that the problem right there, in the long run. not frequent updates by BIS or shut off dates, or HIVE or etc. you get what you pay for. you pay a cheaper price and go with an externally managed solution that takes the work of making sure everything up to date out of your hands, and your going to run into these issues. Not just with DayZ but with any external managed solution. be it a game server, web host, database.. anything that runs on a computer really.

If I were you Id ask for a refund, and then report them for selling servers below the minimum requirements that or up your slots to 40 or 50 really though, Id tell them you want a refund, for breaking dayz rules. and then find a different host that actually follows the rules set forth by the DayZ dev team (to avoid having your server blacklisted) EDIT: I just re-read what you wrote, and it seems like you bought a arma 2 server from them, not a dayz specific server? in that case please keep in mind what I posted above, DayZ requires at least 40 slots on the server. once you meet that requirement, please refer to http://dayzmod.com/forum/index.php?/topic/1251-want-to-host-a-dayz-server-read-in-here/ that post and follow the instructions.

Yeah I see it now. Had to look over it again. Again' date=' like I said, you're an idiot if you host with HFB. Simple. I wouldn't pay for such ludicrous rules. [/quote'] And you think that if your server was caught without battle eye, they wouldn't just blacklist your IP? Effectively cutting you off from hosting DayZ? HBS Had two options. Let DayZ blacklist the IP (and fuck over others using the same IP) or suspend the persons account. so either take out 4 servers (3 following the rules) or take out one rule breaking server. SUCH A DIFFICULT CHOICE. I really think I do understand what your trying to get at wild, but really the way your stating it probably is not the clearest. You wouldn't host with HFB because you feel that even if you break the rules (set forth by DayZ Mod itself, that you are required to follow when hosting a server regardless of if its a box, or a rented VPS) you shouldn't be in trouble, and should be able to keep hosting DayZ. Correct me if I'm wrong?

We are def not shutting it down... are you sure it was US23? we love hosting the server and having a home, and providing a home!

the view distance cap is for server performance. The higher the draw distance server side, the lower the server FPS will be. with a low server FPS you see things like rubberbanding, hitreg detection errors, and just all sorts of bad juju. The current view distance is a balance of immersion vs performance.

@Lemondish @Cal627 I'm glad you guys, and your friends are enjoying the server! I know I solved your issues via PMs but just in case anyone is lurking the thread both issues have been resolved, and I promise 7.1.2 wont take so long to update to this time! (darn you working for a living n stuff)

I have two issues with this statement 1) that's more than just a little presumptuous. 2) there is only one way to get (real) experience, and that's to learn by doing. No one is born with an innate ability to host a game server or server or any kind. its book learning and trial/error. As for the script.log file, there is a parser that one server admin created (cant remember his name right now) that I know he has been sharing to filter out the normal logs from the flagged stuff. There is an updated scripts list that doesn't cause the log to bloat like it did previously. tl;dr I 100% agree with you about your statements about how hard it is to maintain a hack free server. I also think you went WAY overboard with your blanket statement

US23 is Vet + CH:OFF + 3DP:ON + MaxPing:150 running 1.7.0 beta 93398 req

if you use BEC you might as well just set it to auto-kick lobby idlers at say 15 minutes, and have that in MOTD (that's what I do, anywho)

I agree with some sort of consistent server naming scheme, however there are some servers that enforce things like maxping that I feel should be stated right in the server name so people dont join without knowing. this reduces aggravation across both players and server admins. for instance, my server naming follows the outlined scheme, but I also add at the end of it to provide better information to the player DayZ - US23 (v1.7.0/beta 93398) [3dp:ON ch:OFF] [uTC-8] [MaxPing:150] dayzmod.com - hosted by Customtext I think being able to add these important bits to the server after the main required info is important and relevant to the server admin and player alike

I know its not ideal for a solution, but as long as you have full remote access to your server blackfuse, you can use autohotkey. what I did was place a shortcut to rcon, then recorded it using the AHK recorder, I did a 5 minute one then a 1 minute one. I use firedaemon on a schedule to launch these before my server restart. you can probably write a batch file that you can launch before and after work, that will automate that stuff though. have it run the 5 min warning, ping a fake IP for a fake 5 4 min wait time, run the 1min warning, ping again, then run a command to shutdown and restart the server.

Server Name: US23 (v1.7.1.5) [VETERAN|3DP:ON][uTC -6][MaxPing:150] Slots: 50 Difficulty: Veteran with 3rd person on and crosshairs off. Version: 1.7.1.5 with beta 93965 Location: Dallas, Texas Time Zone: UTC -6. Teamspeak3: 23.29.118.203 Rules: Standard DayZ rules including no side chat maxping of 150 (sorry guys, we like to maintain a solid server at all times, and pings over this can hurt the stability) the server will reset itself (and give a warning) at 4am UTC -8 every day Contact: Myself via the forums Donations (certainly not needed, but always appreciated!) http://us23dayz.chipin.com/us-23-dayz-server 6/25/12 *Updated the information at the top, we now have a TS3 server up and running! *Added a donation link, think of donations as a rainy day fund, or even a way for us to open more servers!