howichrgelazer

The game won't launch on a server but it will create the necessary registry files. However, I found with the steam version, it's best to create a new folder and copy both the contents of your arma 2 and arma 2 oa folders into that one folder. That way it'll see all the assets and you have the steam folders untouched in case you need to update. Just make sure to copy the beta folder over on each beta update. :)

So I was thinking, To further streamline the process and prevent unnecessary threads in the section, perhaps only members of the server host group (like us) should be the only ones with the power to start a thread? Just allow all users access to reply to threads. This way, the server hosters can still have a place to have a server discussion and announce downtime, and users can still respond with reports and other necessary information. But they won't be able to create threads like "Admin abuse or Admin killing all people!" - That could be rolled in with the other reporting category or posted in the server thread created by the host in question. Then have one sticky for each of the following: Purpose of the category (explain admins can't kill people, or have control over the master db, etc.) Requirements and channels to start a server (combine to one thread) DayZ Server Auto Restart Disclaimer about donations Possible Suggestion: Locked/Passworded Server report thread with guidelines for reporting and users can report findings. The rest should be able to be unstickied because information like installing the beta has been included in the post for 1.7.1. What do you guys think?

Okay so I was sitting down and thinking to myself on how to restructure this properly. Here's my take on things. Server Discussions and Announcements - Find information and talk about active DayZ servers Server General - Report a problem with a server or ask for help with server related issues In Server Discussions and Announcements, only people under the server hosters group can post threads. Limit one thread per hoster. Non-hosters can post replys to threads. Server General would be just like Sykotix suggested (to be honest, both things, but yeah). Alternatively, you can break it down into three categories which would be Server Discussions and Announcements, Server General, and Server Reports. That way you can break up the admin abuse/locked server reports up with the posts about help with servers. Ideally, you'd want them in IRC so three categories is probably pushing it too far. It should be a requirement for each hoster to create a thread on their respective servers so users can keep up communication with them. It's important for the user base to be able to express concerns, and with so many "third-party" servers, you have to have some official line of communication. I would hope each server admin has a forum account. :) And with the main server threads out of the way of sever general, that category can be more streamlined for reports and people who have issues starting or configuring a server. The biggest issue I see is that there is a weird gap between server hosters, the server team, and the users. Admins who stay on top of everything have no issues, but we still have admins out there that are using the wrong naming schemes, have no thread for contact information, and ones that just don't plain show up in IRC. I'm not even suggesting that they have to talk or anything, but if you're running an alpha server, communication between the team and the users is paramount. I know you guys are trying your best to make due with all the requests, so it's going to take time for everything to fall into place, but yeah. A little house cleaning could go along way in helping things run more smoothly :)

Added an example for server difficulty to help clear up any possible confusion. Should I continue to support this guide? Not sure if it's been helpful or not to anyone. I also want to sit down at some point and write a quick PHP script that helps assist server owners in generating a server name with the correct nomenclature. Should be pretty easy to do if it's necessary. I still notice a lot of servers out there who aren't using the naming scheme in the right way, and I want to make it as simple as possible. :)

Lol, looks like we were all over that issue. ;) As for VPSes, it's honestly all about who you get it from. Our server runs on a VDS and it works really well. The major thing is that it's running a virtualization solution which gives you dedicated resources, and not something like OpenVZ which you share resources (and hosters love to oversell the hell out of the boxes). Pretty much, make sure the virtual server is on quality higher-end hardware (with isolated resources for your instance), the box has bandwidth for it, and that they have a good track record of not overselling. It should fine no problem. But I understand where Pallidum is coming from, there are just too many VPS providers out there that oversell or don't provide enough horsepower for a game like this. It's easier to just say avoid them. ;)

Yeah I wouldn't artificially try to alter the time for one DayZ server on a box with two DayZ servers running on it. We've already seen server(s) get blacklisted for doing so (all daylight for example) because it mucked up the hive.

Depends on the specs of the VPS, but you'd be better off ordering two separate ones so you can offset the time on each. The devs don't like it when you fiddle with the time outside the system clock itself as far as I know. For an example, have one VDS at GMT-6 and the other VDS at GMT+6. The question I have for you is: Are your familiar with running servers? I'm assuming since your renting a VPS it'll be unmanaged, it's no easy undertaking if you don't have the experience. I'd recommend going with a managed VDS provided by some hosts here if your skills aren't up to par. :)

I think the major issue with having individual databases during this stage of development is the sheer amount of headaches it would cause pushing out updates for those servers along with what changes are made to the master. Plus all it takes is one person who doesn't know what they are doing to create an unstable server which would generate bug reports that have nothing to do with the mod itself. As for server hopping for loot, there are mechanics in the game that help curb loot spawns for people who do this. Finally, in what you call "ghosting" - it's just a matter of being aware of your surroundings. Honestly if somebody logs in, there is a delay from logging in to when they actually get control of their character. If they are in an area they normally wouldn't get to with others around, chances are, they'll be shot pretty darn fast. Besides, people run a HUGE risk if they log out in lets say Stary and log back in. I've heard of plenty of people getting waxed because they didn't log out in a better area originally. EDIT: And just to make sure I'm not sending the wrong signals, I'm not bashing your idea. I just don't believe there is a necessity to have server run databases at this time. :)

Log into another sever, screenshot your GUID when battleye reports it and type/send it to them so they can go through bans.txt and remove the GUIDs in question. The ban list will have to be re-loaded or the server will need to be restarted for it to take effect.

I was about to recommend somebody til you got to the unlimited bandwidth part. But I'll throw it in anyways: https://www.nfoservers.com/order-virtual-dedicated-server.php These guys are top notch. Fast support, quality bandwidth, high end hardware. Been with them for ages. A big bonus is that they are having a summer sale right now. I'm using a VDS plan from them for our DayZ server. Plus they have a 2-day free trial for any new accounts. If you do use them, tell 'em in the comment that rcgvds (cuatthefinish [ a t] gmail [d ot] c om) sent you. :) EDIT: The time offset can actually be set in the Xen settings in your control panel, so you're able to offset the time outside of the OS. Which is pretty nifty. I do want to warn you though Savage. I'm not sure of your experience in administrating servers, but if you don't have any background in working with Windows Server or managing a game server, I'd look into a host that is more managed. I think you'll get into trouble with an unmanaged server if you don't have experience.

Yeah, that sounds like the culprit then. Server is majorly de-synced. A reboot should put it right back in line. (Assuming nothing is wrong with the system clock, which there shouldn't be).

That would be a negative ghost rider (afaik). Although, I'm sure Ander or rocket will announce when helis are safe to have in servers.

How often do you reboot the server?

Our server does have vehicle spawns APOF1S. ;)

Made a few changes and grammar fixes.

This is possible. I also wouldn't pin the blame on a server admin yet until there are more details. More often than not it's the work of a hacker. Unless the admin himself is using scripts, which I highly doubt.

This should probably be posted in ban appeals just in case this user comes on the forms to discuss the matter. Or to be honest, not even posted at all unless the user complains. As a server admin, there's no reason to publicly taunt somebody, even if they performed an exploit. ;) Now if this was a warning thread (which it isn't based on the lack of information on the person involved) then I'd probably think differently. However, this seems more like a call out then anything helpful.

If one has the rcon password they can. It could have also also been a timeout with the hive. With everybody dying like that and probably recreating characters, it probably choked the server until it caught up with itself. If the server was only down for 20 seconds, I doubt it was a reboot. It normally takes 30 seconds to 1 minute to do a full restart. Plus the mission would have started over again. My bet is on the server having to communicate with the hive for all the new player and death requests.

Server naming conventions aren't being followed the way they should be. I know the team is working hard to rectify the issues. I posted a thread which can help explain things further: http://dayzmod.com/forum/showthread.php?tid=18203

Server admins do not have the ability to mass kill people, kill individuals, teleport, alter items, etc. This was the work of somebody using scripts or hacks.

This is how it's supposed to be (how I understand at least): You state the difficulty mode of your server, then after that, you add optional flags which deviate from what that difficulty has at stock. So if you choose to do Regular, but you want crosshairs off, the server name should have [REGULAR CH:OFF] because by default in Regular crosshairs are on. Now how many server admins try to follow that, I'm unsure of. I know a lot of people have been trying to get the right naming convention down.

21.06.2012 08:38:40: MARIARDI (46.39.36.67:43536) f8dddc9a1627941eddf5537f60ca53cb - #30 if (isnil 'BIS_GITA_fnc_createMarkers' || false) then { BIS_GITA_fnc_createMarkers 21.06.2012 08:38:41: MARIARDI (46.39.36.67:43536) f8dddc9a1627941eddf5537f60ca53cb - #36 CfgWeapons" >> _x); if (_isOK) then { player addWeapon _x; }; } forEach _wpns; }; r_player_ 21.06.2012 08:39:59: MARIARDI (46.39.36.67:43536) f8dddc9a1627941eddf5537f60ca53cb - #36 y + _tQty; }; if (_iItem != "") then { _item addWeaponCargoGlobal [_iItem,1]; }; }; r_player_ 21.06.2012 08:38:52: Observ [Solar_TFFN] (188.232.76.152:2304) 2dd4e48dfbf865bdce72736339b8e9d5 - #36 CfgWeapons" >> _x); if (_isOK) then { player addWeapon _x; }; } forEach _wpns; r_player_ 20.06.2012 21:01:27: PoopFaceKiller (71.55.176.195:11646) 1bd1a5600a90669e198a71644c5da21c - #36 y + _tQty; }; if (_iItem != "") then { _item addWeaponCargoGlobal [_iItem,1]; }; }; Are these legit or suspect? I'm noticing the last one comes up more often that the other one, so I'm thinking the last one is okay, but I just wanted to make sure.

No problem, thems the breaks with DayZ. Usually people do that to greif or to protect loot for themselves. So the only way to counter it is to take it down yourself. No reason for the devs to really stop it. It's part of the game. ;)