If people can wait 8 years for the game to be on early access, I'm sure 1 more year of fixes, adjustments, and improvements is no cause for concern. And I'm fairly certain a mere 'out-of-place decimal point' is nothing to sneeze at.
The whole point is that the game won't get anywhere if it takes Taleworlds that long just to fix a decimal point issue, much less anything more complex.
I can't even play right now because
one of the more recent patches introduced a new bug that makes Bannerlord unable to handle anything but default My Documents location (they probably are looking up the wrong registry key). Something that have been working until then without any problem. I've provided all the extensive information I could gather on my own without doing detailed code analysist with dnSpy (and it's not really a tool I can comfortably use to do code inspection of something that low-level), and can't even get a "ok, we'll check this" in the tech support thread from them. Since early Monday morning.
But they are busy inspecting save game files from people who had OneDrive override the MyDocuments default location, and get the same problem as I do right now instead. A problem which, in all likelihood considering it hasn't been reported before my issue occurred as well, is probably caused by the very same change in how user files location lookup was changed in the more recent patches.
Instead of checking whatever changes were done to the save system, in particular determining user files save location. FFS, simply reverting to 1.3.1 version of Bannerlord fixes the problem (at least for me - and I strongly suspect might also do so for OneDrive-issue affected people, but I'm not TW's QA lead so can't get anybody to verify it that easily), the problem did not exist until either 05/22 or 05/29 hotfix (I got both of them at once after not-playing for a week, but looking at other people's reports of issues it's most likely 05/22 hotfix that borked things up). That should be all the information required for competent programmers to zero-in on the problem, and I fail to see what "save game" files have to do with any of this, since the game crashes precisely because it can't correctly access the location of save files in the first place.
tl;dr: If a simple decimal point that causes a major and immediately noticeable issue (combat-related, to boot, so basically the core gameplay subsystem) doesn't get corrected in two weeks, good luck getting the game in any kind of decent state before the declared EA period is up, even in its current barebones state, much less something more elaborate.
