Cuts, injury..

But also, if it were wrong, how would something like that be fixed? Through code, @look_place?

Again, not a complaint really, more of me just being confused by some things I've seen.

And other thing that happens to all is that you get a cut or a bullet to the gut and your clothings remain intact, they don't tear, they don't rip, they don't get bloodstains and most importantly most chars don't change their clothing after a fight...

Or you think that a katana slits thru your gut without ripping thru your clothes? Enven when unarmed, a pull to give you a headbutt will at least wrinkle your clothes, extend that to a real to-the-death fight and you'll have clothes being ripped and torn to shreds.

(Edited by Xeethot at 4:58 pm on Dec. 5, 2004)

@look_place me is hunched over in pain.

or

@look_place me is standing tall and acting uninjured.

But it should also come through in your RP. If you a corpie, chances are your not used to pain, and will do things like faint and scream like a girl when your getting shot, while mixers would lay on the ground cripped, yet spitting on your boots and voicing loudly his opinion about your immideate family members and their associations with certian animals while blood runs out the side of his mouth.

Clothing/armor degredation and damage is duely noted.

-Kevlar

(Edited by Kevlar at 11:27 pm on Dec. 5, 2004)

I fought a rat for about 30 minutes….

It attacked, combat froze.
(I attempt to flee for ten minutes, eventually succeeding)
REPEAT...

then miraculously Combat worked.
Weirdness.

As for the original topic:

There's the @condition message that I'm sure everyone who reads the boards knows about, but hey maybe not, so here you go.

http://www.sindome.org/cgi-bin/ikonboard//topic.cgi?forum=14&topic=75

I'll fix combat.

Seriously. :)

Back to work tomorrow. :(

All the @hate code and NPC combat scripty stuff was done after I left so I'm pretty blind on the code involved.

Quick and dirty fix might be to stick a "is in combat" check very early in the relevent NPC code that primes them. (might be :is_combatant() or something like that around somewhere if memory serves.) If they're already in combat, don't attack again, that should stop the churn.

I can see that causing other possible issues though, NPC's not assisting in certain circumstances or reacting sensibly in larger fights… hard to say for definite.

Shouldn't be too difficult to add a few simple checks to smooth things over though, perhaps have NPC's queue additional targets while their current target is still here/alive/standing rather than pingponging around. When the current target goes down, check the queue and if necessary move onto the next hostile...

Blind musings though, it's like 7 years since I last touched any of it. :)

So far as I know it effects all combatants when it happens, so either the combat task isn't initiating properly or something is stalling it… but that doesn't really narrow it down much. :)

Johnny is indeed a total cunt though. :)

Hi Johnny. Any chance of a response? A hug? A hell yeah? :)