View Issue Details

IDProjectCategoryView StatusLast Update
0001928The Dark ModAIpublic30.03.2013 01:09
ReporterSpringheel Assigned ToSpringheel  
PrioritynormalSeveritynormalReproducibilityhave not tried
Status closedResolutionfixed 
Summary0001928: Sleepers can become alert while asleep
DescriptionIt appears as though sleepers are becoming alerted by noises around them even while still asleep. This means they switch to their alert KO cone and cannot be killed by a single arrow to the head. Since the player has no way of knowing this, we probably want to fix this so that AI that are asleep do not do those things.
TagsNo tags attached.

Relationships

related to 0001718 closedangua Problems with BJing sleeping AI 
related to 0001719 resolvedangua Problem when AI sees player while lying down 
related to 0003053 feedback AI should be able to alert sleeping AIs 

Activities

grayman

grayman

28.03.2013 01:48

viewer   ~0005252

Last edited: 28.03.2013 01:48

A sleeper's audio acuity is cut in half.

So a sleeper can still hear nearby sounds. These will raise the sleeper's alert level, though slowly. The sleeper is allowed to be at the Relaxed and Observant levels w/o waking up. When he rises to the Suspicious level (alert level >= 6.0), he wakes up.

The lowest level where an AI can be immune to KOs is AgitatedSearching. The narrower KO cones when in higher alert levels are used at this level or Combat. The sleeping AI is wide awake at these levels.

The narrower KO cones are also used at lower alert levels, but only if the AI is hit in the back of the head, which won't happen when they're sleeping.

So I'm not seeing how the KO cones come into play to make it harder to KO a sleeping AI whose alert level has begun to rise.

---------------------------------------

Rather than using a rising alert level to wake up an AI who's hearing things, we could leave the alert level untouched, and have him wake up if he hears a sound that's loud enough to do so. A simple threshold.

Springheel

Springheel

28.03.2013 21:40

administrator   ~0005257

This is a really old bug that may not even be accurate anymore, although I have no problem with your suggested change.
grayman

grayman

29.03.2013 00:34

viewer   ~0005261

If things are okay the way they are, I'll skip making unneeded changes.

Can I close this?
Springheel

Springheel

30.03.2013 01:09

administrator   ~0005266

I think it's safe to close it.

Issue History

Date Modified Username Field Change
25.08.2009 23:41 Springheel New Issue
12.03.2012 20:57 tels Relationship added related to 0003053
12.03.2012 21:54 tels Relationship added related to 0001718
12.03.2012 21:54 tels Relationship added related to 0001719
28.03.2013 01:48 grayman Note Added: 0005252
28.03.2013 01:48 grayman Assigned To => grayman
28.03.2013 01:48 grayman Status new => assigned
28.03.2013 01:48 grayman Note Edited: 0005252
28.03.2013 20:12 grayman Assigned To grayman =>
28.03.2013 21:40 Springheel Note Added: 0005257
29.03.2013 00:34 grayman Note Added: 0005261
30.03.2013 01:09 Springheel Note Added: 0005266
30.03.2013 01:09 Springheel Status assigned => closed
30.03.2013 01:09 Springheel Assigned To => Springheel
30.03.2013 01:09 Springheel Resolution open => fixed