oolite/Resources/Config/characters.plist
Eric Walch b8359a110b - Added a JS script to pilots. On unloading at a station, the event "unloadCharacter()" is send to the pilot-script.
- Characters in character.plist now always do a basic setup. That way there is always a valid pilot when not using all character keys. This allows for partial randomisation of pilots for the unused keys.
- Added a JS script for the constrictor-pilot.
- Added default pilots to be used by oxps.

git-svn-id: http://svn.berlios.de/svnroot/repos/oolite-linux/trunk@3841 127b21dd-08f5-0310-b4b7-95ae10353056
2010-11-30 20:11:45 +00:00

45 lines
933 B
Plaintext

{
"constrictor-mission-thief" =
{
"random_seed" = "1 3 5 7 11 13"; // fix the name and details, but use the key to keep it secret
bounty = 1000; // not actually used, we do the reward in the script
origin = 7; // system number seven (Lave in Galaxy 0)
script = "oolite-constrictor-pilot.js";
};
/*
For ships added in custom roles, Oolite will always add a randomised pilot.
When you want control over the bounty and insurance of the pilot, you can define
a specific pilot for your ship by using one of the following character keys as pilot
in shipdata.plist. e.g.: "pilot" = "oolite-trader";
*/
"oolite-hunter" =
{
role = "hunter";
};
"oolite-miner" =
{
role = "miner";
};
"oolite-passenger" =
{
role = "passenger";
};
"oolite-pirate" =
{
role = "pirate";
};
"oolite-police" =
{
role = "police";
};
"oolite-slave" =
{
role = "slave";
};
"oolite-trader" =
{
role = "trader";
};
}