Difference between revisions of "Development:Missions"
(→See also) |
m (Switched SVN URLs to GH) |
||
| (18 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{NAV_Manual | | {{NAV_Manual | | ||
| − | | previous=[[ | + | | previous=[[Development:Campaigns|Edit Campaigns]] |
| − | | up=[[ | + | | up=[[HowTos]] |
| − | | next=[[HowTo: | + | | next=[[HowTo:Edit News|Edit News]] |
}} | }} | ||
---- | ---- | ||
| − | |||
==EDITING MISSIONS== | ==EDITING MISSIONS== | ||
{{attention}} | {{attention}} | ||
| Line 16: | Line 15: | ||
===[[HowTo:Edit_Missions:Python:Missions|Python Inheritance In Missions]]=== | ===[[HowTo:Edit_Missions:Python:Missions|Python Inheritance In Missions]]=== | ||
| − | === | + | ===Conclusions=== |
| − | + | Well this is the best I can do so far. Please read this documentation over and let me know if you have any suggestions or clarifications. And best yet give it a shot and try it out. And at least look at | |
| − | + | '''[https://github.com/vegastrike/Assets-Production/tree/master/modules/missions/cargo_mission.py modules/missions/cargo_mission.py]''' (which is called from a number of missions I think) as well as '''[https://github.com/vegastrike/Assets-Production/blob/master/modules/missions/privateer.py modules/missions/privateer.py]''' called by '''[https://github.com/vegastrike/Assets-Production/blob/master/mission/explore_universe.mission mission/explore_universe.mission]'''. And certainly try to understand '''[https://github.com/vegastrike/Assets-Production/blob/master/modules/quests/quest_drone.py modules/quests/quest_drone.py]''' before trying to write a quest (or while trying to write one). | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Please also have a look in [[Development:Quests]] for a detailed explanation on the structure of quests and an explanation on how they work. | |
| − | |||
==See also== | ==See also== | ||
| − | * [[HowTo: | + | * [[HowTo:Add_Conversations]] |
| − | |||
* [[HowTo:Edit_News]] | * [[HowTo:Edit_News]] | ||
| + | * [[Development:Campaigns]] | ||
| − | + | ---- | |
{{NAV_Manual | | {{NAV_Manual | | ||
| − | | previous=[[ | + | | previous=[[Development:Campaigns|Edit Campaigns]] |
| − | | up=[[ | + | | up=[[HowTos]] |
| − | | next=[[HowTo: | + | | next=[[HowTo:Edit News|Edit News]] |
}} | }} | ||
| − | + | ||
| − | [[Category: | + | [[Category:HowTos|Edit Missions]] |
| + | [[Category:Development|Edit Missions]] | ||
Latest revision as of 18:58, 22 March 2020
 Edit Campaigns
|
 HowTos
|
Edit News 
|
Contents
EDITING MISSIONS
Introduction
Vega Strike has a powerful missions scripting interface that allows you to nearly modify Vega Strike at whatever level you choose, from the AI scripts (and the physics thereof) to the missions... to the overall plot and goal of the game.
Basic XML integration
Python Inheritance In Missions
Conclusions
Well this is the best I can do so far. Please read this documentation over and let me know if you have any suggestions or clarifications. And best yet give it a shot and try it out. And at least look at modules/missions/cargo_mission.py (which is called from a number of missions I think) as well as modules/missions/privateer.py called by mission/explore_universe.mission. And certainly try to understand modules/quests/quest_drone.py before trying to write a quest (or while trying to write one).
Please also have a look in Development:Quests for a detailed explanation on the structure of quests and an explanation on how they work.
See also
| Edit Campaigns
|
HowTos
|
Edit News
|
