Difference between revisions of "Category talk:Oolite"
From Elite Wiki
Line 41: | Line 41: | ||
Several of these plists still need a link in the directory, might I suggest grouping them under a topic called 'property lists'? | Several of these plists still need a link in the directory, might I suggest grouping them under a topic called 'property lists'? | ||
-Yours Arexack. | -Yours Arexack. | ||
+ | |||
+ | : well, it's a slow business making these things ;) | ||
+ | : you mean that several of the 'lesser' plists go together on one page? ''Property list omnibus''? :D | ||
+ | :the intent was to go about it in a pyramid sort of way, and let it grow from there. from OXP to OXP_howto to OXP_howto_plist, ..to_model, ..to_texture, etc. and from within each of those to link to all the necessary (greater) detail pages headed by the proper name of the item. but that, for instance, howto_plist would be the root..[[User:Murgh|Murgh]] |
Revision as of 19:29, 19 January 2006
Scripting: (refer to AI-reference.html)
General scripting: Methods Messages AI-states etc (+introduced since which version)
AI-scripting: SomeAI.plist [examples] specific methods/syntax?
Scripting in other property lists (Config); Many of the same scriptingmethods can be used as in AI-scripting.
Shipdata.plist
Scripted_actions Death_actions
Script.plist
Conditions greaterThan, lessThan, ifElse etc Do methods [Example: meeting a ship at witchpoint] Specific methods/syntax..
Mission scripting
Missiontext.plist..
planetinfo.plist
[example: placing a moon] specific keys, methods etc..
demoShips.plist -none.. hud.plist -none.. shipyard.plist -same as shipdata.plist.. commodities.plist -none.. speech_pronunciation_guide -none.. descriptions.plist -none..
Several of these plists still need a link in the directory, might I suggest grouping them under a topic called 'property lists'? -Yours Arexack.
- well, it's a slow business making these things ;)
- you mean that several of the 'lesser' plists go together on one page? Property list omnibus? :D
- the intent was to go about it in a pyramid sort of way, and let it grow from there. from OXP to OXP_howto to OXP_howto_plist, ..to_model, ..to_texture, etc. and from within each of those to link to all the necessary (greater) detail pages headed by the proper name of the item. but that, for instance, howto_plist would be the root..Murgh