• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
I think you misunderstood. What is possible to do is click on merge when you have several normal armies and one mercenary army and all the normal armies are merged. It avoid deselecting Merc before merging. That's all.
Mercs still work as before.
 
  • 3
  • 1
Reactions:
Merc armies being standalone is one of the core principles of the current iteration. If they were gonna make such a massive change to it, they would talk about it more than as a passing remark at the end of an unrelated dev diary. But if it's any consolation, I saw other people on the forum make the same mistake you did, so clearly the way the change was phrased could have been clearer.
 
I believe that was a modifier you could apply that was added for modding? IDK.
 
I think you misunderstood. What is possible to do is click on merge when you have several normal armies and one mercenary army and all the normal armies are merged. It avoid deselecting Merc before merging. That's all.
Mercs still work as before.
It is more a case of terrible wording in the dev diary than a misunderstanding. This thread appearing after the patch release felt pretty much guaranteed due to that wording. With the specific mention of not being able to merge mercs with other mercs as an exception, the most logical interpretation of the dev diary would be that it would become possible to merge mercs with non mercs.
 
  • 4Like
Reactions:
I was waiting for this to be fixed in the next patch! As the person above stated - it was just badly explained. But it's a bit harsh coming from a native English speaker (me) to someone in Sweden using a 2nd language.
 
I was waiting for this to be fixed in the next patch! As the person above stated - it was just badly explained. But it's a bit harsh coming from a native English speaker (me) to someone in Sweden using a 2nd language.
I would argue that adding an exception about mercs not merging with other mercs isn't a first/second/third language issue. The main problem with the wording was the mention of the specific exception. Mentioning such a specific exception when mercs don't merge in general doesn't make sense regardless of language. I'm guessing it is more a result of dev diaries being a rather low priority, and not necessarily something the people writing dev diaries enjoys (I doubt many devs became game developers because they wanted to write marketing pieces on their work). It's therefore not surprising that they end up being rushed, and possibly not being checked by other people with knowledge of the patch content.

With the below being the only dev response to the dev diary (ignoring BjornB's forum betrayal comment), it seems very likely that the dev diary is a case of being rushed:
Hey guys! Just wanted to let you know that I've been a bit busy in the past few days with the release preparations for King of Kings, but I plan to answer questions and feedback later this week.
 
My disappointment is immeasurable and my day is ruined.
I also misread.
Same. The microing to make mercenaries work is annoying and armies keep detaching from each other so that solution doesn't really work either
 
I would argue that adding an exception about mercs not merging with other mercs isn't a first/second/third language issue. The main problem with the wording was the mention of the specific exception. Mentioning such a specific exception when mercs don't merge in general doesn't make sense regardless of language. I'm guessing it is more a result of dev diaries being a rather low priority, and not necessarily something the people writing dev diaries enjoys (I doubt many devs became game developers because they wanted to write marketing pieces on their work). It's therefore not surprising that they end up being rushed, and possibly not being checked by other people with knowledge of the patch content.

With the below being the only dev response to the dev diary (ignoring BjornB's forum betrayal comment), it seems very likely that the dev diary is a case of being rushed:
Yeah, it isn't a case of a first/second/third language issue, neither is it a DD being rushed or not checked (we tried to be very, very careful with that one, as we wanted to be very clear with all the stuff presented on it, both for the DLC and for the free QoL features; so a lot of people reviewed it, and I reworked it a lot from the first draft). It's just a case of bad wording that went unnoticed under the radar, even with multiple different people checking it.

Sorry for the inconvenience regarding it, the intended behavior was already explained perfectly by @FrogCrusher .

PS: It's true that the last DDs were not so much a priority compared with the last preparations for the release of King of Kings the update 1.36, and the post-release support of 1.36; that's why I've been more active in answering threads like this checking for post-release issues, and I still have as a pending task to go answer the last DDs.
 
They really need something like the Group Layers function in Photoshop. This way they maintain their 'identity' as Mercs vs Regular (and thus creating bloat by managing unit performance individually within an Army), but can be moved around as if they were the same entity (army) on the screen.

Returning to the Photoshop analogy:
- what we thought we could do is Merge Layers
- what we actually can do is Merge Regular units in one action even if a Merc is in the stack
- a solution could be to Group Units, so they move around as a single army, but behind the scenes, the game treats them as separate
 
Group Units
Like... an army, which is a grouping of separate regiments? :p

Nah I get what you mean, I just doubt they'd do this

My honest to god wish is that at like, dunno, tech 10 or something, merc companies would straight up disappear as like their own entities, and instead recruiting a company would just recruit a stack of mercs like we had before 1.30
which... should be possible, given that the old mercs still exist in the codebase and can be spawned in-game
 
  • 1
Reactions:
They really need something like the Group Layers function in Photoshop. This way they maintain their 'identity' as Mercs vs Regular (and thus creating bloat by managing unit performance individually within an Army), but can be moved around as if they were the same entity (army) on the screen.

Returning to the Photoshop analogy:
- what we thought we could do is Merge Layers
- what we actually can do is Merge Regular units in one action even if a Merc is in the stack
- a solution could be to Group Units, so they move around as a single army, but behind the scenes, the game treats them as separate
I'm pretty sure what you're referring to is the "attach army" mechanic - take your merc stack, click the "attach" button and choose your regular stack, attach as many merc (or split regular) stacks as you want, then click the regular stack to move somewhere and all the rest will follow it.

Aside from general movement pips reducing attrition and increasing movement speed (and I guess the consolidate regiments button, which shouldn't apply to this anyway), I'm not aware of any mechanic that cares whether your regiments are in the same army or separate armies as long as they're in the same place.