OBD:BINA/OBJC/CMBT
|
|
File description
General settings
| Offset | Type | Raw Hex | Value | Description |
|---|---|---|---|---|
| 0x00 | char[4] | 43 4A 42 4F | OBJC | object collection |
| 0x04 | int32 | B0 0D 00 00 | 35628 | size of the complete combat part from this postion in bytes |
| 0x08 | int32 | 27 00 00 00 | 39 | unknown; do not change it |
| 0x0C | int32 | B4 00 00 00 | 180 | size of the following element in bytes |
| First element (black outline) | ||||
| 0x00 | char[4] | 54 42 4D 43 | TBMC | combat |
| 0x04 | int32 | 70 01 00 00 | 368 | old file ID |
| 0x08 | int32 | 00 00 00 00 | 0 | unknown |
| 0x0C | float | 13 55 5F C3 | -223.332321 | x-position of unknown |
| 0x10 | float | D4 A8 8E 41 | 17.832436 | y-position (height) of unknown |
| 0x14 | float | C3 05 E9 C2 | -116.511253 | z-position of unknown |
| 0x18 | float | 00 00 00 00 | 0.000000 | rotation on the x-axis in degrees |
| 0x1C | float | 00 00 00 00 | 0.000000 | rotation on the y-axis in degrees |
| 0x20 | float | 00 00 00 00 | 0.000000 | rotation on the z-axis in degrees |
| 0x24 | char[64] | Stand_and_Fire | space for notes | |
| 0x64 | int32 | 00 00 00 00 | 0 | combat ID (looked up from Character.BINA) |
Behavior part
| Offset | Type | Raw Hex | Value | Description |
|---|---|---|---|---|
| 0x68 | int32 | 02 00 00 00 | 2 | long range behavior; the following values are possible (values in dec):
|
| 0x6C | int32 | 02 00 00 00 | 2 | medium range behavior; values as above |
| 0x70 | int32 | 02 00 00 00 | 2 | short range behavior (hand to hand behavior); values as above |
| 0x74 | int32 | 02 00 00 00 | 2 | medium retreat behavior; values as above |
| 0x78 | int32 | 02 00 00 00 | 2 | long retreat behavior; values as above |
Combat part
| Offset | Type | Raw Hex | Value | Description |
|---|---|---|---|---|
| 0x7C | float | 00 00 F0 42 | 120.000000 | long/medium range; distance of the border between long and medium ranges; you can make it visible with the script command *ai2_showcombatranges = 1* |
| 0x80 | int32 | 01 00 00 00 | 1 | melee override; see below; the following values are possible:
|
| 0x84 | int32 | 00 00 00 00 | 0 | if no gun; behavior of AI which doesn't have a gun in its hand ( but can have it holstered); the following values are possible:
|
| 0x88 | float | 00 00 20 42 | 40.000000 | medium/short range; distance of the border between medium and short ranges; you can make it visible with the script command *ai2_showcombatranges = 1* |
| 0x8C | float | 00 00 48 43 | 200.000000 | pursuit distance; see below for info |
Non-combatant part
| Offset | Type | Raw Hex | Value | Description |
|---|---|---|---|---|
| 0x90 | int32 | 58 02 00 00 | 600 | panic hurt (time in 1/60 seconds) |
| 0x94 | int32 | 84 03 00 00 | 900 | panic gunfire (time in 1/60 seconds) |
| 0x98 | int32 | 58 02 00 00 | 600 | panic melee (time in 1/60 seconds) |
| 0x9C | int32 | B0 04 00 00 | 1200 | panic sight (time in 1/60 seconds) |
Alarm part
| Offset | Type | Raw Hex | Value | Description |
|---|---|---|---|---|
| 0xA0 | float | 00 00 96 43 | 300.000000 | alarm search distance |
| 0xA4 | float | 00 00 A0 42 | 80.000000 | alarm enemy ignore distance |
| 0xA8 | float | 00 00 00 00 | 0.000000 | alarm enemy attack distance |
| 0xAC | int32 | 1E 00 00 00 | 30 | alarm damage threshold |
| 0xB0 | int32 | 68 01 00 00 | 360 | alarm fight timer |
These settings affect the behavior of an AI that's running for a console (e.g., script command *ai2_doalarm*).
- alarm search distance
- area around AI, where engine checks if there is some console with 40 bit (see CONS).
- Alarm enemy ignore distance
- This one specifies an "ignore range". Enemies which are inside this range are not ignored but AI doesn't attack them.
- Alarm enemy attack distance
- Zero by default.
- 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)
- 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.
- Fight timer
- 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.
- Alarm damage threshold
- 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*.
Whole alarm logic can be tripped by:
- *ai2_doalarm* command (suitable for geyser's rugby)
- *run for alarm* (0b) behavior, altough this behavior alone does NOTHING, it just turns on *alarm search distance*. If there is no console with 40 bit in reach, AI stands still and just stares.
- *run to alarm* if no gun event ( only when AI is unarmed ), again it turns on *alarm search distance*, but this time AI can do normal actions (attack, hunt) if there is no 40 bit console within reach.
- ???Find alarm??? pm_pursue action, still unknown
Further info
About pursuit distance
First of all, pursuit is NOT when you have been seen and now running away. If you do that, AI is in *combat* mode, not *pursue* mode. You are pursued only when you have NOT been seen by central vision field (see ONCC). So if some enemy does sound that touches AI's sound detection sphere, or when some enemy interferes with AI's peripheral vision field, AI goes into pursue mode with him. In this mode AI uses special behavior for investigating. According to the EXE, possibilities are (dunno if it is in proper order, it is raw EXE rip):
- Find Alarm
- Keep Looking
- Return To Job
- Glance
- Hunt - not implemented in Oni (accidentaly I have read error message in Manplant a few months ago saying that)
- Move
- Look
- Wait
- GoTo
- Forget
What AI does while in pursuit mode depends on the last values in CHAR. But it is still unknown how it works. It also depends on the alert level of an AI (lull, low, med, high, combat). Pursuit mode lasts from the moment of the disturbing action until AI goes to forgotten hostilethreat for enemy action, or after one investigation loop for friendlythreat action (see ONCC for info about ...threats).
So...what is the pursuit distance??? It is distance that is AI allowed to travel from its original location for *pursue* purposes. Set it high and AI can run through whole level if it hears or spots something. Set it low and AI will do just a few steps in a direction of disturbing action.
About melee override
First something about minimal shooting distance.It is in the ONWC and determines closest range for AI to fire that weapon. If enemy goes closer, AI stops shooting and tends to run away until it reahes minimal shooting distance again. Now if you set this minimal shooting distance higher than it is originally (for example try 200) you can have some fun chasing AIs as they are running away from you.
Point is that if you set melee override to some range (for example 03 - short range) and then try it, you will see that the moment you are closer than minimal shooting distance AND you are in range which enables it (short range in this example) AI will switch to melee mode instead of running away.
So you can make short range for example 200 units big and set min.shoot.dist. 100 units big and have melee override 03 -short range. AI will then shoot at you even if you are inside short range, but the moment you ecounter min.shoot.dist. it switches to melee.
How it switches back to weapon when you run away back into min.shoot.dist. is not clear. So far it happens automatically after some time. Where is timer for that??? Let us know, if you know....
--Loser 09:03, 29 July 2007 (CEST)
Bluebox screenshot
|
|
Neu = New |
| ONI BINARY DATA |
|---|
| AKVA << Other file types >> CBPI |
| BINA : Binary data |
| TMBD << Other BINA >> ONIE |
| OBJC : Objects |
| CHAR << Other OBJC >> CONS |
| CMBT : Combat profile |
| [[OBD:File types/{{{family}}}|{{{family}}} file]] |