ImpulZ

This one is not a bug, there is just no key assigned to it yet, same goes for holding breath or the free look. It will be addressed in a controller overhaul. The existing fire mode switch is an exploit. This is one of our prioritized tasks both on PC and Xbox. We are working on a more elaborate climbing/vaulting system, but this is not going to be implemented this year. Reloading and resulting issues with hit registration are known problems the team is looking into. Will be fixed soon. :) While we listen to our Community at all times, we have to prioritise our work, as any company has to.

Both issues are known and they should be resolved pretty soon. :)

Hello survivors! We have a new Xbox Update for you today, servers are offline until then. Fixed VoIP issues while in an Xbox party Fixed crash while disconnecting from a server Fixed character in water in the main menu Fixed issues with magazines and reloading Improved title stability This update will include a complete character wipe for all Xbox players to free all players locked in database! Don't forget to restart your consoles. We are looking forward to your feedback!

I know you probably did not mean it that way, but as you mention it: Devs are not wizards, they are people that do hard work. Too often folks expect us to do some magic, because game devs seem like wizards. But we can't make things magically appear, behind every small thing you see in the game hides a lot of work. :) But that was off-topic from my side, sorry for that.

Just reminding you guys that this discussion is about finding a good entrance to game servers, not about an ethical evaluation of server switching. This is starting to get a bit out of hand, so keep your cool and refrain from making this personal.

So you are able to start the game and get into the server browser? What happens when you try to join a server, do you get an error message?

Yes.

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)