@Ahruman
Posted: Wed Apr 23, 2008 10:19 am
@Ahruman: Specifically! Please, please, please explain *drags hair around* *foams from the mouth* *makes uneligible gargling noises*
Total confusion now ...
PLEASE, again for dummies (me!), slowly for writing down.
... will work as intended and WITHOUT breaking other OXPs in the process or not???
And does it mean that this like_ship thingy mentioned here ...
As I need the information and everyone is telling me something diverging now and I have no idea, please respond, I should be so lucky. (No, no Kylie Minogue advertisements here)
Nervewrecked
L
Total confusion now ...
PLEASE, again for dummies (me!), slowly for writing down.
Does this mean that ...As I stated yesterday in this very thread, scanForNearestShipWithRole: will not see such NPCs as the player, because it only searches by primary role. NPC ships would have “player” in their role set, but never as the primary role, so this problem does not exist. In older versions of Oolite, only the primary role was stored, except in some exceptional (buggy) cases, so this shouldn’t be a problem there either. Whether it’s a useful thing to do is another matter.
Code: Select all
<key>roles</key>
<string>player hunter trader pirate</string>
And does it mean that this like_ship thingy mentioned here ...
... is no longer nescessary or not?Ahruman wrote:Commander McLane wrote:
If you examine the original shipdata.plist (the one inside your Oolite.app (you're on a Mac, aren't you?)), you will see that it doesn't even use the like_ship-key.
I think this is mostly a historical curiosity.
As I need the information and everyone is telling me something diverging now and I have no idea, please respond, I should be so lucky. (No, no Kylie Minogue advertisements here)
Nervewrecked
L