For the patches that take standart 2-4 weeks to release, that is perfectly okay, but months goes by without a single word getting out, there should be an update to that policy i think, because the lack of communication becomes a bigger problem than the potential false expectations, if it takes long, there should be semi-vague info updates that at least mentions the fields that are being worked on, words such as "experiments" can be used to avert expectations.The current approach is not to share details on upcoming patch content (that could lead to false expectations). Our broader priorities are defined within the Future Plans post.
Agreed, I was very heart broken when bannerlord failed to be a great game, all those planned features, dropped, and best excuse is, 'too complex' or 'not in our vision'. The next time tws makes a game, I'll wait before I'll buy it. (But I'm sure everyone would do the same)Let´s be honest, TW doesn´t give a **** about whatever we say in their official forum, steam community or reddit. They don´t give a **** at all.
We shouldn´t expect ANYTHING from TW even if they choose EA to "release" their game that should have been released around some months ago yet, still claiming that in their EA description.
We are paying peasants that can be happy that we´ve bought a broken EA release, remember those placeholders.
Modders did add stuff TW said isn´t possible.
Modders do care about the game, TW do care about the console release.
So remember, just for the future IF TW announces their space game we paid for (with our Bannerlord EA money) and make your decisions if you´ll ever trust this company again, I mean this small indie company...
Yes. Exactly. And to just say " we are still working on the things that we told you about months ago... so please Shhhhh and be happy" that's not good enough.For the patches that take standart 2-4 weeks to release, that is perfectly okay, but months goes by without a single word getting out, there should be an update to that policy i think, because the lack of communication becomes a bigger problem than the potential false expectations, if it takes long, there should be semi-vague info updates that at least mentions the fields that are being worked on, words such as "experiments" can be used to avert expectations.
I know what's in testing, not what will pass testingCan we inteprete this as "We don't even know ourselves what's going to be included in the next patch" then?![]()
I don't expect thatYes I'm aware you can go back to previous versions, I've gone back to v1.2 a few times just to compare. While overall I'd say the game is better, there's been some steps back, and a lack of addressing long standing issues. Problem is modders are working of their own accord. You can't expect there to be some sort of modder conference on what "version is best to mod", because nobody knows when to expect updates or what's even going to be in them.
That - to me - is more of an argument for careful communication rather than against it.It's kind of too late for "false expectations". There's always going to people here or elsewhere clamoring for "Rain/Lightning/Weather" or "Criminal Empires" or being able to "turn villages into Castles", etc.
However, not telling anything can be just as dangerous for a community/developer relationship. [...] The two options are reveal nothing, or just put out a detailed notification of what's in it, and shoot down any assumptions that can be made.
"Not telling anything" is hyperbole rather than reality. Our plans for the game are out there and at least an initial implementation for a number of the shared points has been achieved since. Not to mention that communication is not limited to the content of the next patch.For the patches that take standart 2-4 weeks to release, that is perfectly okay, but months goes by without a single word getting out, there should be an update to that policy i think, because the lack of communication becomes a bigger problem than the potential false expectations, if it takes long, there should be semi-vague info updates that at least mentions the fields that are being worked on, words such as "experiments" can be used to avert expectations.
1.7.2 will be a regular patch. It has been in the testing and fixing state for a while and we do not (usually) add further content at that stage.Of course people will expect something big when there is no update for a long time.
Can you link me the bug report? I would be happy to check in on it.and just fix the bug that stops the existing rain feature from working

No bug report sorry, but these threads give some information. https://forums.taleworlds.com/index.php?threads/showing-weather-conditions-on-campaign-ui.439209/Can you link me the bug report? I would be happy to check in on it.
Since you mention that, I would like to remember that there are still underlying issues with the game, with AI (which is often talked about) but also with character animations). Some examples:Can you link me the bug report? I would be happy to check in on it.
Does TW still plan to do something about this?Hi, i have shared both the video and the thread with the devs and this turns out to be more than just a cosmetic issue. As far as i can tell this issue is linked with animation, thus combat and game balance. So we can not really change it at the moment. We can look into the cosmetic side of the problem. If you encounter other armors that stretch like this one or even more, please share their names with us and we can add them to the list.
We will continue to tweak and improve both mission and campaign AI.with AI
Stretching textures on some character animations are considered acceptable afaik. The world map scene will see further improvements, though, if there are especially problematic cases, bug reports on them would be helpful.
Duh plz tell me Will battle mode be in 1.7.2 thanksWe will continue to tweak and improve both mission and campaign AI.
Stretching textures on some character animations are considered acceptable afaik. The world map scene will see further improvements, though, if there are especially problematic cases, bug reports on them would be helpful.
Don't worry, I love you despite the wrinkles.I am an old man now... the spark of love between Duh and I was extinguished some time ago
Then there are still some embers under the ashes...Don't worry, I love you despite the wrinkles.
You're correct, and I shouldn't have said "Not telling anything". That is incorrect, as there has been larger communication about the general things being added into the game. I guess that I should elaborate on what I more meant by that. We know the general plans for the game, but that's it. The community doesn't know what's going to be in a patch, it doesn't know when a patch might come, it doesn't know if anything may have been cut."Not telling anything" is hyperbole rather than reality. Our plans for the game are out there and at least an initial implementation for a number of the shared points has been achieved since. Not to mention that communication is not limited to the content of the next patch.
For the second grievance, no, you'll never end that you. But it would end the first one. If there is a massive issue that is holding back the patch, letting the community know will at least make people understand that things are taking a while for good reason. If there's a massive issue, I think most sane people will understand that the patch is taking longer.However, I also personally don't think that it would resolve frustrations with "it's taking too long" and "it doesn't have the thing I care about".
I'd agree with this when patches were coming in 2-4 weeks, like said earlier, however months with relative silence doesn't bode well.You can see that in most patch topics - and they are better than a status update since they don't just hold information but come with a playable version.
That is inevitable, but its a lot better then people just thinking the game is dead, and spreading the idea that the game is dead. Silence is just going to sever the already loose ties that connect the developer and community. And, if communicated well enough, people who moan about their own expectations being wrong will be seen as, well, people who hyped up their own expectations, not people who have a genuine problem with the product.Similarly, even the most careful wording will naturally lead to some expectation.
i think the frustration comes from, first the future plans post was amazing to hear new things worked on. We got nothing new in many many months. Just stating what is being tested and maybe not able to be put into patch because of issues, isn't an excuse to not mention it. Just because its being tested doesn't mean we would expect it in the patch. Bad things happen. So what I have said and people are talking about is the once a week, very vague answers to people wondering what is going on. I asked this awhile ago, why is it difficult for maybe once a week for someone to say we are working on this, this and this and its currently in testing or final testing and we "think" it could be next week. the future plans post is so out of date and the best communication we get is a developers video that shows things already implemented we don't care about. I personally hate hearing the excuse "Just mentioning it and people will expect it", It's early access, anything can happen and we get it. Many other developers offer massive information. Why not make a thread where no one can respond and make it a dev blog or whatever where you can once a week just give a quick update on the next patch, content, how far its into testing, you can even put at the top in all RED, "nothing it testing is guaranteed to be in the next patch" I just don't understand the virtual silence we get. Here is my attempt at the once a week post. "We are still in testing and running into a few major issues delaying it, Content A,B and C are looking good but content D and E are causing issues so we appear to be at least 1-2 weeks out." Those 2 lines tell us everything we need to know about the patch from content to issues to new features with no expectations. So my question is why are the 2 lines of communication being done once a week in a thread, that difficult. We don't need the entire time line, just an update on how's it going and what we "MIGHT" be getting. At least try, people are mad, upset and frustrated and unless you try, how do you know if it might be better. Just tell people its NOT guaranteed and don't expect anything, these are all estimations and hoping to be implemented. I am being serious in asking and with best intentions, is that 2 lines of communication once a week, that difficult to just try and see how well it works.........other developers do it multiple times a week, why is TW unable to do it as well? Why alienate your fan base when something so simple would satisfy many, not all that's impossible, but many would be.I know what's in testing, not what will pass testing
I don't expect thatHowever, I also don't think that the update schedule will be geared towards your modding setup. The first and foremost responsibility is to deliver the base product that everyone uses. So the best bet for players that wish to play with mods is to use them with a "stable" version that receives no more updates.
That - to me - is more of an argument for careful communication rather than against it.
"Not telling anything" is hyperbole rather than reality. Our plans for the game are out there and at least an initial implementation for a number of the shared points has been achieved since. Not to mention that communication is not limited to the content of the next patch.
Nonetheless, I agree that there could be more detailed status reports. However, I also personally don't think that it would resolve frustrations with "it's taking too long" and "it doesn't have the thing I care about". You can see that in most patch topics - and they are better than a status update since they don't just hold information but come with a playable version. Similarly, even the most careful wording will naturally lead to some expectation.
1.7.2 will be a regular patch. It has been in the testing and fixing state for a while and we do not (usually) add further content at that stage.
Can you link me the bug report? I would be happy to check in on it.

I know what's in testing, not what will pass testing
I don't expect thatHowever, I also don't think that the update schedule will be geared towards your modding setup. The first and foremost responsibility is to deliver the base product that everyone uses. So the best bet for players that wish to play with mods is to use them with a "stable" version that receives no more updates.
That - to me - is more of an argument for careful communication rather than against it.
"Not telling anything" is hyperbole rather than reality. Our plans for the game are out there and at least an initial implementation for a number of the shared points has been achieved since. Not to mention that communication is not limited to the content of the next patch.
Nonetheless, I agree that there could be more detailed status reports. However, I also personally don't think that it would resolve frustrations with "it's taking too long" and "it doesn't have the thing I care about". You can see that in most patch topics - and they are better than a status update since they don't just hold information but come with a playable version. Similarly, even the most careful wording will naturally lead to some expectation.
1.7.2 will be a regular patch. It has been in the testing and fixing state for a while and we do not (usually) add further content at that stage.
Can you link me the bug report? I would be happy to check in on it.
?I've suspected for a while that many of the Devs have been moved onto a new project (which is usually detrimental to the initial one) given the glacial progress and now I'm convinced it's a smaller group working to finish Bannerlord.