View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001964 | FSSCP | tables | public | 2009-07-16 23:38 | 2009-08-23 09:46 |
| Reporter | chief1983 | Assigned To | Wanderer | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.6.11 | ||||
| Summary | 0001964: ship_set_default_weapons() contains hardcoded retail weapon names | ||||
| Description | So a change_ship_type() call leads to ship_set_default_weapons() being called. When there are more banks on the ship than the table defines, it tries to fill the holes with Light Lasers and Rockeyes via: // Make unspecified weapon for bank be a Light Laser swp->primary_bank_weapons[i] = weapon_info_lookup(NOX("Light Laser")); and // Make unspecified weapon for bank be a Rockeye Missile swp->secondary_bank_weapons[i] = weapon_info_lookup(NOX("Rockeye Missile")); We already have a player weapon precedence table, shouldn't it go through that in order and pick the first one by some more intelligent means? | ||||
| Tags | No tags attached. | ||||
