Lesbosisles
Knight at Arms
In another 8 years maybe. No guarantees though.
-
If you are reporting a bug, please head over to our Technical Support section for Bannerlord.
Beta Patch Notes e1.4.2
- Thread starter Callum
- Start date
Users who are viewing this thread
- Status
Knight at Arms
Sidhwen_Khorest
Sergeant
I read the original message too, it wasn't a message direct to that player.
Well, at least we have some real information now. I think the struggles we're seeing here is what has been going on for quite some time.
If I am reading his comments correctly, the refactor itself has been "done" for five weeks. That would mean all of this time has been a test->fix->test cycle. If they have documented 40-50 new bugs in internal testing, it is bound to be 100s when it reaches us. I don't know how you could realize 2 months into EA that a refactor of this scale is required.
One impression that I have gotten over the months of following things is that it appears that at least some of the developers are not doing a great job of testing their code before it reaches QA. This is just a hunch but I do wonder what their processes are in terms of Unit Testing and even Ad Hoc testing.
Anyway, if Mexxico says "at least" a week, we're probably looking at 2-3. Their burn rate against "40-50" bugs is roughly 8-10 per week and there are sure to be more detected over the next week. My guess is around July 31.
If I am reading his comments correctly, the refactor itself has been "done" for five weeks. That would mean all of this time has been a test->fix->test cycle. If they have documented 40-50 new bugs in internal testing, it is bound to be 100s when it reaches us. I don't know how you could realize 2 months into EA that a refactor of this scale is required.
One impression that I have gotten over the months of following things is that it appears that at least some of the developers are not doing a great job of testing their code before it reaches QA. This is just a hunch but I do wonder what their processes are in terms of Unit Testing and even Ad Hoc testing.
Anyway, if Mexxico says "at least" a week, we're probably looking at 2-3. Their burn rate against "40-50" bugs is roughly 8-10 per week and there are sure to be more detected over the next week. My guess is around July 31.
Also notice no mention of new features or content....
![[LCG]Norris](/data/avatars/m/516/516448.jpg?1580994825){kind=avatar}
there are games that come out in EA with a sufficient base that allows you to find incentives and play non-stop, not the case of Bannerlord
That´s the biggest issue, waiting for about 8 weeks for nothing, just a new update with new bugs. Then waiting like 2-3 weeks more to fix those bugs I guess. Then wait like whatever time to at least get something new that isn´t a new auto save slot or a UI change.
That´s really dissapointment.
They should change their EA description to be at least honest to new buyers.
Rostan
Recruit
What will this refactoring do exactly, from the point of view of a player? Will it improve performance in big battles? Will it create a base for improving AI? Or what?
Also, does the entire team have to work on this? Wouldn't some work on filling up content that is currently missing?
Also, does the entire team have to work on this? Wouldn't some work on filling up content that is currently missing?
Not much, it will help them to improve the game more easily, at least it should. But it´s TW, we can´t be sure if this is the last refactoring or just the beginning of another 8 years
.
We were naive to think that it was harvesting season, then.
Nalgasucia507
Squire
We were indeed my friend.
A couple of weeks ago when Devs mentioned the update was taking long because of the refactor, they explicitly said there will be no new content
Lesbosisles
Knight at Arms
Looks like these different people have an infinite vacation. Especially the ones who create scenes >_<I thought they had different people working on different parts of the game?
It was and is for TW, harvesting money.
Also the writers or voice actors
. Or maybe they´re forced working on the code too and that´s why the code is the way it is, who knows? Could be the janitor who is responsible for this mess?
9yearsago
Sergeant
- Status
