Gilden is one of the best factions in the hands of the AI. I don't know how great they are for players since I only play as custom factions, but they're always in the top 2 in the games I play (and I run 10 AI opponents). Them and the Ythril, or whatever they're called. The gray guys. I've never seen Tarth near the top, though.
That might still be a bug, though. The normal healing rate is 1/level. Scarred's description overrides the per level recovery, but perhaps an enchantment should override that? Either that, or they need to change the description as you suggest.
12. When you run out of mana, it cancels all of your enchantments. Not just the ones that have a mana maintenance, but all of the city enchantments, too. It shouldn't cancel those. It should only cancel enchantments with a mana maintenance, which are unit enchantments.
So there are people who like the XP split, and some that don't. I think that, while this is still a debatable topic, Stardock should focus on other areas where we can all agree the game needs changes, like bug fixes. They can revisit the XP split at a later time when the less debatable aspects have been taken care of.
Maybe he's editing his post since you guys read it, but it doesn't sound that inflammatory to me. He just lists 4 problems that annoy him more than the other problems with the game (although 4 might not be valid). 1. I've seen this since I started playing FE in January. How to reproduce? Get your army 1 tile away from a monster's lair, and then click to move to that lair, so you use your last point of movement moving right next to it.
If you're playing an Empire faction, you can build a lot of cities. As you get more cities, it becomes more important to start them building them Workshop chain, as Slave Pens will nullify the Unrest penalty for Production (thereby circumventing part of the city count Unrest penalty). Also, with Death Magic, you can have Oppression on the city until they complete the Slave Pens. Once you have Slave Pens built, you don't need to reduce Unrest until you want that city
In D&D you don't have troops.
I need to update my formula, though. It doesn't work with only 1 champion being in the army (it would give a 50% bonus). The basic idea is still valid, though.
Combat champions still don't seem worth while to me. I'd only want to have the champions together in the early game when I'm short on units. That said, I don't like to see dramatic balance changes. Rather than remove the split entirely, why not make it less of a split? Still reducing the XP gains, by not by such a large amount. X = base eXperince points C = number of Champions (including the soverign) G =
I've seen the same issue, but I've never figured out how to report it. I guess this is good enough. It happens too often to be bad luck.
[quote who="kaosbain" reply="23" id="3351963"]Quoting Alstein, reply 22 I still don't know why they lack increased upkeep costs. Is there some sort of hardcoded issue that keeps the team from trying this? I thought upkeep cost were set by labor costs? That means the increased labor costs of mounted troops inherently have higher upkeep costs? I could be wrong but I thought that's how upkeep was calculated.[/quote] I don't know if it's tied to t
I've seen this as well. The way initiative is calculated is messed up. Often times one of my units with high initiative will go twice in a row, even though there are 7+ units on the field. It should be fairly evenly spaced out. The way it should work is that every unit in the battle should have a temporary turn order value (I'll call it TOV for lack of a better name). Each turn, every unit's TOV increases by its initiative. The unit with the
[quote who="bigduncm24" reply="2" id="3351785"]Change the thread title to Minor Bug Omnibus?[/quote] Good idea. And done.
I've got more to add, but I wrote them down in prior versions and need to confirm they are still occurring, and they are rather rare.
I'm currently in the process of updating this list to 1.3b. Anything with [] before the number has not been checked yet in 1.3b. I removed issues I confirmed to be fixed. Here's a bunch of minor bugs that I didn't feel were worth each getting their own thread. I'll probably add more minor bugs to this thread. Feel free to contribute. I can add to the list
In no case is it better to spend 4 turns going around a river than spending 2 turns to cross it and reach the same tile (which is the situation in the screenshot).
I do like the new feature where bringing up your spellbook automatically selects the last spell you cast, however it does have one problem: You can't scroll up. Not right away, anyway. If I try to use the mouse wheel to scroll up the spell list, nothing happens. Instead, I have to scroll down first, then I can scroll up. While this is a minor bug and there is an easy workaround, I find it to be far more annoying than I probably
It is a bug. I've seen it before. For some reason, the system will sometimes refuse to path across a river, instead going completely around it, even though it may take many more turns to do so. This problem has been around since before I started playing in January. It's not a frequent problem (although that might be more because I've learned to not use auto-pathing because it keeps getting me killed
If you can load the autosave before the crash, and reproduce the crash after loading it, then it would be helpful to submit that autosave for review. Without it, there's not much the devs can do.
Sounds like a bug to me. Stun should interrupt casting.
I had a problem with the beast collar disappearing before, although it was different. It was also in pre-LH days, but it might still be relevant. I had two beast collars on my sovereign. I used one of them and successfully tamed a beast. While I only used one, both of them disappeared from inventory. I didn't notice until I went to fight another beast (fortunately I noticed it before going into combat). It was too hard to try to reproduce, an
Previously this bug was thought to be caused by the system accidentally dumping extra units into the map, but from the screenshots, it doesn't look like that's the case here.
Why is there even still an Explore button? Nobody hits it on purpose (but if they do, they quickly learn it was a bad idea). While they could devote man hours to fixing the bug or highlighting the button when it's on, I think the best thing is just to remove the feature altogether.
While loading auto-saves has quite a few problems, such as automatically moving units on load, I'm just going to report this one particular issue for now. This issue has been reported before, but perhaps not with steps to reproduce. Also, it's still a problem in 0.85, so still worth mentioning. 1. Set auto-save to save every 1 turns (otherwise this will be annoying to reproduce since you'll have to match up the turns). 2. Start training any unit in any
This bug is easy to reproduce. 1. Attack something with an army with multiple units (meaning your army has multiple units), or a champion that can summon units. 2. Let some of your units die in combat -or- summon some units during combat (Skeleton Horde works great for this). 3. After combat, but in the same season, cast Call of Titans. It may have to target a champion, as both times I've been in this situation, that's what I was doing, but it might still