Difference between revisions of "Development:Quests & Campaigns"
m (→Implementation References) |
m (→Implementation References: sp) |
||
| Line 31: | Line 31: | ||
==Implementation References== | ==Implementation References== | ||
| − | ===[[HowTo:Edit_Missions:Python:Bindings:CPP|VegaStrike C++ | + | ===[[HowTo:Edit_Missions:Python:Bindings:CPP|VegaStrike C++ Functions Listing]]=== |
| − | ===[[HowTo:Edit_Missions:Python:Bindings:Python|VegaStrike Python | + | ===[[HowTo:Edit_Missions:Python:Bindings:Python|VegaStrike Python Functions Listing]]=== |
===[[Development:Python:Functions|Useful Python Functions]]=== | ===[[Development:Python:Functions|Useful Python Functions]]=== | ||
Latest revision as of 17:48, 1 June 2010
This page is meant to provide a platform for campaign, mission, and quest & adventure programmers to describe the python scripting mechanisms and merge their ideas and best practices...
Campaigns, Missions, Quests & Adventures
Campaigns
Campaigns describe the overall plot in which the player is involved. From the campaigns various missions are given depending on the progress of the universe and its various conditions.
For more information, head over to Development:Campaigns.
Missions
Missions can be nodes of a campaign or independent missions available through fixers or the mission interface.
For mission editing, refer to Development:Missions.
Quests and Adventures
Quests are equivalent to adventures and are independent events that happen in specific systems when the player is there.
A description on creating quests can be found in Development:Quests.
Common References
Python scripting reference for campaigns, missions, and quests.
