Jump to content

Outhouse/Black Hole


Recommended Posts

I know this was mentioned in the anoucement thread of QoL2 but im just wondering if anyone out there knows a way around the black hole? Ive tried debug "Destroy", CTRL + F4 and deconstructing, etc. no luck. If nothing else I'm kinda hoping the developers will hotfix it if more attention is drew to it.

I just cant get enough of this game. 700+ hours in already and i keep going back for more!

Link to comment
https://forums.kleientertainment.com/forums/topic/102397-outhouseblack-hole/
Share on other sites

Looks like Klei wanted to fix that exploit where you get 200kg of dirt and 100.5 kg of polluted dirt when you deconstruct full outhouse. This caused side effect that you cannot deconstruct outhouses at all.

I'm wondering how Klei testers team is testing such cases? Do they receive some change note for code and they test changed features and areas around it? This is what happens in my company when new software revision was received. So if they do in similar way then how tihs problem was not detected if it is 100% occuring each time on everybody's comupter.

Or maybe Klei rely only on players as testers?

1 minute ago, Angpaur said:

Looks like Klei wanted to fix that exploit where you get 200kg of dirt and 100.5 kg of polluted dirt when you deconstruct full outhouse. This caused side effect that you cannot deconstruct outhouses at all.

I'm wondering how Klei testers team is testing such cases? Do they receive some change note for code and they test changed features and areas around it? This is what was done in my company when new software revision was received. So if they do in similar way then how tihs problem was not detected if it is 100% occuring each time on everybody's comupter.

Or maybe Klei rely only on players as testers?

Or maybe the dev team never got around to deconstructing outhouses while testing the changes.  Sometimes little things get overlooked.

10 minutes ago, KittenIsAGeek said:

Or maybe the dev team never got around to deconstructing outhouses while testing the changes.  Sometimes little things get overlooked.

Only it isn't little thing.

This is what could happen if it is really a side effect of an attempt to fix outhouse exploit - a tester receives a change note where it clearly states that code was changed in outhouse deconstruction functionality. So first thing a tester should check is if deconstructing outhouse still works well.

But this is still under assumption that it is the side effect I described and that Klei test their code in a way like it is done in my company. I could be totally wrong, but I judge it from my experience perspective as former tester and now a developer.

I tend to think that they rely on the community to do the testing. Which is fine by all means. But if that is in fact the case I would honestly like to see more communication between the developers and the community. I mean they do talk with us. But from the few threads I've read through that actually seemed to get a decent amount of attention there still wasn't a developer commenting on it. I guess what I'm trying to say is that if they are in fact relying on the community to test, (and even if they aren't) I would AT LEAST like to see more acknowledgements that they're listening to the community and to our recommendations and complaints. eg. the poll about the new printing pod by Lilalaunekuh

I guess that what gets fixed depends on the number of devs and their experience.  An experienced dev will be more likely to fix a complex issue, but it takes time away from fixing other complex issues.  Then the patches need tinkering to fix any breaking changes.

On a plus side, I am very glad that the development team isn't Bethesda, as the recent calamities over recent Fallout 76 cock ups patches seems just too comical.  They've even released patches that accidentally rolled back the version, applying old bugs that had been fixed instead of applying fixes for new bugs.  Now they have to fix old bugs again, as well as the bugs that were originally intended to be fixed by the patch, which is just amateur hour at it's finest.

34 minutes ago, Angpaur said:

I'm wondering how Klei testers team is testing such cases?

I case you missed it. We are the testing team. It's an early access game, and in order to speed up development Klei did away with testing before releasing previews.

<-- you see that badge? It says "alpha contributor" which means I was one of those on the test team before they dispensed with testing.

It always amused me working as a software developer at a particular company, they hired testers at about 1/2 the hourly rate of the developers, yet they only hired 1/2 as many testers as developers, but expected the developers to do most of the testing on the software we wrote.  In actuality, they were paying over the odds for developers to do the job of testers instead of just hiring more testers and saving themselves some money while shortening development time.

2 minutes ago, Craigjw said:

It always amused me working as a software developer at a particular company, they hired testers at about 1/2 the hourly rate of the developers, yet they only hired 1/2 as many testers as developers, but expected the developers to do most of the testing on the software we wrote.  In actuality, they were paying over the odds for developers to do the job of testers instead of just hiring more testers and saving themselves some money and lengthening development times.

In my company, there is no testers on the project I'm working. All the testing is done by the devs. It works pretty well but we are only 5 in the team so there's not much work done every Sprint. I don't know if it would work if we were to be 20 devs or so.

6 minutes ago, Saturnus said:

I case you missed it. We are the testing team

And that is the thing that bothers me - software developer should have testing team, to at least test basic things before delivering to customers. We paid for this game and even if it is early access we are theirs customers. A customers who accepts the fact that game is still under developement and some of as are willing to help by testing and bug reporting. But this doesn't mean Klei is supposed to throw all testing responsibility on us, especially if we do it voluntary.

You see, if you have 2 testers and 4 devs, you'd get more development done instead of testing, while the software is tested more thoroughly and bugs are caught quicker and you find more bugs.

Don't get me wrong, development does require some testing, but not when you are doing more testing than development.

I'm also not suggesting that you lose 1 member of your team, just to hire 2 testers.

17 minutes ago, Angpaur said:

And that is the thing that bothers me - software developer should have testing team, to at least test basic things before delivering to customers. We paid for this game and even if it is early access we are theirs customers. A customers who accepts the fact that game is still under developement and some of as are willing to help by testing and bug reporting. But this doesn't mean Klei is supposed to throw all testing responsibility on us, especially if we do it voluntary.

You're complaining about a testing branch of an early access game?

What.

They do do basic testing before delivering it to us. With a group of volunteers that opt into the testing branch.

2 minutes ago, Yunru said:

You're complaining about a testing branch of an early access game?

What.

They do do basic testing before delivering it to us. With a group of volunteers that opt into the testing branch.

You're right - it is a testing branch and I opted for it voluntarly and I'm not annoyed that a bug occured.

I'm just worried if things haven't gone too far that software developers are now using strategies to cut costs by relying only on testing done by their own customers. Some basic testing still should be performed on developer side and I think we, as customers, should not allow companies to cross certain line and speak up when it happens.

Maybe I'm over-reacting the whole thing, but such tendencies to release buggy code are becoming more common in all game industry and gamers should not just accept it and sit silent.

Even in early access, the quality of development of this game is leagues beyond that of a AAA title like Fallout 76, which is probably several orders of magnitude more costly to develop & has been fully released to boot.

Klei get too thumbs up from me, their quality of work and dedication is fantastic.

Lets take Ark as an example.  Their devs haven't even played the game, don't want to play the game and they have no contact with the community at all and never listen to anything the community asks, begs or demands and the people who do go on the forums to talk to the community are there for advertising purposes and community firefighting.  Plus, bugs generally take at least 6 months to fix.  The quickest player support your likely to get is at least 2 weeks.

EA is another example, if you look at the number of really successful software houses and franchises they've bought, they've stripped all of them, ruined their franchises and monetized every game they have gotten their hands on, to the point that nearly every game now released is pay to win, the only exception is Overwatch, which they have massive advertising revenue on.  For EA, their only incentive to making games is to make money on and not what US the players want.

Fallout 76? Ark? Do we really should try to compare to the worst, instead the best?

But only question is who is really better than Klei? ;)

I don't want people here to think I'm bashing Klei. I still admire them for the overall great work. But I think that things would be better for everybody if they have a testing team to at least do basic check of changed, existing functionalities to detect side effects.

In case of new functionalities or features I think it is ok to just give it for testing on beta branches, becasue this is what they are for. 

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.

×
  • Create New...