Dirty Bomb "Update"?

(Jan S.) #1

EDIT:

So yes, it is previous version, because of broken deliverables.
DB really needs bigger dev team because these issues are so common that it’s not healthy anymore.
Every time I defend DB somewhere this happens…

So, there is an “update” for dirty bomb right now to download, but according to steamdb, it is actually the same version that we had before yesterday’s maintenance.
What’s going on?

(GatoCommodore) #2

so its the game rollback but not the map right?

(bontsa) #3

Rollback of the hotfix.

(Jostabeere) #4

I repeat myself, but I start to see a pattern. Again.

(The_True_mo) #5

…

(Nail) #6

I see, so you’d rather they didn’t fix it

welcome to Beta testing

(strawberryJacket) #7

Paragon is a real beta, DB only use beta tag to have an excuse.

(The_N00Ba) #8

What is the definition of Beta testing these days?

(AlphaUT) #9

Beta testing is testing.

(KUST__LunarTM) #10

Probably because the game doesn’t function as well as the devs would like that the game is still in Beta. Although, it’s not very common to have extremely long betas to the point where players fulfill all their enjoyment from the game and leave before it officially goes “live.” Changes and reworks to the game can still be made out of Beta, Overwatch is a prime example of such; the game is fully released and changes are constantly being made to the characters, switching up the meta from time to time, but those changes are more content related whilst the things DB is said to be working on is more along the lines of the actual game code to improve how the system itself works.

(Jostabeere) #11

[quote=“Nail;214342”]I see, so you’d rather they didn’t fix it

welcome to Beta testing[/quote]

I’d rather have bugfix that does not create more bugs so a rollback is needed.

(Nail) #12

and I’d like to win a lottery, guess what

(Jan S.) #13

[quote=“Nail;214342”]I see, so you’d rather they didn’t fix it

welcome to Beta testing[/quote]

But they didn’t fix it. They just rollback to previous version, that’s not fixing.
It’s nice that almost every comment you do on these forums is defending the game, but you can’t overlook these issues appearing almost after every update.

I was going to ask you what will you do when these issues will appear after leaving beta, but at this pace, that won’t happen very soon.

(Mister__Wiggles) #14

Beta is just a tag that is thrown around these days. Has little to no substance. Dirty bomb isn’t a beta and hasn’t been for a long time. It’s just a tag that devs use as an excuse for making mistakes really. SD need help, the team is tiny and they clearly ate so stretches that they can’t even test an update properly. Just invite players to test a closed branch for you, would kill 90% of bugs before they are released. Sorry but if the Christmas event comes along and there still isn’t a fix in play then I’m done.

(ENDgie) #15

I feel the DB team periodically forgets they are a beta. I mean for a while they were doing content updates like Rouge en Vouge then it seems like they remembered “oh we’re a beta and this game isn’t in a completed state yet” and switched focus to fix/polish updates like Summer Squash and MOFO.
I do hope that they stop holding onto the security of being a beta in the near future (though there are things indeed that need fixing before that) and I hope nexon gives some marketing for DB when it releases officially whenever that is to make up for some of the players lost from length of beta by making it known to new players.

(bontsa) #16

[quote=“Wikipedia”]Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. Software in the beta stage is also known as betaware.[2] Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, preview release, prototype, technical preview / technology preview (TP),[3] or early access. Some software is kept in perpetual beta, where new features and functionality are continually added to the software without establishing a firm “final” release.

Beta testers are people who actively report issues of beta software. They are usually customers or representatives of prospective customers of the organization that develops the software. Beta testers tend to volunteer their services free of charge but often receive versions of the product they test, discounts on the release version, or other incentives.[/quote]

Go read yourselves too by all means, the article continues after that.

We’re testers. Deal with it. If you can’t handle incomplete features and fragile code, play something else. Nothing wrong in that. Sure these things can be and are frustrating, and that can be expressed in a manner that is constructive, but in the end of the day DB is (at least seems like) SD’s passion project that will take considerably long to be done in the way they are happy to call it “released”.

@JohnS Sure these issues are something that they will have to start taking lessons from, but I fail to see how rolling back to previous version after first trying to figure out the bug for entire workday, is “not fixing”. Decisions have to be made at some point, as you should know there is no emergency work duty in software development the same way in i.e field of medicine.

(Jan S.) #17

I agree with you @bontsa, but I still believe there should be more people working on the game.
Development progress is slow, bug fixes bring even more bugs and PTS clearly isn’t enough. (through I will not say what do I think about it because that would probably just mean lock of this thread).

This technique may allow a developer to delay offering full support and responsibility for remaining issues.

I think this is basically what’s with DB right now. We have store, we have DLC packs, we have events (that we can spend money on even through they mostly don’t work properly).
I support SD and Dirty Bomb. I defend it where I can, but these are facts.
Updates are being released in huge packages instead of in smaller ones. I understand why that happens sometimes (like MOFO update), but for bug fixes, I think updates should be more common - especially in beta.
SD are aware of some bugs and they have them fixed, but they wait for example one month to release it because other fixes “have” to be released with it.
That sounds more like “final product system”.

If you can’t handle incomplete features and fragile code, play something else.

I think we all here can handle that. But repeated mistakes are something else.
Fletcher’s stickies were fixed 2 times since the bug appeared, but somehow it’s still not fixed.
The reason why I write here is not because I can’t handle it, but because it’s getting repetitive and obvious that there’s something wrong with development. It’s because I care about the game and I want it to succeed. We are using forums, we know what’s happening, but majority of DB players don’t even read changelogs or don’t watch dev videos. And repeated mistakes like that, slow development…that all is the reason DB’s players are leaving. And if this would be any other dev team than SD, I wouldn’t be here anymore.
I don’t know everything about game development and I understand it’s one of the hardest things to do. But if DB will continue like this, it’s not going to have bright future.
It’s my opinion and I might be completely wrong here. But that’s how I see it right now.
I’m sorry for this wall of text.

(Nail) #18

“I don’t know anything about game development”

fixed that for you and that’s your answer

(bontsa) #19

[quote=“JohnS;214429”]I agree with you bontsa, but I still believe there should be more people working on the game.
[/quote]

Can’t disagree with that, but then again it’s not the DB team itself at fault for that. I’m not saying you said so, but some people around these different platforms should keep that in mind.

[quote=“JohnS;214429”]

This technique may allow a developer to delay offering full support and responsibility for remaining issues.

I think this is basically what’s with DB right now. We have store, we have DLC packs, we have events (that we can spend money on even through they mostly don’t work properly).
I support SD and Dirty Bomb. I defend it where I can, but these are facts.
Updates are being released in huge packages instead of in smaller ones. I understand why that happens sometimes (like MOFO update), but for bug fixes, I think updates should be more common - especially in beta. [/quote]

Glad to see you actually read the article I posted, was waiting for someone to point that line up. Just personal opinion, but DB’s situation is somewhat more complicated than due the fact developer is also bound to publisher with certain things and entire product is running live as we speak.

Despite all the crap Nexon support gets, can anyone honestly hand on their hearts say they do absolutely jackshite? No. Things could be done more efficiently for sure, that’s always a thing, but if anyone remembers Xinpoopcode times, well, yeah.

[quote=“JohnS;214429”]SD are aware of some bugs and they have them fixed, but they wait for example one month to release it because other fixes “have” to be released with it.
That sounds more like “final product system”. [/quote]

Not for me, sounds more like “way too much work with way too little crew resources”- thing. And in this case I am not referring to only amount of crew, but efficient usage of them. See above at “everything can be done more efficiently”. We have no idea of knowing where the real issue lies, so we shouldn’t take much stance on that.

[quote=“JohnS;214429”]

If you can’t handle incomplete features and fragile code, play something else.

I think we all here can handle that. But repeated mistakes are something else.
Fletcher’s stickies were fixed 2 times since the bug appeared, but somehow it’s still not fixed.
The reason why I write here is not because I can’t handle it, but because it’s getting repetitive and obvious that there’s something wrong with development. It’s because I care about the game and I want it to succeed. We are using forums, we know what’s happening, but majority of DB players don’t even read changelogs or don’t watch dev videos. And repeated mistakes like that, slow development…that all is the reason DB’s players are leaving. And if this would be any other dev team than SD, I wouldn’t be here anymore.
I don’t know everything about game development and I understand it’s one of the hardest things to do. But if DB will continue like this, it’s not going to have bright future.
It’s my opinion and I might be completely wrong here. But that’s how I see it right now.
I’m sorry for this wall of text. [/quote]

Yep, you’re not alone with thoughts about slow development. But one of the golden rule with long-term changes is “if something (issue) has taken a year to develop, it takes at least a year to completely fix it”. We’re estimating whats happening behind the scenes we know pretty much nothing of. Even if they have problems they are actively fixing, it will take quite some time for us end-users to see it. And it’s pretty much none of our business. We vote with out presence and wallets.

It’s completely understandable if one doesn’t have the time to give to them, but I got so I’m not leaving this boat. Neither are Sagans and such taking a break, as they themselves keep saying they’ll be checking on the situation.

[spoiler][quote=“JohnS;214429”]Development progress is slow, bug fixes bring even more bugs and PTS clearly isn’t enough. (through I will not say what do I think about it because that would probably just mean lock of this thread).[/quote]

Mods close derailed and unnecessary, uncivilized discussion/banter/raging. I hardly believe stating such opinion out loud as itself would result in lock. It’s the more vocal less thoughtful and less constructive side that makes that happen.[/spoiler]

(Jostabeere) #20

[quote=“Nail;214439”]“I don’t know anything about game development”

fixed that for you and that’s your answer[/quote]

With your age, experience and game development knowledge you could act less like a child and explain what you actually want.
Or you explain why the people are wrong instead closing your eyes, ears and nose and screaming: “Everything is perfect, you’re just wrong and stupid” when someone critizising your favourite game or your favourite dev team which obviously both have issues right now.