But you said that you loved me. </3
Just play some MP until the next beta ? ? ? ? ?
Damn bro, I though the beta branches were used precisely for testing purposes. We have apparently entered now a new era where we can't even expect the beta branches to arrive at the same time than the previous version stable patch. Crazy times here in Taleworlds land.
So you would prefer to see:
a) The current Beta patch not being moved to live if the next Beta patch isn't ready.
b) The next Beta patch being released to the players even if hasn't undergone the necessary internal tests and had critical issues fixed.
Noted.
Oh here we go again....
1 Adding the stabilized Beta to the stable branch allows/encourages modders to update their mods. Many just plain don't bother with the beta.
2 Some game venues don't offer the beta, so the stable update is very important to those players.
3 If the beta crashes TOO MUCH there's nothing to beta teas. There's no value in 1k+ "Game won't start" or "I pressed a button and it crashed" reports.
4 Some players have specifically asked for this in the past and it's not even the first time the stable got updated but the new beta was delayed. It's good and makes sense.
I expect a new patch to be the biggest one, more than 2 month without new patch.
I admit, the fact the blocker issues persisted makes me hopeful these are significant changes or new systems somewhere. I wouldn't expect so much trouble if it were just tinkeroos and new shoulder pads.
When will you figure out that we are needy children who happen to be in their 30's?
:stomps little frog feet:
New Beta!
New Beta!
New Beta!
New Beta!
New bug. Party in your army don't buy food when in city or village and you end up feeding your entire army
"
New bug" Hah hah hah hah ? They eat all your food. Deal with it.
There is a reason the beta branch is called a beta, and a reason why it's an opt-in update. It's meant to be unstable, players are better at finding bugs and in much higher numbers than your testers. The whole reason you release beta updates is to let the community find issues.
Bugs yes, known or invasive crashes NO.
Look at how many problems the beta often has: If tw thinks it's too crashy to put out, IT IS.
More than ever the multiplayer needs players to test the ranked system. Taleworlds is not even mentioning the fact that 1.7.2 brings lot of changes to the multiplayer in their last video tweet...
So I can hear gamer words and get vote kicked?
MP NEVER! ?
MP NEVER! ?
If u aren’t capable of thinking by your self i will explain more directly.
The problems they are referring to in the beta are probably game breaking/causing crashes, how are u supposed to test something it if crash constantly or work so bad that the only thing people would report is what they already know is bronen…
Agreed
As for our beta release approach - we have our internal processes and guidelines. While the beta is less stable, it is still meant to pass certain criteria. So we won't release it with known (frequent) crashes or other significantly game breaking issues.
And I thank you for this! Getting a bunch of people to download a patch ,get 10 crashes and re-vert to stable, is a lose/lose situation.
Your point about splitting the playerbase is valid. But bugs that cause the fps to drop to 10 or lag spikes in general are some pretty major oversights in your testing phase of development, especially since it's known you take a lot of time to roll out patches for anything.
If you're going to enable a beta with no servers to test it on, at least be able to deliver in a stable way considering you have more time to test it on the branch.
This is concerning, I haven't started a new game yet to see though. I don't mean this to be condescending but I hope people are re-optimizing their settings after the update, it often requires this to run well IMO.