View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000102 | FSSCP | gameplay | public | 2004-02-11 20:42 | 2004-02-20 05:30 |
| Reporter | Skippy | Assigned To | Goober5000 | ||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0000102: Cruiser not attacking fighters when ordered | ||||
| Description | In a created mission, when a cruiser (like a deimos) is ordered to attacked a fighter or a bomber, it won't move to its current, even to reach beam range. However, when ordered to attack a capital ship, there's no problem, it'll move towards it. | ||||
| Tags | No tags attached. | ||||
|
|
This is present in all the builds (but impossible to test in the original FS2) |
|
|
Um, I don't think this is a valid AI behavior. You should build the mission so that the cruiser is scripted to move to a certain waypoint. If you can't predict where the enemy fighter is going to be, then you should deploy a fighter wing of your own to intercept it. Not a cruiser. |
|
|
The cruiser is supposed to attack Alpha wing (ai-chase order), and Alpha wing is supposed to lure it from it's current position AND prevent him from reaching its final position if that cruiser moves to intercept. I can't be more precise, or by PM only (it's a project mission) |
|
|
PM me, please. |
|
|
Resolved via FRED. Closing. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-02-11 20:42 | Skippy | New Issue | |
| 2004-02-11 20:44 | Skippy | Note Added: 0000189 | |
| 2004-02-12 05:03 | Goober5000 | Note Added: 0000192 | |
| 2004-02-12 05:03 | Goober5000 | Status | new => assigned |
| 2004-02-12 05:03 | Goober5000 | Assigned To | => Goober5000 |
| 2004-02-12 06:20 | Skippy | Note Added: 0000195 | |
| 2004-02-12 13:53 | Goober5000 | Note Added: 0000196 | |
| 2004-02-20 05:30 | Goober5000 | Status | assigned => closed |
| 2004-02-20 05:30 | Goober5000 | Note Added: 0000208 |