ImpulZ

Thank you for reporting this. This is a bug with the sickness system that causes a hemolytic reaction when you give yourself blood. It is acknowledged and the team is working on a fix.

Rebinding keys is not supported in the game yet. We know this is troublesome especially to many left-handed players out there, but it will return to the game eventually.

No auto-run in DayZ, sorry.

Will both be assigned with the next overhaul of the controls.

The fire mode switch is not working as intended (should be quite obvious) and thus there is not definite bug when it's not working at all. We are looking into reworking the design for the fire mode switch.

If any of you are experiencing this kind of frame drops, please report the issue to our Feedback tracker at feedback.dayz.com. If you are new to reporting, please follow this guide.

Optimisation is an ongoing process, we understand this is an issue and will try to work continuously to ensure a smooth experience on all consoles.

This is a known issue, we are working on resolving the sending of the verification mail as soon as possible, you should receive it later.

The DayZ Server Files have been released for PC. Private server hosting for Xbox is not possible yet.

Regarding running/jumping you might be low on stamina or carrying to much weight (reducing your stamina below a critical level on which you are not able to sprint/jump any more). You might not be able to switch your items because you don't have the space in your inventory to store the item from your hands.

While DayZ is striving to be an authentic survival experience, first and foremost, it is a game. Just to ask behind your own questions: Would it be realistic or fun to have an entire tree of apples at all times? Would you rather have each tree wear it's apples only once a year? Realistic, but definitely not fun in a game. Same for water in every building, would it be realistic to have fully functioning water support in the post-apocalypse, and would it be fun? -- Digging multiple worms was possible and might be possible again, anyway it is not a priority right now. More a question of balancing once we move towards/past 1.0. Continuing to work with soda cans is also an interesting thought (we had for example concepts of traps with them), but filling not closable cans with water while running around might not be the best idea in terms of realism and making any fluid container reusable might not be fun either.

There is no possibility on Xbox right now to define your spawn point. It is very likely the guy just had very lucky respawns (there is a major cluster of respawn points at the southeastern shoreline), and that he just found it funny to hunt you down as he saw his lucky spawns.

You are not the only one affected, we are getting swarmed with this kind of requests. So we have to find a general solution for this problem.

If you are stuck somewhere, please report the location and your GamerTag to our Feedback Tracker at feedback.bistudio.com

Is the problem fixed now? After downloading yesterday's update you should be able to see servers again.

How to Ban There are currently two ways to ban players from a server: Create a file ban.txt in the server root folder and add the player UID in a new line (44 characters long id that you can find in .adm or .rpt logs) Create a file bans.txt in the serverRootDirectory\battleye folder and add the player BE GUID in a new line (32 characters long GUID which you can get from RCon tools like Dart or BEC). The location of the BattlEye folder can be customized via the startup parameters -bePath and -profiles. Some RCon tools like Dart offer the option to ban users directly via their UI which is then, written to bans.txt.

Hello survivors! We have a new Xbox update for you today (approximately 3 PM CEST). Fixed the registration of player/infected hits (from a gun) when the player has a slower connection to the server Fixed a possible cause of the player character corruption in the database Fixed multiple server crashes (increased stability of the game) Fixed the inability to damage headgear/hat/helmet Don't forget to restart your consoles. We are looking forward to your feedback!

The minimum requirements (provisional) for running one server instance are: OS: Windows Server 12-16 or Windows 10 (Linux server hosting is not supported yet) Processor: Intel Dual-Core 2.4 GHz or AMD Dual-Core Athlon 2.5 GHz 6 GB RAM 2.5 GB space on the drive SSD for logs/install (highly recommended)

Server Economy - Documentation We are providing samples of relevant offline mission files on our Github

BattlEye Configuration The config file BEServer_x64.cfg needs to be in the same folder as BEServer_x64.dll.The location of this folder can be customized via the startup parameters -bePath and -profiles. Parameters: RConPassword MyPassword - Sets the password for the connection of the RCon tool (remote connection admin tool like BEC/Dart) RestrictRCon 1 - Enables/Disables RCon functions (kick/ban/connection restrictions)

Launch Parameters You can find a complete documentation of the launch parameters on our Community Wiki

Config Parameters The server configuration is handled via serverDZ.cfg, a configuration file which you can use to configure various game server settings such as the player count, 3rd person view, and welcome messages. etc. The file usually is located in the root directory of the server but can be placed elsewhere with the startup parameter -config. To ensure, that Steam does not overwrite this file with an update, be sure to have a copy of this original file and rename it. You can find a complete documentation of the server configuration file and its parameters on our Community Wiki

There is a 15 second logout counter when your character stays vulnerable after leaving the server. We are aware that combat in DayZ can take it's time and can be pretty nerve-wrecking, which is why many folks decide to use the coward's way out. Ghosting is a problem resulting from this. However, keep in mind that it takes several minutes for someone to log around you. If someone does not even peak his head for a minute, there might be something off. The team is keeping an eye on the situation and we hope once the database locks are working as intended to have more limitation to those exploits.

There are still ongoing inventory optimisations, so we will work on fixing the mentioned frame issues and crashes.

We are in the process of testing new fixes to resolve the situation. We apologize for the inconvenience and hope to set all affected players free as soon as possible.