script-spawned police doesn't get correct scan_class

[Commander McLane]

If a ship with role "police" is spawned by a script (or via the console) it does not get CLASS_POLICE, but CLASS_NEUTRAL, if no scan_class is specified in its shipdata. If it's spawned by the populator, the correct scan_class is assigned, even if there is no entry in shipdata. But script-added police currently need their scan_class explicitly set.

I think that's a bug.

[Thargoid]

As suggested elsewhere, could the auto_AI flag in shipdata.plist also be used to set the scanClass for appropriate roles? For example if auto_AI is true and the role is "police" or "wingman" (and possibly others too) then the scanClass gets auto-set to the appropriate values too.

[Kaks]

Doesn't sound too undoable...

[Eric Walch]

Doesn't sound too undoable...

Its an easy addition to the current code that sets bounty for some script added ships. Looking at the code, the populator does not force a CLASS_POLICE for police on route. Only when no scan_class was set it becomes police scan_class. That means when you define CLASS_MILITARY for a police, it will keep its military class. I don't think that is wanted behaviour as that will lead to adding not wingman but escorts and they will get a military scanclass from their mother. So it will be a military ship with civilian escort-ship that have a military label.

stations do it different again. Patrol is forced to CLASS_POLICE, while defence_ships keep their scan_class from shipData. When no class was defined, they keep a CLASS_NOT_SET.

All the code starts with newShipWithRole:, so adding the fix there will also force police on the other locations to CLASS_POLICE unless auto_ai is explicitly set to false. So I leave the code on the other locations as it is at that fix will so a lot of the potential other problems.

----
I also took a look on thargoids. When added in interstellar space they always get a CLASS_THARGOID but in normal space only when no other scan_class was defined for them. Look a bit buggy when they are handled differently. But there is no auto_ai for thargoids because the populator never has altered their AI. I don't want to change that and risking breakage of existing thargoids.

[Eric Walch]

As suggested elsewhere, could the auto_AI flag in shipdata.plist also be used to set the scanClass for appropriate roles? For example if auto_AI is true and the role is "police" or "wingman" (and possibly others too) then the scanClass gets auto-set to the appropriate values too.

That is the approach I am following. But what looked like a simple 1 line change proofs to be more work. Not directly because of this bug, but checking against other code to make sure I don't introduce new bugs lets me stumble over all kind of other small bugs/inconsistencies.

wingman need no special handling. They are only selected when the mother has police scan_class and they inherit their mothers scan_class. But interceptors need also get a scan_class set. And they need a correct pilot. The populator adds police characters as pilot, but a script will add a random character to an interceptor. So they could have bounties than.
Populator added interceptors are added in game with a primary role of police. I will change trunk so the same happens for script added ones. That way they automatically receive the correct 'police' pilot. (= clean with 125 ₢. insurance).

I'll make script and populater consistent. With auto_ai = true (default) or without scan_class defined, the police (and interceptors) will always be forced into a police scanclass. With auto_ai = false the defined scan_class will be used. Probably never useful, but who knows what use for it some scripters might invent

[Kaks]

Probably never useful, but who knows what use for it some scripters might invent

/me looks causally at McLane & Thargoid

[CommonSenseOTB]

Probably never useful, but who knows what use for it some scripters might invent

/me looks casually at McLane & Thargoid

Stolen Viper oxp perhaps?

[Thargoid]

/me whistles innocently...