Difference between revisions of "Development:Quests & Campaigns"

From VsWiki
Jump to: navigation, search
m (Common References)
m (Implementation References)
Line 31: Line 31:
  
 
==Implementation References==
 
==Implementation References==
===[[HowTo:Edit_Missions:Python:Bindings:CPP|VegaStrike C++ Funcions]]===
+
===[[HowTo:Edit_Missions:Python:Bindings:CPP|VegaStrike C++ Funcions Listing]]===
  
===[[HowTo:Edit_Missions:Python:Bindings:Python|VegaStrike Python Funcions]]===
+
===[[HowTo:Edit_Missions:Python:Bindings:Python|VegaStrike Python Funcions Listing]]===
 +
 
 +
===[[Development:Python:Functions|Useful Python Functions]]===
  
 
=See also=
 
=See also=

Revision as of 11:30, 22 April 2008

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.

Explanations

Summary about Python-Vegastrike Class Relationships

Python - Vega Strike Bindings

Python Inheritance with AI Scripts

Implementation References

VegaStrike C++ Funcions Listing

VegaStrike Python Funcions Listing

Useful Python Functions

See also