Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

Sign in to follow this  
chefwillis

Release Bug Fixes ASAP

Recommended Posts

My suggestion is simple and to the point. I suggest the Dev team releases big fixes as they are completed on a day-to-day basis.

Meaning if 3 bugs are fixed on Day x then release the hotfixes containing those fixes on Day x+1.

You don't wait weeks to fix bugs. It shouldn't work like that. Bug fixes shouldn't have to come with additional content they should just come as soon as they are completed.

Sure it might mean installing patches daily, but taking 5 minutes away from your times is better than taking 3 hours because you died or lost progress because of a ridiculous bug.

This is not a rage thread, do not mark it as such. I haven't played in over two weeks so 1.7.2 hasn't affected me at all, but the bug reports are rampant and there is nothing being released to fix it, instead we are forced to wait for other side-projects to be completed.

Share this post


Link to post
Share on other sites

World hunger, world peace, addiction and man's inhumanity to man are next on the list..

Fixes take time.... Did you really think that posting this would somehow make them slap their foreheads and have some kind of epiphany?

  • Like 1

Share this post


Link to post
Share on other sites

Fixes take time.... Did you really think that posting this would somehow make them slap their foreheads and have some kind of epiphany?

The mental image your post produced made me lol... but I think what he's saying is for them to introduce smaller-scale patches, and I'm inclined to agree. This is alpha- let the people whine and complain if a bugfix release doesn't work, or there aren't new features... there's no better way to test than using the public, and we're happy to be of help.

Share this post


Link to post
Share on other sites

World hunger, world peace, addiction and man's inhumanity to man are next on the list..

Fixes take time.... Did you really think that posting this would somehow make them slap their foreheads and have some kind of epiphany?

Do you really think any of these things in the sub-forum do? No. Of course not. And of course fixes take time, unlike you, who didn't take the time to read the post.

It isn't like 20 bugs are fixed at the exact same time. They are fixed(or at least attempted to be fixed) on a day-to-day basis. So as soon as the fix a couple of bugs within a few days, they release a hotfix containing those fixes, despite there being more bugs to fix.

Share this post


Link to post
Share on other sites

It's an Alpha. They are very likely working their asses off, trying to fix things.

The thing is, when you "fix" one thing, and quick testing shows that it's really fixed, it most likely has broken something else, somehow.

The DayZ team - to my understanding - is not that big of a group, compared to actual game developers or the bigger mod developers.

They just can't fix things daily AND test that they actually WORK.

And don't get pissed at me for saying "it's an alpha."

Even if it was beta/full release, it would likely take EVEN LONGER to make patches and test them out.

Share this post


Link to post
Share on other sites

It's an Alpha. They are very likely working their asses off, trying to fix things.

The thing is, when you "fix" one thing, and quick testing shows that it's really fixed, it most likely has broken something else, somehow.

The DayZ team - to my understanding - is not that big of a group, compared to actual game developers or the bigger mod developers.

They just can't fix things daily AND test that they actually WORK.

And don't get pissed at me for saying "it's an alpha."

Even if it was beta/full release, it would likely take EVEN LONGER to make patches and test them out.

But that's the whole point of the alpha, for us to test out the stuff they probably broke in an attempt to fix something. I'd rather get just a couple of bugs, from smaller releases, than a swarm of bugs from a larger release, it takes too long to document each bug and find out what is actually causing the problem, thus wasting everyone's time.

Share this post


Link to post
Share on other sites

Do you really think any of these things in the sub-forum do? No. Of course not. And of course fixes take time, unlike you, who didn't take the time to read the post.

It isn't like 20 bugs are fixed at the exact same time. They are fixed(or at least attempted to be fixed) on a day-to-day basis. So as soon as the fix a couple of bugs within a few days, they release a hotfix containing those fixes, despite there being more bugs to fix.

I guess you've only worked with software as a user. That's ok. I will explain.

You do what you THINK fixes one bug. How do you know it works? You test.

I. Order to more realistically release content, very bare bones testing is done at intervals. It's usually called unit testing. Does e program crash? Lock up? Have an egregious memory leak?

What you proposed would slow velopment to a crawl.

Fix tiny thing. Test.

Still broken.

Test.

Still broken.

Test.

Release.

Fix second thing.

Test.

Still broken.

Get reports that new things have developed with the first bug.

Go back to fix and test cycle with first bug and ignore second bug. Only which code do I work with? The branch where I thought the first bug was fixed, or after, when I had done work on the second bug...

Oh gee. Maybe I should have fixed several things and then done unit testing...

There's a reason no one fixes in very tiny steps.

The server and client side updates are already a shit whirlwind with releases every few weeks. You want what, daily releases?

You're basically asking a chef to cook a meal one bite at a time.

Share this post


Link to post
Share on other sites

I guess you've only worked with software as a user. That's ok. I will explain.

You do what you THINK fixes one bug. How do you know it works? You test.

I. Order to more realistically release content, very bare bones testing is done at intervals. It's usually called unit testing. Does e program crash? Lock up? Have an egregious memory leak?

What you proposed would slow velopment to a crawl.

Fix tiny thing. Test.

Still broken.

Test.

Still broken.

Test.

Release.

Fix second thing.

Test.

Still broken.

Get reports that new things have developed with the first bug.

Go back to fix and test cycle with first bug and ignore second bug. Only which code do I work with? The branch where I thought the first bug was fixed, or after, when I had done work on the second bug...

Oh gee. Maybe I should have fixed several things and then done unit testing...

There's a reason no one fixes in very tiny steps.

The server and client side updates are already a shit whirlwind with releases every few weeks. You want what, daily releases?

You're basically asking a chef to cook a meal one bite at a time.

1. You are wrong, I am a programmer. Two, you are wrong, you code in segments, not the entire game all at once. Three, you still don't undrstand what I'm trying tosay. I'm trying to say that bug fixes shouldn't have to wait to be released because of new content that is being added. Also, I was saying day-to-day hypothetically. It isn't ALWAYS day to day. And of COURSE you need to test code that references other code that may cause other errors within other code. Of course you need to test it bit by bit. But the things that are already fixed or what they think is fixed should be release with the hindrance of wanting to throw in a few other special treats in with the next build. But when you get all those things ironed out, you release it, you don't wait, and then say, "oh i think this might be the right time to release it." No you release it ASAP(As soon as possible(meaning if it isn't feasible you dont release it, hence the as soon as possible part))

If the bug fixes they release cause more bugs, then good! We know what the problem is and can be fixed easier. Or would you rather have an entire game that runs off of paperclips and twigs?

If they don't want to fix it within this update then they won't fix it! Not hard to figure out really, they can always fix it later and release content that causes more bugs. They don't have to fix the entire thing bit by bit. We test it for them and release the bug reports. They get the bug reports and fix them on their own time. But when they have a fix for the bugs or one they think works, they should release it as soon as they can.

Edited by chefwillis

Share this post


Link to post
Share on other sites

My suggestion is simple and to the point. I suggest the Dev team releases big fixes as they are completed on a day-to-day basis.

Meaning if 3 bugs are fixed on Day x then release the hotfixes containing those fixes on Day x+1.

You don't wait weeks to fix bugs. It shouldn't work like that. Bug fixes shouldn't have to come with additional content they should just come as soon as they are completed.

Sure it might mean installing patches daily, but taking 5 minutes away from your times is better than taking 3 hours because you died or lost progress because of a ridiculous bug.

This is not a rage thread, do not mark it as such. I haven't played in over two weeks so 1.7.2 hasn't affected me at all, but the bug reports are rampant and there is nothing being released to fix it, instead we are forced to wait for other side-projects to be completed.

and this one gets the award "Not a f***ing clue how programming works entirely"

in an alpha, you dont prioritize on fixing existing bugs, you want to find out how the game should be and what kind of stuff should be added

when the game has all the stuff the developer wants to put in, then the bug fixing can occur, since when you go "new stuff -> bug fixing -> new stuff -> bug fixing" it will take forever to complete the game

instead, put everything you wanna have in there, and then fix the bugs in one big swoop

also, the people who work on DayZ probably dont get paid for it, and even if, it wont be much, so dont be that silly guy demanding stuff for free without any right to demand it

Share this post


Link to post
Share on other sites

and this one gets the award "Not a f***ing clue how programming works entirely"

in an alpha, you dont prioritize on fixing existing bugs, you want to find out how the game should be and what kind of stuff should be added

when the game has all the stuff the developer wants to put in, then the bug fixing can occur, since when you go "new stuff -> bug fixing -> new stuff -> bug fixing" it will take forever to complete the game

instead, put everything you wanna have in there, and then fix the bugs in one big swoop

also, the people who work on DayZ probably dont get paid for it, and even if, it wont be much, so dont be that silly guy demanding stuff for free without any right to demand it

This gets the award of "Not reading the f***ing posts." I'm not saying to fix bugs immediately after new build

I'm saying RELEASE THE BUG FIXES AS THEY ARE FIXED. This has nothing to do with prioritizing. This has to do with releasing fixes as they fix them. Does everyone that thinks they know something about software an asshole?

Let me say it again. When. they. fix. the. bugs. while. doing. their. normal. programming. and. build. releases. they. release. said. fix.

This. has. nothing. to. do. with. prioritization. It. merely. has. to. do. with. releasing. the. work. they've. already. done. to. our. benefit. without. having. to. wait. for. the. next. build.

One more time.

Nothing. to. do. with. prioritization.

Nothing.

This is how it goes release > bugs found > code for next build > code a few bug fixes that would normally go in next build > release bug fixes if it doesn't mess anything more up or isn't for that build > release next build.

I'm not being a silly guy demanding stuff. You obviously don't know what subforum you are in. It's called suggestions. If I were "that guy" everyone in the subforum is "that guy"

Edited by chefwillis

Share this post


Link to post
Share on other sites
Sign in to follow this  

×