rocket

Well see, thats what is confusing. Because I've mainly been getting reports from people that tents are working. please post what happened and on what servers. Some admins are restarting HIVE mid initializing. Regardless, anything you value keep on yourself. Anything you don't put in tents. Need to test the tents and find the bugs.

My tank trap item model is causing infinite polygons on doom on some screens. So I need to sort that out.

By having hundreds of friends to carry said hundred jerry cans. Soon you will be able to power fuel pumps with generators. But right now you can't. Carrying jerrycans is good exercise anyway :)

That generally happens when the admins restart HIVE it desync's with the ArmA2 server during startup. If they're lazy - they will restart HIVE and everything continues as if the initialization has been done. If they're smart - they will restart the arma2 server and leave hive up.

The "keys" folder only matter if you are HOSTING the mission. The keys that matter are the *.bisign files with the name of each of the mod files: eg. dayz_anim.pbo.dayz.bisign These need to be with the addon files. Do not run any other mods other than the dayz ones. This includes CBA and JayArmA2lib. These are only used by the server. Your client only needs the vanilla files and the DayZ files. Anything else will probably trigger a kick by the server and/or battleye.

can you provide some more detail about what state it is? compared to what state you would expect it to be in now?

As above said, the database updates your name each time you login. It was initially intended you could create multiple characters, but that was when we had a character for each server. Unknown whether this will be pursued. It's possible but would need to check for potential exploits, balancing issues, etc... before it was coded.

That's the key reason why I haven't rolled back the likely change that causes DC to work unreliably. Having players in another body is necessary to ensure saving works on disconnect, which is the only really effective way to prevent a number of the key exploits. SQF is pretty similar to C, but its not the engines code, and it has some very peculiar aspects to it particularly regarding locality.

I was going to take it out, but then I realized I was simply taking short term easy with long term hard way. The reason its not working is because the code I use to swap is a underdeveloped and I didn't want to work on it. I need to deal with this eventually to allow you to change clothes in the game anyway. So I just cowboy'd up. And, as Oilman said, the state of the mod is very early in the SDL. The popularity of the mod has been a bit or a surprise given it only just went Alpha. I've probably been modifying my approach a bit much, the SDL is the way it is for a reason and I guess I need to just toughen up and be firm about it.

Send RPT files to [email protected] After the recent patches, nearly all instances of this are now due to either outdated files, servers needing a restart, or corrupted installations triggering BattlEye.

Two most common reasons for this scenario: 1. Your client passed a null-object to the server as your player avatar. This can happen either because of an outdated dayz file, or more rarely because of a poor initialization of the mission (it has sent the message to authenticate before it has created your avatar). 2. The authentication was not processed. The server is designed to abandon difficult or problematic requests, so that it doesn't hang. It will try ten times to authenticate you, and if it can't, it will give up. In both cases, the best thing to do is to reconnect. Restarting ArmA can help greatly with initialization issues.

Thats the plan, I actually have checking in/out coded. But HIVE is under alot of pressure, until we release the .NET version (rather than the current C++ version), I am minimizing the calls especially read/writes.

It only spawns zombies per player. In a fifty slot server, there will be many, many more zombies than on a server with only 5 or 10 people. Currently, the system will stop spawning zombies around you when there are 20 around you. However, if you move away more can spawn with the others still spawned. The system is very careful with zombie numbers and removes locally spawned zombies on disconnect. There are many competing schools of thought on the zombies currently, and where such disparate viewpoints exist I tend to leave the system alone until a compelling argument exists - hence what I have not done much with this area. If, for example, I remove the random chance that a zombie will knock you out - zombies become even less of a threat. As many have found out, it only takes one zombie with a lucky hit to kill you. ArmA2 has a limitation on the number of agents/units it can support. We have had over 1800 on a server before, but this is very problematic with warping and all sorts of desync issues. It is the kind of thing that will be tweaked and developed going forward. Remember that games like L4D also have rather low limits on the quantity of zombies, its just the way they come in that makes it seem like large numbers.

Need more info, such as when the heli was last entered/exited. How soon after that the server had crashed - really all the info you can. For obvious reasons, the server cannot sync vehicles like players - because if the server crashed while the vehicle was moving it would spawn in the air. It syncs on getout of a player, and if you disconnect while near it.

Pro-tip. Don't forget to use clearWeaponCargoGlobal rather than clearWeaponCargo lol... Thanks for highlighting that - fixed in 1.5.5

I think actually for the most part there is agreement. Generally speaking, myself included, we don't think there can be a restrictive mechanic for it. But there needs to be more incentive to team up, which is natural in the real world. This is going to take some time to be implemented, its not a simple one or two line code change. Persistent fortifications are a test of the ability for the server to handle large numbers of objects, so we will see how that goes.

I just did a database scan, 697 characters have a toolkit. However 360 of them are dead.

Scrap metal and toolkit. Has anyone seen a toolkit yet?

You put it a bit more politely than I did :D Sorry about that folks. I'll be replacing those objects with scrap metal. So out of scrap metal you can repair things or make tank traps.

The initial vehicles which spawn in-game are all badly damaged with no equipment. So if you find something like that, then it's a player's hard-earned treasure.

Right now, I think the last thing we need is more players! Certainly some publicity will be good in the future, but people forget this only JUST went alpha, it still has all the "meat" of the features to add - it's essentially a rough proof of concept. It's also still very buggy, unpolished, and unstable. I think before any real publicity is done these issues need to be addressed. I only announced it on the BI Forums because it had reached the point where it needed capacity testing. I hadn't actually intended it to be enjoyable, at least in a long term sense, in its current state.

Should be.

Yes, uh. Its supposed to be a pile of metal for you to make Hedgehogs (tank traps) out of. Unfortunately, it binarized wrong and came out looking like a bunch of shit.

Alright alright. Enough already! I've taken it out for 1.5.4. And I've put some soft-toys and My Little Pony skins to make up for it.