OBD:BINA/OBJC/CMBT: Difference between revisions

OBD:BINA/OBJC/CMBT (view source)

Revision as of 12:43, 27 December 2006

978 bytes removed , 27 December 2006

→‎Alarm behavior

Loser

271

edits

@@ Line 203: / Line 203: @@
 | BGCOLOR="#C8C864" | 68 01 00 00
 | 360
-| ALIGN=LEFT | alarm fight timer; same as fight timer in [[OBD:ONCC|ONCC]], but this works while AI is in run for alarm mode
+| ALIGN=LEFT | alarm fight timer; see below
 |}
 ;Alarm enemy ignore distance
-:This one specifies an "ignore range". Enemies which are inside this range are NOT ignored. Ignored are those ''outside'' this range.
+:This one specifies an "ignore range". Enemies which are inside this range are not ignored but AI doesn't attack them.
-::(''well, naturally'' [[User:Geyser|geyser]])
-:When AI doesn't ignore it does NOT mean it attacks. It only knows when there's an enemy nearby and it tries to face that enemy while still on the move. So it runs in a weird way.
-::(''that's probably meant for more efficient auto-blocking or something'' [[User:Geyser|geyser]])
 ;Alarm enemy attack distance
-:WHY - IS - IT - '''ZERO'''??? Seriously. It is ''really'' set to zero by default.
+:Zero by default.
-::(''same reason as for the weapon dodging, heh'' [[User:Geyser|geyser]])
+:This one specifies an "attack range" around an AI running for an alarm. When there is an enemy inside, AI stops running for the console and attack the enemy (if AI knows about him, of course)
-:This one specifies another range around an AI that's running for a console.
+:Nevertheless AI still keeps in mind that it should run for the console. So when there is no enemy inside this range and fight timer runs out, AI resumes running to the specified console.
-:When there is an enemy inside this range and the AI ''knows'' about that enemy (i.e., doesn't ignore it due to the "ignore" range above), it will stop running for the console and attack the enemy.
+;Fight timer
-:But, at the same time, AI still keeps in mind that it should run for alarm. So when there is no enemy inside this range, AI resumes running to the specified console.
+:When AI, which is running for the console, is engaged in a fight and enemy manages to disappear (either by phase-cloak or simply by hiding behind some corner), AI tries to chase him or looks for him. Alarm timer specifies how long should AI chase/look for the enemy. For chasing, timer starts when the enemy is outside *Alarm enemy attack distance*. Of course when the enemy escapes even from *Alarm enemy ignore range*, AI abandons him automatically.
-;Note
-:So if you have "ignore range" > "attack range" > 0, you get what I was searching for (for half a year or so):
-::If an enemy is running for an alarm and you get too close, they'll stop, turn and start fighting with you.
-::When you are far enough (or dead), they'll resume running ^_^'.
-:You don't know how wicked this feature is until you've tried it out yourself.
-::^_-
 ;Alarm damage threshold
-:it has something to do with run-to-alarm abortion, but I don't quite get it.
+:Specifies how long AI, which is running for the console, remembers someone hurt it. Until this timer runs away, AI doesn't tend to use console. It only stays in fight stance near console, ready to fight. If someone hurts AI which is running for the console, then escapes and then tries to hurt it again while this timer isn't finished yet, AI remembers him and initatively attacks him the moment he steps inside *Alarm enemy attack distance*.
-:It looks like an amount of damage when AI exits run for alarm state and acts as usual.
-:But damage taken while fighting someone within the "alarm enemy attack range" doesn't count.
-::[[User:Loser|Loser]] 11:31, 17 December 2006 (CET)
 ----
-:As for the "alarm damage threshold", what would make sense to me is the following:
-:*an AI is supposed to run for a console
-:*there's an enemy in its way (within the ranges above)
-:*it stops to fight that enemy
-:*it takes more damage than a certain threshold
-:*it says "So long, sucker" and resumes with its alarm job
-:*(''overriding'' the "attack" range, and maybe the "ignore" range as well)
-:So, it's rather the opposite of your idea, Loser:
-:*alarm running would have top priority
-:*it's the ''fighting'' that would be aborted
-:Doesn't that seem likely? I haven't checked.
-::[[User:Geyser|geyser]] 15:47, 17 December 2006 (CET)
-:Another possibility (perhaps more likely), is suggested by the Big Blue Bow Beta WMDD below.
-:Namely, the "damage threshold" and the timer may be meant to work together
-::(note that they're grouped under the "Attack If Knockdown" label)
-:The idea here is that if there's a physical contact between the runner and an enemy
-::(the enemy attacking the runner)
-:then the runner will stop running and start defending itself
-::(provided the damage it received was above the threshold)
-:and will resume running after a certain delay (the timer).
-:Obviously, that "attack if knockdown" logic would be somewhat redundant if the attack range is large enough.
-:If an AI has already stopped running for a console and is engaging enemies, what use is the "knockdown" check?
-:So I'm not sure, maybe it's the first possibility after all.
-::[[User:Geyser|geyser]] 15:47, 17 December 2006 (CET)
 :Boy, that is ''so'' promising for CTF and Rugby... Thankee, Loser ^^
 ::[[User:Geyser|geyser]] 15:47, 17 December 2006 (CET)
+:Now I can say whole alarm behavior is resurrected. When somebody sees you, he runs for an alarm. If you manage to outrace him, he fights with you, but keeps his eye on every chance for escaping and running for alarm again. When alarm is tripped, it alerts all AIs with proper alarm group number and they either hunt you (if you are inside their pursuit distance) or their alert level is raised to combat or high level.
+:I know there is still *Alarm search distance*, but we doesn't need it (there are plenty of other ways how to check that AI saw enemy and should run for alarm) plus it seems that both *Run For Alarm* behavior and *Run To Alarm* If no gun events are bugged in the same way and are defunct. Or there are missing labels "this is alarm console, you silly AI" in console files. I don't know and I think we can live without that. Or do you think about something else???
+--[[User:Loser|Loser]] 13:43, 27 December 2006 (CET)
 ----