BattleMaster Community
BattleMaster => Helpline => Topic started by: BarticaBoat on February 11, 2018, 08:06:33 PM
-
Bought a region to resolve at the turn, got the successful message, but the enemy appointed a lord before the change (I assume) and the region did not flip. Shouldn't it still have flipped as I had put in the command earlier?
-
Nope, if you want to be sure of getting it to go off, you need to buy it now.
Buying at the turn is for if you want some plausible deniability, but it has extra risks.
-
Can the UI be updated to explain all of these "extra risks"? Obviously some of them were not obvious, and should be spelled out in detail.
-
I'm rather confident that there is text explaining that it's riskier.
EDIT: Reviewed the in-game text and the risks warning could be more explicit. Please submit a bug report for a text change.
-
When I attempted it on a different continent, I think I remember the description you get was informative enough that if time was against you, you should buy the region now. In this recent situation, I would have to agree that you should have bought the region now and not the other option. I forget exactly how the description was worded but I understood it enough to come to that conclusion. If it's not clear enough to others then maybe it should be changed. Can someone post the actual words of the action here to examine?
-
I'm rather confident that there is text explaining that it's riskier.
EDIT: Reviewed the in-game text and the risks warning could be more explicit. Please submit a bug report for a text change.
My issue is I assumed once I put it in I had it, and that by using the stealth option I was decreasing the risk of local troops stopping me. I feel I should get the 50% back that you get for command failure.
-
We don't generally give back money that was lost for an actual bug, let alone a text that could use clarification.
-
We don't generally give back money that was lost for an actual bug, let alone a text that could use clarification.
What I feel and what's going to happen are different things :'( let me cry over this lol
-
I'm rather confident that there is text explaining that it's riskier.
EDIT: Reviewed the in-game text and the risks warning could be more explicit. Please submit a bug report for a text change.
Thank you. Filed tracking bug: http://bugs.battlemaster.org/view.php?id=9216
-
Well, I'm not sure y'all are talking about Evora, but the place just revolted to Redhaven while we had vast control and I was appointed Lord.
Think this is a bug.
-
This war has gotten so cheesy, where the actions of a few with gimmicky mechanics completely null out the actions of the many. What used to be rare mechanics that would add some diversity to warfare now seems to have taken the biggest role, leaving rank-and-file nobles more irrelevant than ever.
-
If you're referencing the frontline martyr tactic, its... Ridiculous. I mean, where in the hell would an entire army fire at a single noble's unit and ignore a battlefield full of warriors? It just doesn't make the slightest sense.
This tactic has done a great job revealing a tactical/technical fallacy in the combat code that must be rectified as soon as possible.
-
Perhaps he's referencing the swarm of scrolls that start to get used or using cheap priest actions in an offensive fashion.
-
If you're referencing the frontline martyr tactic, its... Ridiculous. I mean, where in the hell would an entire army fire at a single noble's unit and ignore a battlefield full of warriors? It just doesn't make the slightest sense.
This tactic has done a great job revealing a tactical/technical fallacy in the combat code that must be rectified as soon as possible.
I wasn't, if you are talking to me, but I also deeply despise that. Not sure what the best fix for that would be though.
-
I mean, where in the hell would an entire army fire at a single noble's unit and ignore a battlefield full of warriors? It just doesn't make the slightest sense.
This tactic has done a great job revealing a tactical/technical fallacy in the combat code that must be rectified as soon as possible.
Just hate it... pure nonsense and people are exploiting it all the time in every continent. Bug or not, code error or not... it's revolting.
-
If marshals could set line settings for the whole army (or if line settings was solely left up to marshals), then this kind of thing would become less common, imo, as the simplicity of making sure everyone's doing the right thing would start to outweigh the gain of the advantage of meat shield units.
-
Or... you know... you don't set all the archers to fire a single unit. But I think this is code and we are all back to "we need people".
-
Or... you know... you don't set all the archers to fire a single unit. But I think this is code and we are all back to "we need people".
Archers fire at whatever is the closest line unless said line is in melee, then they fire at anything behind the melee. It isn't a setting.
-
Yeah... Just... We need to work on the archer code.
I can't in any reasonable way see even a dozen archers being stupid and dense enough to fire on the single closest guy while ignoring the giant mass of units behind him, much less a hundred to a thousand archers unloading on the front-guy heroically leading the charge while completely ignoring the entire god damn army a few steps behind him.
Its just... Wow. Even dungeon-crawler/MUD/JRPG AI isn't that stupid, and I've played a lot of those :P
If a unit reaches overkill, the others should aim elsewhere. I mean, how many dozens or hundreds of arrows pierce the same guy before you go "Hmm, maybe I should aim elsewhere."
Though that opens up a whole other bag of worms because apparently our archers have perfect godlike aim and never hit anyone other than their exact target, which is honestly something I'd like to see changed. Maybe asking too much in that case, however.
-
The fact that they have an entire line of archers with a range of 3 or 4 lines and they're shooting at the lonely meat target makes no sense. People are just exploiting it.
-
...Because 1,000 archers loosing a massive volley of arrows will *totally* land within a perfect 3-by-3 box and miss everyone else in the army, and no one else will have maybe tried aiming for the huge ocean of warm bodies a few paces behind them, because logic
-
Just goes to show that players have found a way to manipulate an obvious flaw in the combat mechanics which the coders never planned for.
Happens. A LOT. In game development. Or, honestly, any kind of engineering really.
Someone, somewhere, will find some completely insane or ridiculous way to obsolete an entire system by uncovering an unexpected oversight.
Then, you fix/patch/redesign and become more robust than ever. :)