guidez

I think it's gonna land Bliss, no? Wonder if there is any work being done on this now

^ crosire is the man Or woman Don't know yet, kee-kee-kee ;)

What if... We had an SD version: Class = MakarovSD Name = Makarov SD Side = EAST Info In use for nearly forty years the venerable PM Makarov served with the Soviet Red Army and now serves the Russian Federation Armed Forces. Equipped with a suppressor the silenced Makarov PM is an ideal weapon for special forces and assassins. Magazine Class(1) = 8Rnd_9x18_Makarov Magazine Class(2) = 8Rnd_9x18_MakarovSD http://www.armatechs...eapons/pistols/

Technically, the M1911 and Revolver suck as well post that Beta update, so any pistol I have I go for the headshot anyways. Waste otherwise.

I usually have better chances finding M1911's and Revolver's now then makarov's actually. If there was an SD version, well now, that would be different. From what it looks like according to ARMATech, you can use regular Makarov mags. Will have to do some testing.

Mmm, thanks for beans, om nom noms

DayCC use's Bliss. The install package simply gives an easy to use interface for administration, but the core of the hive is Bliss.

+1 for Bliss. I am using Control Center right now (dayzcc.com), and that developer loves Bliss as well. So +2

I bet you the plan is for the Dev teams to officially take a look at what the private community has developed to see not only which private hive best fits the makeup of the public hive, but ALSO to see if the private hives have done anything better (which I am sure they have) then the old hive. Just because the private hives are essentially hacks of the public one doesn't mean that the public hive DB runs things the best way.

The private hives would appreciate a single database type instead of 5 billion branches. That way, when rocket makes a new DayZ update, there is only one type of Public and Private hive that has to be updated, not 5 billion. Do you realize how much DB crap has to go into effect just to get Dogs ready for Private? Now multiply that by multiple privates hives running different tables and crap. I need to go trademark uber synergy™ before rocket does...

If the DayZ Development team officially supported Private Servers in addition to Public Servers, would you choose to host a Private or Public hive server? The question here is not whether or not rocket condones and approves of private hives (he does), but rather why they are not officially SUPPORTED (developed) by the devs. Everyone’s eyes are currently focused on the bugs, issues, and hacks occurring in DayZ, as well as the upcoming features. I can assure you though, once DayZ is “finished”, the public hive will be the largest glaring issue with DayZ, and by then it will probably be too late. Let’s take a quick over-view of the Pros and Cons of both hive types: Public Hive: Pros: - If your favorite server goes down, you can simply jump onto another server and still have your gear - I actually have no other Pros: Please supply me with some and I will update this Cons: - Administrators have little to almost no control over their server - The devs have to police the servers, since clans could lock down a server and hoard their gear, then noob kill on another - The hive goes down, NO servers work - A lot of bandwidth overhead. Not only do users have to make connections to your server, your server has to makes connections to a central server - Server hopping can never be fixed, so whether it’s hopping for gear or getting around barricades, the public hive allows it. This is one of the biggest issues for end game, which experienced players can get to VERY quickly. Private Hive: Pros: - Administrators have some more control - Characters only exist on that one server: No server hopping for gear or easy kills - Can whitelist/password protect their server, minimizing/eliminating hackers. Since a clan would get easily bored with no ability to server hop, they would have to allow other players on or their server will die from boredom - Database backups. Hacker messed up your server? Recover your automatically backed up database! (biggest win IMO) - A LOT less bandwidth overhead. The database is local to your server, so not only do you not exceed your monthly limit but you also have FASTER and MORE RELIABLE responses from the local hive/database. My users log into my server in 10-90 seconds worldwide. Cons - Some would say that private hives ruin the core or image or idea that rocket had for DayZ, but please read-on A lot of the plans for Standalone DayZ seem pointless to me. Why bother with “shoring up” a building / doorway, if I can simply server hop to another server? Why should I even bother making an entrenched camp, if someone can just hop over the non-existing barricades on another server? Games like World of Warcraft don’t allow you jump your character to another server (without a tedious server transfer process), so why can we do it in DayZ? To ease the support-ability of private hives, the devs could create a “private hive image”, one that server owners could download along with DayZ updates. This database could be locked down, with only certain fields allowed for customizations. For example, altering the weather or time of day would be allowed, but everything else would be locked down, so the core image of DayZ stays the way that Public Hives were, with the exception of all the Pros that Private brings. I had originally started this argument with the ability for private servers to customize whatever they want, but I believe customizations should actually still be limited, even on private servers. My private hive runs as vanilla as possible, with the exception of insta-kill on trying to go off-map and a customized day/night cycle, governed by my private hive community.

And 53.7% of the consequences result in rocket releasing an update ahead of schedule. ;)

YES! That is ALL the private hive community wanted to hear. As always, rocket, you are the man.

And this fix would, in effect, make putting up structures pointless. Your saying that even though I placed the structure, I will be teleported out of it when I log back into the server. You might reply that they could code it so that players who made the structure won't get teleported out. But then what about clan members? Ok, now code a way to allow clan members. Now they have to code a way remove players. Your suggestion is a coding nightmare.

Why not? Everyone seems to be so stuck on "we've had central server and that's the way to be". People have 1,5,10,20 WoW accounts/characters: What makes DayZ so special that you need a persistent character across all servers? Change all references in the code from "IP xxx.xxx.xxx.xxx", where XXX is the Central Hive DB IP, to "localhost". I know it's more involved then that, but it wouldn't be to much work on the side. OR, and this would be very helpful, provide the current database to the community. What I mean is, allow the third party developers to download the current hive (minus user data of course), so that they know what to build on. In the end, all that I am looking for here is for the developers to be more helpful to private servers: It's not like they OWE us private server owners anything, but if they appreciate how much load the private hives have taken off the central server, the private hives would just as much appreciate access to the public hive so as to ensure the longevity of private hives.

Updated first post to more recent information

I have updated the first post to be more informative of what I am looking for here. Thinking about it, I am actually against a lot of customization's myself, especially considering that I run a vanilla-esque server. And yes, DB Backups COULD be used as a admin abuse tool, but so could so many other things. But admin abuse will exist on a server, REGARDLESS of what restrictions are in place. It's the people that are the problem, not what they have the capability to do. Restricting what admins can do does nothing to eliminate admin abuse: It just makes it harder for them.

That's a good subject in itself as well: Since the central server is used by all, the Dev's have to police the servers. So no whitelisting, no password protecting, etc. It makes sense why you have to do that today: A clan go gear up on a protected server, then cause noob grief all over the non-protected servers, the return to the safety of their server. Since private hives mean that your character ONLY resides on that one server, there shouldn't be a need to police the servers nor even restrict the whitelisting/password protecting of a server. Take a look at minecraft servers: A lot of the ones that are the most successful are those with restrictive gates (ie; Whitelist, password, etc) in place. The central hive could still exist, but I'd say it would be better off with something akin to Valve public servers, where some wide open servers are hosted by Bohemia, but any private hosted servers are private hives.

I guess another question could be (and would love this to be answered): What is the biggest benefit to a central database/hive over a private hive? We don't have some sort of global economy going (EVE Online), so why even have a central server? It is easier to manage and support a Central Database I suppose, but you could just as easily say "dev's only support untouched private databases" to avoid the kids complaining about corrupted DBs.

Database backups (restore on hacker incident) Events for your community Customization (User's on my server cannot leave the map boundaries. They insta-die if they try. No off-map hoarding) The database backups are a big thing: I only restore on global incidents (I run a whitelist server, so we have had no hackers), but should we have an incident, users will only lose X amount of progress, where X is how often you backup the DB (I do it hourly). *edit* I actually run DayZ as vanilla as possible on my private server. The map boundary and Day-time for both American and European users are basically the only changes I have made.

What's stopping you from running a private server the way the Dev's want a public server run?

Brought up earlier, but again: It's a LONG way from "condoning and preferring" to "supporting". My private hive community has asked me: How long will you keep this server up and running? And, quite sadly, I tell them "No idea". That's because I don't know how long until the private hive developer gives up and someone (if anyone) takes up his work. Official support means I can tell my community: "Until you get sick of it"

I'll admit I've never played Eve, but from what I am reading, changes on a server affect all servers in the "universe". If, say, shoring up your base in US111 also shored up your building in US222, then I would be all for a public hive. But we won't ever have that, will we? The gameplay of DayZ is so unique and open for possibilities that it makes too much overhead for a persistent world between servers.

That is great and all, but like I mentioned (in a round about way), only the concept is supported. Break away from the whole central server idea altogether. Develop a PRIVATE server hive, so that us private hoster's don't have to wait for a third party developer to design a new database. When dogs come out, I know for a fact that it's going to take weeks past the 1.7.3 release for a third party to create a new private hive/database. In fact, a new database needs to be created for almost every update. Private servers like mine find it hard to provide our users a playable experience when they have to start from scratch every update. I had actually never even heard of a central hive or database used in this way before, if at all. It's understandable that DayZ was never planned to be this popular, so that's why central was used. But take a look at, say, World of Warcraft. You play on ONE server, and though you can get your character server transferred, there is no way for you to "server hop". Your character and STORY exists on one server.