PC RWG Just When you think it can't get any worse

Really ?i love the last map i played

AD5C915823603824FD20F6EBD4FE475BEFF80756
Click to expand...
That is what a good map looks like.

I'm playing less and less of 7dtd since a17 hit, I like some of the changes, but others just really kill the game for me: encumbrance from inventory slots, move speed reduction from armor, the stam regen reduction from armor also sucks. These 3 issues are some of the major ones why I am losing interest in the game. Bascally I dispise moving slow in games, and it feels like its punishing me for using armor and my inventory in 7dtd.
The game needs more blood and gore, if I shoot a zombie in the face with a shotgun I expect his head to explode if its a shot that would have killed it or something. I'll even take the a16 dismemberment system over a17 anyday. Sledgehammer should be literally smooshing heads as well.

I also find it boring how everything is perk based now, I miss needing to find books to make things, it made exploration more exciting when you finally found that book you needed.
Click to expand...
Ive almost entirely retired playing this game as well,

Speed and stam penalties are just too harsh, and I hate that you can craft everything , if high Int allowed you to read and learn from the more advanced books would have been a great way to merge these two things.

Too much emphasis on realism is destroying the " Fun Factor"

 
Last edited by a moderator:
Not ready for testers but is ready for publish. This reads like a brand new meme.

TFP, please just admit pushing this was a mistake and we can all laugh at it.

 
Not ready for testers but is ready for publish. This reads like a brand new meme.
TFP, please just admit pushing this was a mistake and we can all laugh at it.
Click to expand...
Since you don't seem to understand let me spell it out.

When the game is "published" it will no longer be in "early access". 7 Days to Die 1.0 will be the published game. Nothing we have now is "published" and you are playing it at your own discretion.

Waiting until publishing time is certainly an option and probably one you should carefully consider. Just admit that you erroneously thought the game was a finished product and you don't in your heart believe in the early access model and we can all laugh at it.

<shrug>

For the record, when the game really is published, if RWG is in this state I will be angry too. I just understand that it isn't that time yet and so there is no practical use to getting angry. Play it as is, or revert to an early version, or put it away and take a break.

Have fun making your meme.

 
How do i paint a happy little plain's biome?
Or rather, how to paint and make it work. I tried paint.net, but appears it

screw up when saving.
Click to expand...
I dont post much but wanted to share what I do. I generate a few worlds and look at the different biome and splat maps. Then I pick the best of the two, and copy the desired biome map into the folder of the world I want. Works well. Not sure how it works with water, I havent played 17.2E yet.

 
Since you don't seem to understand let me spell it out.
When the game is "published" it will no longer be in "early access". 7 Days to Die 1.0 will be the published game. Nothing we have now is "published" and you are playing it at your own discretion.

Waiting until publishing time is certainly an option and probably one you should carefully consider. Just admit that you erroneously thought the game was a finished product and you don't in your heart believe in the early access model and we can all laugh at it.

<shrug>

For the record, when the game really is published, if RWG is in this state I will be angry too. I just understand that it isn't that time yet and so there is no practical use to getting angry. Play it as is, or revert to an early version, or put it away and take a break.

Have fun making your meme.
Click to expand...
Since you don't seem to understand let me spell it out. TFP pushed an update with literally untested changes. Pushes to content delivery mechanisms is called publishing.

>Don't you dare point out onee chan is being inflammatory and condescending on my forums!!! -- OzHawkeye<

 
Last edited by a moderator:
Since you don't seem to understand let me spell it out. TFP pushed an update with literally untested changes. Pushes to content delivery mechanisms is called publishing.
You don't need to wear butthurt all over your face every time you post btw. It makes you seem even less professional, if that's somehow possible.
Click to expand...
Since you don't seem to understand, they released an "experimental" that you had to manually opt-in to, and to treat it like it's a stable build is.. interesting.

 
Since you don't seem to understand, they released an "experimental" that you had to manually opt-in to, and to treat it like it's a stable build is.. interesting.
Click to expand...
Awww, beat me to it.

 
Since you don't seem to understand, they released an "experimental" that you had to manually opt-in to, and to treat it like it's a stable build is.. interesting.
Click to expand...
I understand that just fine. What you don't understand is that even experimental changes at least get a testing pass. You don't just throw builds at user acceptance testing. It creates anarchy in the dev process and loses the confidence of the users.

You always have a QA step before you push.

 
I understand that just fine. What you don't understand is that even experimental changes at least get a testing pass. You don't just throw builds at user acceptance testing. It creates anarchy in the dev process and loses the confidence of the users.
You always have a QA step before you push.
Click to expand...
And you don't suppose that the 17.2 experimental release was to allow for greater testing of things other than RWG? I mean, clearly RWG is borked right now, zero argument there, and as someone who plays exclusively RWG, I'm still playing A16 till it all gets sorted. But an experimental release may well include components that are borked, where the goal is to stress test other systems in the meantime while the borked one gets further love.

 
I understand that just fine. What you don't understand is that even experimental changes at least get a testing pass. You don't just throw builds at user acceptance testing. It creates anarchy in the dev process and kisses the confidence of the users.
You always have a QA step before you push.
Click to expand...
Not always. Sometimes things get pushed and only have minimal testing done on it, which experimental/bleedingedge is the best place for it to go. It only upsets the confidence of those looking for a reason to be upset for whatever reason <shrug>

Play stable, if it's starting to get to you. There's nothing wrong with opting out and waiting till the next build, be it experimental or stable. :02.47-tranquillity:

 
And you don't suppose that the 17.2 experimental release was to allow for greater testing of things other than RWG? I mean, clearly RWG is borked right now, zero argument there, and as someone who plays exclusively RWG, I'm still playing A16 till it all gets sorted. But an experimental release may well include components that are borked, where the goal is to stress test other systems in the meantime while the borked one gets further love.
Click to expand...
The RWG changes did not need to be included. If they are even slightly competent, those changes would be in their own branch and it could be excluded from the main branch when it comes time to build/test/deploy.

 
Not always. Sometimes things get pushed and only have minimal testing done on it, which experimental/bleedingedge is the best place for it to go. It only upsets the confidence of those looking for a reason to be upset for whatever reason <shrug>Play stable, if it's starting to get to you. There's nothing wrong with opting out and waiting till the next build, be it experimental or stable. :02.47-tranquillity:
Click to expand...
I'm not mad. I'm laughing my ass off at this dumpster fire. I thought we were all laughing about it until Roland got defensive and then I realized this was even funnier.

 
I'm not mad. I'm laughing my ass off at this dumpster fire. I thought we were all laughing about it until Roland got defensive and then I realized this was even funnier.
Click to expand...
It's alright, I didn't say you were mad. I just suggested you might consider opting out of the experimental build.

You just keep implying there's something wrong, that experimental things, got released in a experimental build.

All I'm doing is pointing out, there's nothing wrong with it.

 
It's alright, I didn't say you were mad. I just suggested you might consider opting out of the experimental build.You just keep implying there's something wrong, that experimental things, got released in a experimental build.

All I'm doing is pointing out, there's nothing wrong with it.
Click to expand...
Well yeah there is. It's fine if it had bugs. But this wouldn't make it last QA and the conversation above clarified it never went to QA but it did get published. This is literally the "If it builds, ship it" meme in action. Not only that, is getting defended.

This is the best thing that's happened all alpha!

 
The RWG changes did not need to be included. If they are even slightly competent, those changes would be in their own branch and it could be excluded from the main branch when it comes time to build/test/deploy.
Click to expand...
As a software engineer myself I agree with this. Testers are given a release at a certain stage. After their testing issues are brought back to developers who then make another update giving that update for testers to test and cycle repeats itself. Once the major issues are fixed then the product is released to the public. In this case, when the majority of RWG worlds are unplayable it should not have been released at all. Like I said earlier, 17.0 RWG was fine. They then made changes for the 17.1 release which borked it up somewhat. Now more changes to 17.2 RWG messed things up in a major way. If they knew about this why not revert back to 17.1 or 17.0 RWG?

Some of you are saying oh this is experimental and you opted in for this thing. Yeah that's true but game companies have an obligation to have a somewhat working product before releasing anything to the public for their feedback including while in EA phase. When players have to recreate a RWG world several times just to make it playable, then there's an issue.

You cannot always say 'You're playing in experimental branch so expect bugs.' Major (gamebreaking) bugs should be found/fixed by the company before any type of release. Users sometimes find major bugs but usually they're by accident and hard to find/reproduce. In this case however, the issue occurs immediately when you create the world! Its the first you thing you see!

 
And you don't suppose that the 17.2 experimental release was to allow for greater testing of things other than RWG? I mean, clearly RWG is borked right now, zero argument there, and as someone who plays exclusively RWG, I'm still playing A16 till it all gets sorted. But an experimental release may well include components that are borked, where the goal is to stress test other systems in the meantime while the borked one gets further love.
Click to expand...
If 17.2 RWG is borked why release it (the new changes in RWG) in the first place? I understand they want to test other features but unless those other features were dependent on RWG then those changes should not have been included in 17.2 release.

 
Since you don't seem to understand let me spell it out.
When the game is "published" it will no longer be in "early access". 7 Days to Die 1.0 will be the published game. Nothing we have now is "published" and you are playing it at your own discretion.

Waiting until publishing time is certainly an option and probably one you should carefully consider. Just admit that you erroneously thought the game was a finished product and you don't in your heart believe in the early access model and we can all laugh at it.

<shrug>

For the record, when the game really is published, if RWG is in this state I will be angry too. I just understand that it isn't that time yet and so there is no practical use to getting angry. Play it as is, or revert to an early version, or put it away and take a break.

Have fun making your meme.
Click to expand...
Roland let's be practical here.

Everything you said is true, and no one is arguing that. But developers went and pushed an untested and broken change to an experimental/test release without even considering letting the testers have a look at it "because they knew it was broken".

There is nothing that can ever be said to make that sentence ok. Its not, not in any company I have ever worked for, nor any other company that Im aware of that employs an actual QA team.

There is plenty that can be said in regards to peoples opinions in changes to systems and skills and AI but for the most part those are opinions. This is an entirely different beast.

 
If 17.2 RWG is borked why release it (the new changes in RWG) in the first place? I understand they want to test other features but unless those other features were dependent on RWG then those changes should not have been included in 17.2 release.
Click to expand...
I gotta agree. They are hampering their testing by releasing a build that makes testing impossible for some. Asking people to revert to 17.1 just to make a world and then re-g®et getting 17.2 just to test is a pretty big ask.

 
All vitriol aside, the man does have a point and I have to agree too.

It's totally fine that RWG is still under work, totally fine that it has not been tested or is not even ready to be tested, so any changes should not be "Committed" to the latest version (experimental or otherwise) until they have been tested.

I think it's the fact that the changes were "Committed" before they were ready to be, that people are whining about it.

 
You must log in or register to reply here.
Back
Top