It slows 7%. 

 

And I didnt consider the other snares for the topic, because they are conditional effects, where as Maim is an actually, always present snare, like the auras. 

 

Side topic tip, when you pursue a reg, always hug a side of the road.  They usually throw their mines in the middle hoping to get atleast 2 hits.  If you go along the sides, you can usually slip past all their mines.  And another tip, don't cast through Mark.  Obviously, its what they want you to do so they can get away, or worse, hunt you down.  If you ever cast through mark while at even or less health than the Reg, you deserve to die. (Unless its a situation where your saving or helping a teamate get a kill)

Oh how offensive I guess an Ass is not much worse than a mule!

 

In simple terms -

 

If the Fire AA is "fixed" then Ice/Hybrid builds will be virtually unfeasible (self-defeating), unless compensations are made to Ice TB. Fixing this "bug" would make TB nothing more than yet another DPS Demigod.

 

Even with this "bug" TB is not significantly disadvantaged, this "bug" makes TB more balanced, this "bug" is unrelated to any balance issues with Regulus.

I don't understand this at all, being able to autoattack in fire mode would be a BUFF to a hybrid build since a hybrid build by definition needs to use fire form. 

You're assuming that you would never, ever go from frost to fire, always fire to frost when giving chase.  You also don't explain what exactly you think the point of the fire aura is given that it gives a run speed and attack speed increase.  Instead you insist that people get permafrost instead, you're the one who's arguing against the entire skillset being useful.

You're just begging the question when you make this kind of claim.  There's no explanation of what would be so unfair about a TB who had the basic functionality which all other DGs (including himself in frost mode) have.

#ANIM_START_MOVING = { Duration = 0.2,TargetState = 'AttackRangedMoving', CopyClocks = true, },

The equivalent entry for the frost build doesn't have the final line hashed out (hash isnt comment iirc in lua...it's probably just denoting it's not implemented).

The attackrangedmoving anim state isn't defined either, though you could add it quite easily.

Ice build has an "AttackRangedMove" anim state.

Speed buffs are useful for more than just chasing people down, I'm not sure this isn't intended behavior.

Thnx for that info woppin...Amazing stuff.

 

Please keep bumping this thread I wand and offical response on this issue before the game hits six months

 

I wouldn't mind a reason on why it hasn't been fixed if it actually is a bug...

Let's see:

• Movement cancelled when activating items bug
• Valor flag bug
• Durations not reset on second cast before the first has expired
• Various auto-atack bugs
• Sedna Healing Wind + Priests bug
• Some item combination bugs
• Picking up dropped items with no slots left
• Poisoned blood granting self kills (and probably allied kills)
• ... (a number of others)

some reported months ago and requiring very little time to fix.  Still not fixed.

With animation missing for TB Fire auto-attack while moving, as I said - don't hold your breath for a fix...

Way Frogballs speaks It might break the bank to make a TB Auto Attack animation while moving...

You guys should quit crying about your precious 'bugs' and just enjoy the game.

Oh for the days before the Interwebs when there were no patches, updates, DLC, or crazy forum whiners and we just sat back and spent all day blasting tie fighters or mapping out dungeons on a piece of grid paper.

You know, come to think of it....Tie Fighter was a pretty bug free game.  *sigh*  Thanks for dredging up those golden memories, I'm going to be depressed all day now.

If only Tie Fighter could run on Windows XP....

 

I wouldn't recommend it, every classic game you drag up from childhood seems somewhat less spectacular when you play it again

I've gotten it to run, but the problem is it runs based on your processor speed, so it goes insanely unplayably fast, like most DOS games from that era do.

Another thing I really want to play is Magic the Gathering: Shandalar.  I even still have my CD, but it runs crazy fast and randomly crashes on XP even in compatibility mode.  *sigh*

I don't think it needs an explicit animation, just translation forward while playing the stationary fire attack one. I tried to hack it in quickly without success by copying most of the stuff from the ice rangedattackmove state. I might try again tomorrow. There's magic numbers in there that I think are the times it actually takes to attack, but I'm not sure why ice is at 0.8 and fire at 1.5.

EDIT: DOSbox IV, you must embrace it with open arms.

I hope this gets fixed in 1.2 or sooner. I'm tired of not being able to attack in fire mode.

Not to get off topic but most of those classics "bug free" games weren't bug free at all. But because they were before the internet, people couldn't group together and crack games or share their exploits they found. Also I'm pretty sure fewer people tried to break games back then and just wanted to play them as they were.

Precisely! And that's what I miss.

I love getting broken games I can't get patches for too.

 

I don't think theres anything wrong with game companys having proper quality assurance. It's demanded by the customers these days because people only want to pay for somthing they feel is a finished product. I don't see you going out to buy big rigs, which was probably an equal state demigod was in at launch in terms of functionality.

My point is this:

Back before the Internet (as it is used today), we picked up games based on what we heard our friends say about them or based on what they said on the back of the box. We took it home and played it as is. We were blissfully unaware of any 'bugs' and just played the game because we wanted to have some fun. There were no epeens to stroke, no stats to worry about.

If we DID recognize a bug we found a way to play around it (if we really enjoyed the game).

By the way, I'm talking about stuff that would be similar to this TorchBearer Fire auto attack 'bug'. This type of thing is not game breaking and could even be intentional programming; not a bug at all.

For example, in the original Bard's Tale (Commodore 64), we didn't go to school the next day and tell our friends 'Hey geez, I wish they had made that wizard in the Cellar not so overpowered. He's too tough.' Instead, we said stuff like 'Hey, that wizard in the Cellar is a tough bastard but I'll get him down somehow.'

I realize today that games are vastly more complex and there are many things to consider and account for, including the Internet itself. And it is much better to be able to update games and such. It's just when people have these petty greivances about TB's auto-attack, or Valor Flags, or some demigod being OP, or whatever, they should just get over it. Quit wasting so much time complaining about it and play the game. Enjoy it! If the devs happen to fix your pet 'bug' then rejoice, until then, find a way around it or play something else.

Back before the internet, multiplayer games consisted of playing second player in Mario Brothers.  Games were mostly bug free, or at least they didn't significantly impact gameplay.

In a multiplayer game bugs are usually far more impactful if you're trying to have a fair game.  And especially if they give someone an advantage.

It's very difficult to enjoy the game you're playing when you lose thanks to a bug or an exploit.  When your valor flag bugs out and their giants beat yours because your creep stats are bugged it's extremely frustrating - not fun.  When you cast a spell but your hero just stands there looking stupid because of a bug, it's not fun.

"Just play the [bugged] game" might have worked years ago, but that was because you were just playing by yourself.

Not really, since BOTH teams would be affected by them. For instance, there is no bug that only affects the Forces of Light.

It still works today, even in multiplayer games. I'm having a blast no matter what Demigod I play, win or lose.

If people didn't post this kind of stuff the devs wouldn't fix it. If there was no community built up around a game there would be no incentive to work on patches for it. If one character was blatantly better than all the others the game would be fair, for some definition of the word, but it certainly wouldnt be very good, whining about balance problems is important for exactly this reason.

Oddly enough, I experienced a bug yesterday where Ice TB refused to auto-attack at all, no matter what I did. I posted a bug report on it in the Demigod Problems forum, but it was just such a weird bug.

After the match, I went and tried TB in a single-player skirmish and TB worked just normally. I don't know what it was all about.

Oh yeah guys, Daggerfall was a CLASSIC. 

Gimme a break, what you're realling pining for is is the cessation of competitive gaming, which is the only type which requires continual balancing, and you'er also glossing over the fact that even though chain lightning crashed MoM consistently I was able to save before every battle I started.

The old games that had unplayable bugs, like Daggerfall, were a waste of time and the ones that had minor bugs could be worked around by saving constantly, and then the ones that had glaring imbalances were single player anyway.

Also get Dosbox and your older stuff will work fine.

Then stop complaining because you'll have fun no matter how many changes we ask for are or are not implemented.  It's no skin off your back either way so what's with all the whining about whining?  Just feel like having a good rant?

Stop whining about my whining about your whining.

There are bugs that affect certain Demigods, and certain bugs that affect certain Demigods more than others.

Do you actually realize it's what you're doing?

Let's just focus on the merits of being able or unable to attack while in fire mode and lay off the absurd notion that people shouldn't talk about things they'd like to see change on the forums.