RE: Campaign creation
Posted: Sat Oct 21, 2006 11:53 am
by Zanthras
There is a sample campaign that breaks down the first two original SS campaigns. I checked grouper, but couldnt find it, so I downloaded it to my local folder. Maybe one of the other guys from the grouper network might know its location...
let me know if you can pull it off grouper, otherwise I can email it to you...
~Z~
a lesser campaign
Posted: Sat Oct 21, 2006 12:15 pm
by Zanthras
Hey I almost forgot...there is also a way to dat a group of missions together as well, basically the same way as creating a ship mod...but slight diff to the mod_info.def file...here is an example from one I created. You can include as many missions as you like as part of the dat.
MOD_INFO
name: "Operation Backtrack"
version: 8
distribute: true
logo: "swtwc.pcx"
desc: "Provide escort for civilian transports as the\n Alliance conducts an orderly retreat from\n the Garrison system.\n\n (Third mission in the 'Long way from home' series.\n\n Require Heavy Spectre and Ssbet (BB set) mods"
copyright: "Copyright (c) 2005 XM productions.\nAll rights reserved."
campaign: { name: "Operation Backtrack", path: "Mods/Missions" }
This will show up in the 'campaign' section after you select missions from the main menu. There isnt really anyway to put missions in any particular order and it wont take advantage of the dynamics in creating missions. They run scripted, the same every time...
just something I thought might be useful to know...
~Z~
RE: Campaign creation
Posted: Mon Oct 23, 2006 9:39 am
by Zanthras
Actions- folder containing txt and pcx files for news, mail and debriefs...see example
campaign_end.txt file
Alliance forces have completed operations in the Solus-Renser Theater. Hegemony resistance has been broken and the Prefect of Renser is meeting with the Alliance Provisional Consulate at this hour to establish terms for a cease-fire and eventual non-agression pact.
All Force:Space units in Third Fleet will be withdrawing from Renser space to predetermined guard points in the surrounding systems. Force:Command expects to be able to rotate your unit back to home space within a few weeks for replenishment and shore leave.
Well done, Commander!
note the pcx files from 4.5 offer different sizes to accomidate different screeen resolutions.
Templates - folder containing mission template files saved in txt, basically a mission def file. see example below...
From the DS_escort_03.def file
MISSION_TEMPLATE
name: "Freight Escort"
type: ESCORT_FREIGHT
system: Solus
region: Trellis
degrees: true
alias: { name: FC1, elem: "Trellis-Solus" }
alias: { name: Obs, elem: "Tal Vesta Stellar Observatory" }
callsign: { name: Alpha, iff: 2 }
callsign: { name: Bravo, iff: 2 }
element: {
name: Ward,
design: TypeIII,
rloc: { ref: FC1, dex: 180e3, dex_var: 50e3, el: 0, el_var: 0 },
mission: freight,
count: 1,
iff: 1,
intel: tracked,
hold: 900,
navpt: { cmd: vector, rloc: { ref: Ward, dex: 50e3, dex_var:10e3, el: 0, el_var: 0 }, speed: 450, rgn: Trellis },
navpt: { cmd: vector, rloc: { ref: Obs, dex: 40e3, dex_var:10e3, el: 0, el_var: 0 }, speed: 450, rgn: Meridian },
}
ward: Ward
alias: {
name: Player,
code: player,
mission: escort_freight,
navpt: { cmd: vector, rloc: { ref: "Ward", dex: 15e3, az: 270, az_var: 20, el_var: 0 }, speed: 500, rgn: Trellis },
navpt: { cmd: escort, rloc: { ref: "Ward:1", dex: 10e3, az: 270, az_var: 30, el_var: 0 }, speed: 500, rgn: Trellis },
navpt: { cmd: escort, rloc: { ref: "Ward:2", dex: 7e3, az: 270, az_var: 20, el_var: 0 }, speed: 500, rgn: Meridian },
navpt: { cmd: rtb, rloc: { ref: Player, dex: 20e3, el_var: 0 }, speed: 250, rgn: Trellis },
objective: { cmd: patrol, tgt_desc: "inbound enemy units" },
objective: { cmd: escort, tgt: Ward, tgt_desc: "the merchant vessel" },
}
event: {
id: 1,
event: Hold,
event_ship: Ward,
event_param: 0,
trigger: Navpoint,
trigger_ship: Player,
trigger_param: 1,
}
event: {
id: 2,
event: Message,
event_ship: Player,
event_source: Ward,
event_message: "Glad to see you guys! Thanks for escorting us.",
event_chance: 50,
trigger: Event,
trigger_param: 1,
delay: 1,
}
the template file will ref a template list file, which you may already have...see example below.
TEMPLATELIST
// specialized templates first
mission: { type: PATROL, group: INTERCEPT_SQUADRON, script: "Templates/IS_Patrol_HS.def", rgn: Solus, name: "Harmony Patrol", after: "05/12:00:00", exec_once: 1 }
mission: { type: PATROL, group: FIGHTER_SQUADRON, script: "Templates/FS_Patrol_HS.def", rgn: Solus, name: "Harmony Patrol", after: "05/12:00:00", exec_once: 1 }
// then general templates
mission: { type: PATROL, group: INTERCEPT_SQUADRON, script: "Templates/IS_Patrol_01.def" }
mission: { type: PATROL, group: FIGHTER_SQUADRON, script: "Templates/FS_Patrol_01.def" }
mission: { type: PATROL, group: INTERCEPT_SQUADRON, script: "Templates/IS_Patrol_02.def" }
mission: { type: PATROL, group: FIGHTER_SQUADRON, script: "Templates/FS_Patrol_02.def" }
mission: { type: PATROL, group: INTERCEPT_SQUADRON, script: "Templates/IS_Patrol_03.def" }
mission: { type: PATROL, group: FIGHTER_SQUADRON, script: "Templates/FS_Patrol_03.def" }
this is only a partial list from the templatelist file...
other files that you might already know about...the order of battle file, (this is from the Alliance.def file)
ORDER_OF_BATTLE
group: {
type: force,
id: 1,
name: "Terellian Alliance",
intel: known,
iff: 1,
loc: (0, 0, 0),
}
// -----------------------
// JARNELL
group: {
type: fleet,
id: 1,
name: "Aradiel",
intel: known,
iff: 1,
region: "Jarnell",
loc: (0, 0, 0),
parent_type: force,
parent_id: 1,
}
group: {
type: carrier_group,
id: 4,
name: "Aradiel",
intel: known,
iff: 1,
region: "Jarnell",
loc: (-130e3, 50e3, 0),
parent_type: fleet,
parent_id: 1,
unit: {
name: "Aradiel",
type: "Carrier",
design: "Aradiel",
regnum: "69",
},
unit: {
name: "Adonai",
type: "Battleship",
design: "Adonai",
regnum: "521",
},
unit: {
name: "Merkava",
type: "Destroyer",
design: "Merkava",
regnum: "708",
},
}
and finally the zones file, again this is only a partial list...
ZONES
zone: {
system: Solus,
region: Meridian
}
zone: {
system: Solus,
region: Solus,
region: Telmera,
region: Omane
}
zone: {
system: Solus,
region: Jalah
}
zone: {
system: Solus,
region: Trellis
}
zone: {
system: Renser,
region: Garana
}
hope this proves helpful.
RE: Campaign creation
Posted: Tue Oct 24, 2006 11:37 am
by Zanthras
I sent you a couple emails with the complete data for the Template.def file and the Templatelist file. Let me know if you got them...
The campaign.ace file that is posted on grouper should have all the info that I have, not sure if that is where you got it.
I applaude your attempt to put together a campaign, although it doesnt apprear to be that hard, it certainly could be time consuming from scratch. I know with the missions I created it took many hours of testing and trying to make one working mission, something challenging with a lot of content. Based on my methods and ideas I guess it might take me hundreds of hours to complete a full campaign with some in depth content, personally I cant justify the time it might take right now...maybe this winter though.
I suppose if you simpified things and minimized content it might take a lot less...all depends on what you are looking to achieve. Whatever the case might be, simple or complex, anybody that does this will be the first person I am aware of that has put together a real campaign beyond the original 4. Good luck!
If I can be of any other help, let me know...
RE: Campaign creation
Posted: Wed Oct 25, 2006 3:51 am
by Dragonlead
Zanthras,
I got your emails. Thanks much!! I also sent you a reply as well. I welcome your input. It takes me quite a while as well for any complex mission, but from the looks of things, not every mission is "custom". That might simplify things a bit.
I welcome any inputs from anyone else out there who has worked on this and has tips, techniques and procedures they are willing to share.
V/R