Shattered Kingdoms

Propably mentioned again, but I'm bored to search and bump it, so here it is.


Obviously a tick passes by, but still it's elite how this griffon can simply walk away when he bleeds to death. Especially since the obvious thing to do as the tick passes by when one is incapitated is to die.

Fix it so that NPCs won't react at all when stunned/incapitated.

EDIT: Happy now? It looks like a lie to me now though, the numbers before and after the tick. Bah. Anything on topic?

Oh, c'mon DA. Ridiculous topic with absolutely no merit. The only thing interesting is how lately you keep using edited quotes of your ticks that include "secret" scriptz. And I don't even know you or read these forums regularly, but for some reason you whipping out your e-penor and trying to impress everyone doesn't suprise me.

You are elite indeed.

Moron.

Because if you saw what script that was, it would make a huge difference for the outcome of my post.

And if I wanted to impress anyone with my eliteness I couldn't simply post it at fave quotes or something as I've done already.

Only e-penor whipping out that you can say is happening is about the NPC that is incapidated.

Now try to stay on topic perhaps?

I think Ruud is trying to say you could have just edited out the *censor script* thingy completely. It has no relevance to the bug, and only shows how cool you are because you have a scripted item that does something and no one knows about it. We can figure out a tick passed, or you could have written *tick*.

Yeah, Tragonis hit it on the head. Thanks for editing it out, DA.

As far as keeping on-topic, what happened there was fast healing. It's been like that for as long as I can remember.

No builder is going to touch it because of all the shyte that has gone wrong in the past and can easily go wrong again. Yes, it's buggy, but you might as well just forget about it. Either that or suggest with an idea log that the "will die soon, if not aided" message be changed since whoever designed that incapacitation code obviously wasn't factoring in the effect of fast healing (unless your skill to fast heal counts as aid somehow, which makes no sense since aid usually means outside help).

Chalk it up to feature-set.

Personally, I sort of like cheating death by the skin of my teeth once in a while, as I've had this bug happen to me many times. After incapacitating you NPC's in seek-and-destroy mode that you've made aggressive (similar to bounty NPCs) will think you've been killed and return home or just sit there, giving you time for a quick escape.

But it's still triage, pure and simple. There's better bugs to be had and better building to be done, especially when looking at the potential to really **** things up by messing with ticks, fast healing, and incapacitation.

Who knows, though? Maybe by mucking around in there Dulrik will finally find a solution to the problem of ticks being so ungodly laggy on SK (probably a memory leak somewhere).

Despite my personal sentiments, I'd support getting rid of the ability to incapacitate all together.

What I see is a spawned bounty hunter who got stunned and immediately ran off to report a fake crime.

NPCs abusing the current law system, thats all.

Its in the plains, NPCs don't run off in the wilderness to report a crime.

And it isn't fast healing either, because when you are mortally wounded, your hp regen stops, and slowly goes down untill you are DEAD!! Just giving enough time for a friendly healer to rescue you in the few seconds before you go into cardiac arrest.

You saw what happened with the bountyhunter. Obviously there was HP regen that occurred. You're not supposed to regen, but the incapacitate code is buggy. Isn't that the point of posting this? lol

What you didn't see was the bountyhunters PoV. Having had this bug occur many times myself, I can say that, although it's somewhat random (sometimes the incapacitation does take effect and work as intended), there are, more often than not, times when you do regen HP and can escape.

[edit] The only reason I say fast healing is because I vaguely remember being restored when this bug happened to me a few years ago and the imm-explanation afterwards.

There is a chance for you to stabilize while incapacitated.

I guess we don't know if it's a bug or not then. Like I said, might as well look at it like a feature or change the misleading status message.

My intuition tells me that these sort of tick-based "chances" are part of the reason why we have tick-lag however. Probably not related to fast healing, I suppose, but really, that's a problem that should be dealt with already.