Thread: Bugs Thread
View Single Post
  #7  
Old 11-29-2012, 05:06 PM
ckdamascus ckdamascus is offline
Approved Member
 
Join Date: Mar 2010
Posts: 1,059
Default

Quote:
Originally Posted by Rork View Post
Actually I think it's the best way to stop them (or any other units with pesky ranged magical abilites), because they just become regular units, but that's not important .
For 35 mana that 'might' or might not work if the stack is weak enough? Considering you can double cast... so many cheaper/stronger methods.

If you trap them, they get stuck in your side of the field, all alone. You can take them out really fast in the first round then.

If they are too strong to finish in one round, you can use phantom or a summoner unit as a decoy so they burn their backstabs on it. You still need to worry about murder but that isn't a big deal.

Trap and Phantom (level 2) can be cast for <= 20 mana so you can still double cast. Most mages will have trap maxed out by then, so you can have your interdictor (usually black dragon or archdemon) stand in front of the pre-dropped traps to bait the assassins to backstab over and fail. (assuming that is out of range of their melee/range)

AND you still get free spells to cast for less mana.

Shackles you can precast one spell then it might work on some or other units as you've seen. Not to mention it costs a LOT of crystals to get.

Quote:
Originally Posted by Rork View Post
Let me make it as clear as possible (too bad I have no screenshot for this).
I did not move my units, just kept them on the starting hexes, so no back was facing at any moment. The actual backstab came from the right front hex of the unmoved unit. Also, the battle went on like this: 1st turn, my army waited, spells and rage rained down, assassins moved; 2nd turn, my army waited, used some more spells and rage, assassins used backstab on the center unmoved unit.
At no point did the assassins used murder, as they were in no contact with any of my units and certainly no kill was involved. Trust me, I do know the assassins quite well .

Double fights like this are shit (obviously a bug not present in the other games), something like a cheat.
Ok that sounds like a bug then. There really is no point in discussing old bugs though. You are using an old version of the game which has already been patched. Also, incorrect about not existing before. This bug existed in Armored Princess (double fight), but far more rare.

Quote:
Originally Posted by Rork View Post
Whatever fixes I can do via file editing or console are more useful than any patch, at least for now, so I'm only playing offline. I would've stopped playing had not I advanced so much in the game, but since patching renders previous saves useless, I decided to try to finish like this. Not a Steam fan, I only use Steam when there's no way around it.
Incorrect. Patch does not render previous saves useless. Of course, you should back up the game just in case (I have).

What happens is if the new patch fixes an old Quest bug, continuing your existing game will not HAVE that quest bug fixed despite being in the new patch because your save was generated in the old one. I know why but ugh it's annoying (because they patch it by using quest item generation and new games generate items).

I can complete the game with my "initial saved game build 6246" with current build 6249. But again, you will find some new bugs which may or may not alarm you, but it will fix other bugs.

Quote:
Originally Posted by Rork View Post
Finally moved past Loki, but I'm not sure if I did what you said, since Enter apparently didn't work (there was a new title involved and then the achievement). I ended up moving mouse pointer on the OK button and pressing Enter repeatedly (yes, I know, not exactly a dignified sight). What I did change in the fight was to move my units on the up and down lateral rows (where Loki's firebreath doesn't reach) and kept them there, except the damage-dealing Dragons, for the duration of the fight. That meant the hexes affected by the the fire didn't activate - maybe it also helped. Anyway, five Death Stars later it was solved with minimal losses. Still, game-breaking bug there, so good luck circumventing it.

Another, well, not bug, but definitely a mistake: Dragon Slayer's Sword doesn't mention in its description that it's part of the Dragon Hunter Set.
Loki's fire breath is terribly bugged in 6246. Works fine in 6249 as far as I can tell both when I use the Breath Weapon (when I learn it after beating him) and during boss fights.

However, it seems they kept the old "crash after" battle one.

Yeah, Dragon slayer sword set is fixed in 6249 as well.
Reply With Quote