It was "BEFORE summer".Iirc, they threw the window for "summer", so it could be anywhere between July and September.
That's a pretty long wait, especially since that's hopefully going to be the real release of MtG in a playable state.
It was "BEFORE summer".Iirc, they threw the window for "summer", so it could be anywhere between July and September.
That's a pretty long wait, especially since that's hopefully going to be the real release of MtG in a playable state.
Ah, alright.It was "BEFORE summer".
Agree. They need to specifically address this with some type of time table fix. If it is going to take a long time so be it but something definitive should be stated.The frontline issues really are unfortunate. I am one of the people who actually enjoys the new features 1.6/MTG added. It'd be great if I was actually able to enjoy them. What's worse is we don't even know whether or not 1.7 is going to address the problem in any meaningful way.
Yeah, I feel the same.The frontline issues really are unfortunate. I am one of the people who actually enjoys the new features 1.6/MTG added. It'd be great if I was actually able to enjoy them.
I can only hope that this is the highest of their highest priorities right now.What's worse is we don't even know whether or not 1.7 is going to address the problem in any meaningful way.
“Nahhhhhhh man who cares about fixing our product and AI functionality at this juncture in time. We got DLC to plan for so you can throw us more money!” - paradox interactiveWelp, and there goes my slim hope of a 1.6.3.
I guess I'll just have to wait for 1.7 to actually play the game again.
I suppose that means more time for Imperator.
You recall incorrectly.Iirc, they threw the window for "summer", so it could be anywhere between July and September.
That's a pretty long wait, especially since that's hopefully going to be the real release of MtG in a playable state.
If all goes according to plan the very rough timeline is that 1.7 happens before summer at some point but 1.8 is large (together with expansion) and takes longer.
Yeah, it is just self-harming if they don't address the AI in the big patch.I agree that it sucks that the AI frontline isn't good in 1.6.2, but personally I have faith that PDX know that it's a major issue and that they will be addressing it in 1.7. I wouldn't surprise me if a non-DLC 1.7 is a reaction to this issue (+ GER stomping everyone atm).
1.7 IS NOT a DLC patch.“Nahhhhhhh man who cares about fixing our product and AI functionality at this juncture in time. We got DLC to plan for so you can throw us more money!” - paradox interactive
If they don't know how they are going to fix it, then they are not going to be able to honestly state an ETA of the fix. That is why they put it as one of their goals.Agree. They need to specifically address this with some type of time table fix. If it is going to take a long time so be it but something definitive should be stated.
Yeah, it gets annoying and I can now understand why the Devs avoid discussing issues such as these on the public forum, as they know they would just be ignored and flamed.Finally, everyone has the right to be disappointed in the current state of the game if they want. I think it's disingenuous to accuse PDX of money grabbing when they clearly stated 1.7 is a balance update (as opposed to an expansion) and that "front line stability" is on their roadmap,
Hydra = technical debt. fix one problem and two appear. HOI IV has lots of debt. Hence a release without a DLC to fix hydra.
People said the game was unplayable in 1.5 because of the carrier bug. People said the game was unplayable in 1.4 about the Yugoslav tree. In 1.3 people said the fact that spearheads were in the DLC made it unplayable without.There's a big difference between "buggy" and "virtually unplayable".
Unfortunately, the frontline issue puts HoI4 in the latter category, which is a damn shame because that wasn't the case before 1.6.
All PDX games are buggy to a degree, but that never stopped people from playing them, I don't think they'll start now with Imperator, and that was true even for HOI4 and the infamous NAV issue pre-1.6.
That's what I think of that bug as well.Yet I wouldn’t say that 1.5 was unplayable, as there were plenty of ways I could have played to minimize the impact of the bug.
You mean the AI is not core enough?It is the first version where the major broken thing is not a core game mechanic.
I remember this problem wasn't present in 1.6.0 though, it only appeared in the 1.6.1 patch or the 1.6.2 BETA. It seems fuel wasn't connected to causing this issue.Also it's not really possible to just "roll back to 1.5.4" as clearly the addition of fuel has required a lot of AI work and has fundamentally changed the AI.