Page MenuHomeFeedback Tracker

Experimental Not Achieving Intended Outcome
Feedback, NormalPublic

Description

Again, new bugs have been found on stable after a month on Experimental. Why were these things not spotted? Just playing the game yourselves would have been enough to spot them. Everyone is noticing them, so why were they allowed through?

What's changing from Experimental to Stable? Or is it a case of Experimental not achieving its intended purpose?

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 7
Category
General
Steps To Reproduce

Play stable.

Event Timeline

I’ve been wondering this too.

I played the experimental servers and clipped a number of instances where bugs showed up. I was planning on uploading the clips to this forum the next day. When I woke up, DayZ had announced that they were rolling out the patch to stable.

My first thought after the bugs started showing up was, “Do the devs seriously not test these updates before they roll them out?” One hour of gameplay would have shown them all of these issues.

So, are they just not testing it themselves? They can’t afford to pay someone to play the game for one hour and identify these issues?

It just doesn’t make sense and it frustrates the community.

Geez changed the task status from New to Feedback.Mar 3 2025, 11:09 AM

I think there needs to be something more done to incentivize players to play experimental. When a new experimental update is announced, I do tend to go report issues when I can, but the servers are almost always empty on console so there is no reliable feedback loop. I think more players would play if scenarios were created to test specific changes, like the arena that was setup to test melee weapons a few updates ago. I get the impression most bugs are found and tested in isolation, rather than in a dynamic gameplay session mimicking a player journey.