https://wiki.hard-light.org/api.php?action=feedcontributions&feedformat=atom&user=81.182.82.204 2026-11-15T12:15:02Z User contributions MediaWiki 1.43.9 https://wiki.hard-light.org/index.php?title=5_easy_steps_towards_your_FREDucation&diff=1667 2005-06-07T20:39:41Z

<p>81.182.82.204: </p> <hr /> <div>=FRED Tutorial=<br /> <br /> There are lots of people in the FS community at the moment, new and old, who claim they can’t FRED. Some have made the choice voluntarily, others simply don’t know where to start, or don’t think it’s something they’d ever be able to learn. The truth is though, even if you’ve never modded or mapped a computer game in your life, you can master FRED in a relatively short time. The following five steps will hopefully help anyone aspiring to teach themselves FRED to map out their plans and ultimately come out a pro FREDder.<br /> <br /> ----<br /> ==Step 1 - Do the Walkthrough==<br /> <br /> This is the most essential part of any FREDucation. You can, and many have, go straight from a completed walkthrough mission and into a campaigns staff and churn out missions with little difficulty. The walkthrough touches on everything you'll need to know to get you started in FRED, and it's a brilliant tool. However, as V themselves admitted, it's still only an introduction to FRED - even before the SCP, people were doing things with FRED that the original coders had never even considered implementing, let alone realized they were already possible.<br /> <br /> ----<br /> ==Step 2 - Baby steps==<br /> <br /> This will be your first functioning mission. It seems a big jump, to go from the fully documented, completely pre-scripted mission of the walkthrough to a completely new, never before seen mission that comes straight out of your head. But it doesn't have to be. This mission can, and probably should, be very simple - have the player defending a stricken capship while the escape pods are prepared. This could, in theory, be done with no sexps beyond those that control the arrival and departure of the various ships in the mission. Of course, a mission this simple is not ideal, so perhaps having the aim of the mission to defend the same capship until a transport can dock to repair its engines? This requires a higher degree of sexping, though not by much. If you're feeling confident, add a twist - the repaired capship comes under attack from a pair of enemy capital ships, and have the player switch from taking out bombers to taking out turrets, while the home ship manoeuvres to escape. Or completely disregard this and do a totally different scenario. All you need to do is become confident replicating the steps you learned in the Walkthrough - things like messaging, mission goals, waypoints, AI commands - without a guide telling you precisely what you need to do.<br /> <br /> -TIP - Don't skimp on this mission - make it as complete as you can. Include a briefing and debrief, mission goals, background, check the music and title all fit - often completed missions can be adapted for use later on, no matter how simple they will appear once your FREDding skill has improved.<br /> <br /> ----<br /> ==Step 3 - Research==<br /> <br /> OK. By now, you're comfortable with what you learned in the Walkthrough, it's time to expand on your knowledge by researching what others have done. Use VPView to extract Volition missions from Root.vp and have a look at how they did certain things. There are lots of more complex things, like Knossos jumping, or having the player follow waypoints, that the walkthrough does not cover. You could also try looking at the missions from various campaigns that have been released. Things like Derelict and Warzone that had few mods often relied on inventive FREDding to add spice to their missions, and these tactics are still just as or even more valid now, despite the multitude of available mods. You’ll also want to check out the various tips and tricks that were written up way back in the day for FRED1, which are hosted on Freespacewatch. These may seem dated, but much of the core information about mission continuity and ambience remains vitally important for any FREDder.<br /> <br /> ----<br /> ==Step 4 – Linking missions together==<br /> <br /> STOP! By this point, you’re probably starting to feel confident with FRED, and you’ve probably started to get some really good ideas for campaigns you can do – big, bold, impressive campaigns that’re going to explain Capella, sort out Bosch and cure cancer. OK, I’m going to say this bluntly - Do not do this. You are not the first to have this idea, and you will not be the first to fail if you start it. That said, I do think a campaign is a good idea here. Building a campaign forces you to think about consequences, to link your missions together, to develop characters in your wingmen – all very useful traits in a FREDder. But for god’s sake, don’t try to make Inferno or BWO your first project. I recommend building a campaign, no more than 4 or 5 missions long, with no staff other than yourself, and no mods that you can’t make yourself or download already done. Hell, I’d recommend you use no mods at all, but I’d be the first to admit that the FS2 isn’t ideal for certain types of missions – FS2 has no Vasudan or light installations, a woeful selection of civilian craft, and really skimps on certain parts of the Vasudan fleet. Stuff like the GVSc Imhoteph from the Scroll of Atankharzim team, or the GTI Archeron by Robin Varley can be indispensable for certain situations. I’m not saying you need these ships, but if your campaign calls for them, I’m not saying leave them out either.<br /> <br /> There are a few things you need to think about while you build your campaign – the first is obviously the story – you need to make something that keeps the player interested, and that is believable, as well as presenting enough challenges so that it can’t be completed in five minutes. If thinking up plots isn’t your forte, then don't worry - in many cases V has done the work for you. There are plenty of referenced battles and combats, in the briefings, Command briefings, debriefings and messages used in the main campaign, where the player is told about events in the NTF war, but never experiences them, such as large parts of the Colossus’ trek through the NTF systems, or the early days of the battle of Deneb. Creating missions from these stories not only makes things easier by eliminating the need for any mods whatsoever, but also enriches the overall FS community by providing a bit of background to the story that we all know so well.<br /> <br /> Planning your missions beforehand can help combat all three of these, and let’s be honest - it’s a lot of fun. Also, keep in mind that you’re probably still learning to FRED – it might be a good idea to insert an asteroid or nebula mission (nebulae can be disguised as the atmosphere of Gas Giants if your campaigns timeline puts you out of reach of the Shivan’s nebula). These aren’t essential, of course, but learning to use these effectively will expand your FREDding possibilities exponentially, and add just a little more buzz to your campaign. Keep in mind also that this campaign is meant as much for your learning as it is to be played. While it may not be perfectly plausible from the point of view of a single squadron, try to vary your missions a bit. A successful heavy assault mission needs to be designed very differently to, say an interceptor mission, and recon missions are a class unto themselves. You may not be able to fit all of the various mission types into your campaign structure of course, but a little bit of variation is always a good idea.<br /> <br /> -TIP – Try to avoid subspace missions your first time out, unless you have a really, really good reason to put your player there. Subspace is very difficult to get right, and has a lot of drawbacks, outlined in another Volitionwatch article. If you can do it well, that’s great, but keep in mind, it’s very, very difficult to do well<br /> <br /> -NB – making a campaign is in no way essential to learning to FRED – what’s important is the experience you’d gain working with the various environments and commands in FRED, and the interesting situations campaigns often lead to. If you don’t want to commit to what is a decent sized project (even three missions will probably see you sitting in front of a computer for twelve or so hours, plus time for testing.) then don’t. Single missions are just as effective here as a minicampaign, and in many ways even more – you don’t need to worry about linking the various missions together, nor come up with plot plausible reasons to see your player plunging into a nebula or asteroid field.<br /> <br /> ----<br /> ==Step 5 – Test, Test, Test.==<br /> <br /> Beta testing is one of the most boring parts of FREDding, and, in some ways, one of the hardest. I hate doing it myself, especially since I test roughly every 5 or 10 changes, which means I’ll generally test each mission at least a dozen times during FREDding, generally a lot more. However, there’s nothing as irritating as a poorly tested mission, and almost nothing so obvious. Everything you release should be exhaustively tested, and if possible by other people. If you’re doing a campaign, try to get it tested at both the mission by mission level and at the final product, if possible. Your testers will give you bug reports, but also on how the story's moving along, or how the speech is going. Most of these problems can be fixed with a few clicks of the mouse or a few word changes in your messages, but it’s these that can tip a good mission over the line into a great mission.<br /> <br /> Also keep in mind difficulty when Beta testing. You’ll often hear FREDders talk about balance in a mission, that elusive point where it is just enough of a challenge to get the player involved and enjoying himself without being frustratingly difficult. Balance is affected by almost everything in a mission, in varying degrees. Seemingly small things, like the orientation of a capship, or the distance a wing of fighters arrives from the heat of battle, can alter the balance as much as the more obvious things such as the players available ship and weapon loadout (Allowing your pilot to use Helioses to take out freighters is not recommended )<br /> <br /> Well done pilot - you now have all the expertise you’ll need to become a fully fledged member of the FREDding community, with a campaign release under your belt (you were planning to release, right?) and the potential to do pretty much anything. With the possible exception of BWO, there’s not a campaign out there that’d turn down applications from FREDders, or you can start your own project, large or small, and add to the FS universe that way. With the SCP and FSO there’s a myriad of new concepts and abilities coming to FRED, and, despite everything you’ll probably have done by this point, there’ll always be a lot to learn.<br /> <br /> ----<br /> =Links=<br /> <br /> Everything mentioned above, and a few other useful resources, will be listed here.<br /> <br /> [http://www.volitionwatch.com/articles/ Volitionwatch Articles Index ] Some useful articles, which, despite their age, can still be very relevant to FREDders. Pay particular attention to:<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=13 What Makes a Good Mission?]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=26 FRED and the Battle of Endor Syndrome ]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=27 Tunnel Vision: Why Subspace Mission?]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=25 The Problem With User-Created Levels]<br /> <br /> [http://www.3dap.com/hlp/hosted/fredzone FREDZone] A useful resource for FRED information.<br /> <br /> GTI Archeron by Robin Varley<br /> <br /> [http://www.fileplanet.com/dl.aspx?3dactionplanet/freespace/acheron.zip GTI Archeron by Robin Varley] - A well built light installation mod that fills a void in the FS2 Shipset.<br /> <br /> [http://www.3dap.com/hlp/hosted/scroll/download.html GVSC Imhotep from The Scroll of Atankharzim] - Vasudan science ship - another void in the FS2 shipset neatly filled.<br /> <br /> ----<br /> <br /> For any questions regarding FRED not covered by this or the other Wiki documents, try the [http://dynamic4.gamespy.com/~freespace/forums HLP forums]. You can also contact me, Black Wolf, through a Private Message on HLP, or by emailing the_lone_black_wolf@hotmail.com</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=5_easy_steps_towards_your_FREDucation&diff=57 2005-06-07T20:38:59Z

<p>81.182.82.204: </p> <hr /> <div>=FRED Tutorial=<br /> <br /> There are lots of people in the FS community at the moment, new and old, who claim they can’t FRED. Some have made the choice voluntarily, others simply don’t know where to start, or don’t think it’s something they’d ever be able to learn. The truth is though, even if you’ve never modded or mapped a computer game in your life, you can master FRED in a relatively short time. The following five steps will hopefully help anyone aspiring to teach themselves FRED to map out their plans and ultimately come out a pro FREDder.<br /> <br /> ----<br /> ==Step 1 - Do the Walkthrough==<br /> <br /> This is the most essential part of any FREDucation. You can, and many have, go straight from a completed walkthrough mission and into a campaigns staff and churn out missions with little difficulty. The walkthrough touches on everything you'll need to know to get you started in FRED, and it's a brilliant tool. However, as V themselves admitted, it's still only an introduction to FRED - even before the SCP, people were doing things with FRED that the original coders had never even considered implementing, let alone realized they were already possible.<br /> <br /> ----<br /> ==Step 2 - Baby steps==<br /> <br /> This will be your first functioning mission. It seems a big jump, to go from the fully documented, completely pre-scripted mission of the walkthrough to a completely new, never before seen mission that comes straight out of your head. But it doesn't have to be. This mission can, and probably should, be very simple - have the player defending a stricken capship while the escape pods are prepared. This could, in theory, be done with no sexps beyond those that control the arrival and departure of the various ships in the mission. Of course, a mission this simple is not ideal, so perhaps having the aim of the mission to defend the same capship until a transport can dock to repair its engines? This requires a higher degree of sexping, though not by much. If you're feeling confident, add a twist - the repaired capship comes under attack from a pair of enemy capital ships, and have the player switch from taking out bombers to taking out turrets, while the home ship manoeuvres to escape. Or completely disregard this and do a totally different scenario. All you need to do is become confident replicating the steps you learned in the Walkthrough - things like messaging, mission goals, waypoints, AI commands - without a guide telling you precisely what you need to do.<br /> <br /> -TIP - Don't skimp on this mission - make it as complete as you can. Include a briefing and debrief, mission goals, background, check the music and title all fit - often completed missions can be adapted for use later on, no matter how simple they will appear once your FREDding skill has improved.<br /> <br /> ----<br /> ==Step 3 - Research==<br /> <br /> OK. By now, you're comfortable with what you learned in the Walkthrough, it's time to expand on your knowledge by researching what others have done. Use VPView to extract Volition missions from Root.vp and have a look at how they did certain things. There are lots of more complex things, like Knossos jumping, or having the player follow waypoints, that the walkthrough does not cover. You could also try looking at the missions from various campaigns that have been released. Things like Derelict and Warzone that had few mods often relied on inventive FREDding to add spice to their missions, and these tactics are still just as or even more valid now, despite the multitude of available mods. You’ll also want to check out the various tips and tricks that were written up way back in the day for FRED1, which are hosted on Freespacewatch. These may seem dated, but much of the core information about mission continuity and ambience remains vitally important for any FREDder.<br /> <br /> ----<br /> ==Step 4 – Linking missions together==<br /> <br /> STOP! By this point, you’re probably starting to feel confident with FRED, and you’ve probably started to get some really good ideas for campaigns you can do – big, bold, impressive campaigns that’re going to explain Capella, sort out Bosch and cure cancer. OK, I’m going to say this bluntly - Do not do this. You are not the first to have this idea, and you will not be the first to fail if you start it. That said, I do think a campaign is a good idea here. Building a campaign forces you to think about consequences, to link your missions together, to develop characters in your wingmen – all very useful traits in a FREDder. But for god’s sake, don’t try to make Inferno or BWO your first project. I recommend building a campaign, no more than 4 or 5 missions long, with no staff other than yourself, and no mods that you can’t make yourself or download already done. Hell, I’d recommend you use no mods at all, but I’d be the first to admit that the FS2 isn’t ideal for certain types of missions – FS2 has no Vasudan or light installations, a woeful selection of civilian craft, and really skimps on certain parts of the Vasudan fleet. Stuff like the GVSc Imhoteph from the Scroll of Atankharzim team, or the GTI Archeron by Robin Varley can be indispensable for certain situations. I’m not saying you need these ships, but if your campaign calls for them, I’m not saying leave them out either.<br /> <br /> There are a few things you need to think about while you build your campaign – the first is obviously the story – you need to make something that keeps the player interested, and that is believable, as well as presenting enough challenges so that it can’t be completed in five minutes. If thinking up plots isn’t your forte, then don't worry - in many cases V has done the work for you. There are plenty of referenced battles and combats, in the briefings, Command briefings, debriefings and messages used in the main campaign, where the player is told about events in the NTF war, but never experiences them, such as large parts of the Colossus’ trek through the NTF systems, or the early days of the battle of Deneb. Creating missions from these stories not only makes things easier by eliminating the need for any mods whatsoever, but also enriches the overall FS community by providing a bit of background to the story that we all know so well.<br /> <br /> Planning your missions beforehand can help combat all three of these, and let’s be honest - it’s a lot of fun. Also, keep in mind that you’re probably still learning to FRED – it might be a good idea to insert an asteroid or nebula mission (nebulae can be disguised as the atmosphere of Gas Giants if your campaigns timeline puts you out of reach of the Shivan’s nebula). These aren’t essential, of course, but learning to use these effectively will expand your FREDding possibilities exponentially, and add just a little more buzz to your campaign. Keep in mind also that this campaign is meant as much for your learning as it is to be played. While it may not be perfectly plausible from the point of view of a single squadron, try to vary your missions a bit. A successful heavy assault mission needs to be designed very differently to, say an interceptor mission, and recon missions are a class unto themselves. You may not be able to fit all of the various mission types into your campaign structure of course, but a little bit of variation is always a good idea.<br /> <br /> -TIP – Try to avoid subspace missions your first time out, unless you have a really, really good reason to put your player there. Subspace is very difficult to get right, and has a lot of drawbacks, outlined in another Volitionwatch article. If you can do it well, that’s great, but keep in mind, it’s very, very difficult to do well<br /> <br /> -NB – making a campaign is in no way essential to learning to FRED – what’s important is the experience you’d gain working with the various environments and commands in FRED, and the interesting situations campaigns often lead to. If you don’t want to commit to what is a decent sized project (even three missions will probably see you sitting in front of a computer for twelve or so hours, plus time for testing.) then don’t. Single missions are just as effective here as a minicampaign, and in many ways even more – you don’t need to worry about linking the various missions together, nor come up with plot plausible reasons to see your player plunging into a nebula or asteroid field.<br /> <br /> ----<br /> ==Step 5 – Test, Test, Test.==<br /> <br /> Beta testing is one of the most boring parts of FREDding, and, in some ways, one of the hardest. I hate doing it myself, especially since I test roughly every 5 or 10 changes, which means I’ll generally test each mission at least a dozen times during FREDding, generally a lot more. However, there’s nothing as irritating as a poorly tested mission, and almost nothing so obvious. Everything you release should be exhaustively tested, and if possible by other people. If you’re doing a campaign, try to get it tested at both the mission by mission level and at the final product, if possible. Your testers will give you bug reports, but also on how the story's moving along, or how the speech is going. Most of these problems can be fixed with a few clicks of the mouse or a few word changes in your messages, but it’s these that can tip a good mission over the line into a great mission.<br /> <br /> Also keep in mind difficulty when Beta testing. You’ll often hear FREDders talk about balance in a mission, that elusive point where it is just enough of a challenge to get the player involved and enjoying himself without being frustratingly difficult. Balance is affected by almost everything in a mission, in varying degrees. Seemingly small things, like the orientation of a capship, or the distance a wing of fighters arrives from the heat of battle, can alter the balance as much as the more obvious things such as the players available ship and weapon loadout (Allowing your pilot to use Helioses to take out freighters is not recommended )<br /> <br /> Well done pilot - you now have all the expertise you’ll need to become a fully fledged member of the FREDding community, with a campaign release under your belt (you were planning to release, right?) and the potential to do pretty much anything. With the possible exception of BWO, there’s not a campaign out there that’d turn down applications from FREDders, or you can start your own project, large or small, and add to the FS universe that way. With the SCP and FSO there’s a myriad of new concepts and abilities coming to FRED, and, despite everything you’ll probably have done by this point, there’ll always be a lot to learn.<br /> <br /> ----<br /> =Links=<br /> <br /> Everything mentioned above, and a few other useful resources, will be listed here.<br /> <br /> [http://www.volitionwatch.com/articles/ Volitionwatch Articles Index ] Some useful articles, which, despite their age, can still be very relevant to FREDders. Pay particular attention to:<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=13 What Makes a Good Mission?]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=26 FRED and the Battle of Endor Syndrome ]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=27 Tunnel Vision: Why Subspace Mission?]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=25 The Problem With User-Created Levels]<br /> <br /> [http://www.3dap.com/hlp/hosted/fredzone FREDZone] A useful resource for FRED information.<br /> <br /> GTI Archeron by Robin Varley<br /> <br /> [http://www.fileplanet.com/dl.aspx?3dactionplanet/freespace/acheron.zip GTI Archeron by Robin Varley] - A well built light installation mod that fills a void in the FS2 Shipset.<br /> <br /> [http://www.3dap.com/hlp/hosted/scroll/download.html GVSC Imhotep from The Scroll of Atankharzim] - Vasudan science ship - another void in the FS2 shipset neatly filled.<br /> <br /> ----<br /> <br /> For any questions regarding FRED not covered by this or the other Wiki documents, try the [HLP forums|http://dynamic4.gamespy.com/~freespace/forums]. You can also contact me, Black Wolf, through a Private Message on HLP, or by emailing the_lone_black_wolf@hotmail.com</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=5_easy_steps_towards_your_FREDucation&diff=56 2005-06-07T20:38:34Z

<p>81.182.82.204: </p> <hr /> <div>=FRED Tutorial=<br /> <br /> There are lots of people in the FS community at the moment, new and old, who claim they can’t FRED. Some have made the choice voluntarily, others simply don’t know where to start, or don’t think it’s something they’d ever be able to learn. The truth is though, even if you’ve never modded or mapped a computer game in your life, you can master FRED in a relatively short time. The following five steps will hopefully help anyone aspiring to teach themselves FRED to map out their plans and ultimately come out a pro FREDder.<br /> <br /> ----<br /> ==Step 1 - Do the Walkthrough==<br /> <br /> This is the most essential part of any FREDucation. You can, and many have, go straight from a completed walkthrough mission and into a campaigns staff and churn out missions with little difficulty. The walkthrough touches on everything you'll need to know to get you started in FRED, and it's a brilliant tool. However, as V themselves admitted, it's still only an introduction to FRED - even before the SCP, people were doing things with FRED that the original coders had never even considered implementing, let alone realized they were already possible.<br /> <br /> ----<br /> ==Step 2 - Baby steps==<br /> <br /> This will be your first functioning mission. It seems a big jump, to go from the fully documented, completely pre-scripted mission of the walkthrough to a completely new, never before seen mission that comes straight out of your head. But it doesn't have to be. This mission can, and probably should, be very simple - have the player defending a stricken capship while the escape pods are prepared. This could, in theory, be done with no sexps beyond those that control the arrival and departure of the various ships in the mission. Of course, a mission this simple is not ideal, so perhaps having the aim of the mission to defend the same capship until a transport can dock to repair its engines? This requires a higher degree of sexping, though not by much. If you're feeling confident, add a twist - the repaired capship comes under attack from a pair of enemy capital ships, and have the player switch from taking out bombers to taking out turrets, while the home ship manoeuvres to escape. Or completely disregard this and do a totally different scenario. All you need to do is become confident replicating the steps you learned in the Walkthrough - things like messaging, mission goals, waypoints, AI commands - without a guide telling you precisely what you need to do.<br /> <br /> -TIP - Don't skimp on this mission - make it as complete as you can. Include a briefing and debrief, mission goals, background, check the music and title all fit - often completed missions can be adapted for use later on, no matter how simple they will appear once your FREDding skill has improved.<br /> <br /> ----<br /> ==Step 3 - Research==<br /> <br /> OK. By now, you're comfortable with what you learned in the Walkthrough, it's time to expand on your knowledge by researching what others have done. Use VPView to extract Volition missions from Root.vp and have a look at how they did certain things. There are lots of more complex things, like Knossos jumping, or having the player follow waypoints, that the walkthrough does not cover. You could also try looking at the missions from various campaigns that have been released. Things like Derelict and Warzone that had few mods often relied on inventive FREDding to add spice to their missions, and these tactics are still just as or even more valid now, despite the multitude of available mods. You’ll also want to check out the various tips and tricks that were written up way back in the day for FRED1, which are hosted on Freespacewatch. These may seem dated, but much of the core information about mission continuity and ambience remains vitally important for any FREDder.<br /> <br /> ----<br /> ==Step 4 – Linking missions together==<br /> <br /> STOP! By this point, you’re probably starting to feel confident with FRED, and you’ve probably started to get some really good ideas for campaigns you can do – big, bold, impressive campaigns that’re going to explain Capella, sort out Bosch and cure cancer. OK, I’m going to say this bluntly - Do not do this. You are not the first to have this idea, and you will not be the first to fail if you start it. That said, I do think a campaign is a good idea here. Building a campaign forces you to think about consequences, to link your missions together, to develop characters in your wingmen – all very useful traits in a FREDder. But for god’s sake, don’t try to make Inferno or BWO your first project. I recommend building a campaign, no more than 4 or 5 missions long, with no staff other than yourself, and no mods that you can’t make yourself or download already done. Hell, I’d recommend you use no mods at all, but I’d be the first to admit that the FS2 isn’t ideal for certain types of missions – FS2 has no Vasudan or light installations, a woeful selection of civilian craft, and really skimps on certain parts of the Vasudan fleet. Stuff like the GVSc Imhoteph from the Scroll of Atankharzim team, or the GTI Archeron by Robin Varley can be indispensable for certain situations. I’m not saying you need these ships, but if your campaign calls for them, I’m not saying leave them out either.<br /> <br /> There are a few things you need to think about while you build your campaign – the first is obviously the story – you need to make something that keeps the player interested, and that is believable, as well as presenting enough challenges so that it can’t be completed in five minutes. If thinking up plots isn’t your forte, then don't worry - in many cases V has done the work for you. There are plenty of referenced battles and combats, in the briefings, Command briefings, debriefings and messages used in the main campaign, where the player is told about events in the NTF war, but never experiences them, such as large parts of the Colossus’ trek through the NTF systems, or the early days of the battle of Deneb. Creating missions from these stories not only makes things easier by eliminating the need for any mods whatsoever, but also enriches the overall FS community by providing a bit of background to the story that we all know so well.<br /> <br /> Planning your missions beforehand can help combat all three of these, and let’s be honest - it’s a lot of fun. Also, keep in mind that you’re probably still learning to FRED – it might be a good idea to insert an asteroid or nebula mission (nebulae can be disguised as the atmosphere of Gas Giants if your campaigns timeline puts you out of reach of the Shivan’s nebula). These aren’t essential, of course, but learning to use these effectively will expand your FREDding possibilities exponentially, and add just a little more buzz to your campaign. Keep in mind also that this campaign is meant as much for your learning as it is to be played. While it may not be perfectly plausible from the point of view of a single squadron, try to vary your missions a bit. A successful heavy assault mission needs to be designed very differently to, say an interceptor mission, and recon missions are a class unto themselves. You may not be able to fit all of the various mission types into your campaign structure of course, but a little bit of variation is always a good idea.<br /> <br /> -TIP – Try to avoid subspace missions your first time out, unless you have a really, really good reason to put your player there. Subspace is very difficult to get right, and has a lot of drawbacks, outlined in another Volitionwatch article. If you can do it well, that’s great, but keep in mind, it’s very, very difficult to do well<br /> <br /> -NB – making a campaign is in no way essential to learning to FRED – what’s important is the experience you’d gain working with the various environments and commands in FRED, and the interesting situations campaigns often lead to. If you don’t want to commit to what is a decent sized project (even three missions will probably see you sitting in front of a computer for twelve or so hours, plus time for testing.) then don’t. Single missions are just as effective here as a minicampaign, and in many ways even more – you don’t need to worry about linking the various missions together, nor come up with plot plausible reasons to see your player plunging into a nebula or asteroid field.<br /> <br /> ----<br /> ==Step 5 – Test, Test, Test.==<br /> <br /> Beta testing is one of the most boring parts of FREDding, and, in some ways, one of the hardest. I hate doing it myself, especially since I test roughly every 5 or 10 changes, which means I’ll generally test each mission at least a dozen times during FREDding, generally a lot more. However, there’s nothing as irritating as a poorly tested mission, and almost nothing so obvious. Everything you release should be exhaustively tested, and if possible by other people. If you’re doing a campaign, try to get it tested at both the mission by mission level and at the final product, if possible. Your testers will give you bug reports, but also on how the story's moving along, or how the speech is going. Most of these problems can be fixed with a few clicks of the mouse or a few word changes in your messages, but it’s these that can tip a good mission over the line into a great mission.<br /> <br /> Also keep in mind difficulty when Beta testing. You’ll often hear FREDders talk about balance in a mission, that elusive point where it is just enough of a challenge to get the player involved and enjoying himself without being frustratingly difficult. Balance is affected by almost everything in a mission, in varying degrees. Seemingly small things, like the orientation of a capship, or the distance a wing of fighters arrives from the heat of battle, can alter the balance as much as the more obvious things such as the players available ship and weapon loadout (Allowing your pilot to use Helioses to take out freighters is not recommended )<br /> <br /> Well done pilot - you now have all the expertise you’ll need to become a fully fledged member of the FREDding community, with a campaign release under your belt (you were planning to release, right?) and the potential to do pretty much anything. With the possible exception of BWO, there’s not a campaign out there that’d turn down applications from FREDders, or you can start your own project, large or small, and add to the FS universe that way. With the SCP and FSO there’s a myriad of new concepts and abilities coming to FRED, and, despite everything you’ll probably have done by this point, there’ll always be a lot to learn.<br /> <br /> ----<br /> ===Links===<br /> <br /> Everything mentioned above, and a few other useful resources, will be listed here.<br /> <br /> [http://www.volitionwatch.com/articles/ Volitionwatch Articles Index ] Some useful articles, which, despite their age, can still be very relevant to FREDders. Pay particular attention to:<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=13 What Makes a Good Mission?]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=26 FRED and the Battle of Endor Syndrome ]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=27 Tunnel Vision: Why Subspace Mission?]<br /> * [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=25 The Problem With User-Created Levels]<br /> <br /> [http://www.3dap.com/hlp/hosted/fredzone FREDZone] A useful resource for FRED information.<br /> <br /> GTI Archeron by Robin Varley<br /> <br /> [http://www.fileplanet.com/dl.aspx?3dactionplanet/freespace/acheron.zip GTI Archeron by Robin Varley] - A well built light installation mod that fills a void in the FS2 Shipset.<br /> <br /> [http://www.3dap.com/hlp/hosted/scroll/download.html GVSC Imhotep from The Scroll of Atankharzim] - Vasudan science ship - another void in the FS2 shipset neatly filled.<br /> <br /> ----<br /> <br /> For any questions regarding FRED not covered by this or the other Wiki documents, try the [HLP forums|http://dynamic4.gamespy.com/~freespace/forums]. You can also contact me, Black Wolf, through a Private Message on HLP, or by emailing the_lone_black_wolf@hotmail.com</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Mission_design&diff=520 2005-06-07T20:35:36Z

<p>81.182.82.204: </p> <hr /> <div>&lt;br&gt;[[5 Easy steps towards your FREDucation]]<br /> &lt;br&gt;[[FRED Tips]]<br /> &lt;br&gt;[[References]]<br /> &lt;br&gt;[[Backgrounds]]<br /> &lt;br&gt;[[Plot Development]]<br /> &lt;br&gt;[[Mission Chatter]]<br /> &lt;br&gt;[[The World of SEXPs]]<br /> &lt;br&gt;[[The FRED Academy]]<br /> &lt;br&gt;[[Battle of Endor-scheme]]</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Ancients&diff=781 2005-06-07T20:08:09Z

<p>81.182.82.204: </p> <hr /> <div>=The Ancients=<br /> <br /> Several millenia ago, a proud and expansive empire reached its pinnacle. Subjugating and enslaving other advanced races, defeating all their enemies and colonizing worlds we have not even heard of, these things made them the most powerful and the only empire in the galaxy of FreeSpace. &lt;br&gt;<br /> <br /> But then, something happened what the Ancients had not been expecting and were not prepared for...<br /> <br /> The Ancients met a powerful enemy, an enemy that was the last of their foes. A foe they did not understand: the [[Shivans]]. It was commonly believed all throught their empire that the [[Shivans]] are the cosmic destroyers who have the noble task of removing their greed empire and punish them for their crimes against all living creatures. &lt;br&gt;<br /> Little is known about the war itself, but what we know is enough...<br /> <br /> The [[Shivans]] destroyed the heart and pride of the Ancients: their military fleet. Then, they bombarded their colonized planets with weapons nobody had ever seen... with weapons that are more powerful than any of theirs. It was no doubt they can only lose in this battle. The only question that remained: will we at least survive? &lt;br&gt;<br /> <br /> The answer came quickly...<br /> <br /> It did not take much time for the [[Shivans]] to reach the Ancient homeworld and stab this race into the heart. By doing so, the Cosmic Destroyers sealed the fate of their enemy. The Ancients had little hope left for survival, albeit efforts had been made. They achieved results in their efforts, but they had no way to use their knowledge against their enemy. &lt;br&gt;<br /> <br /> More precisely, this knowledge made the [[Shivans]] defeated, but they were not the Ancients who delivered that blow.<br /> <br /> They discovered the weakness in the Destroyers' defences, they found a way that could have saved their civilisation. But the Cosmic Destroyers were too powerful and when this information was discovered, it was already too late. The Ancients had been extinguished like insects and fleas. None of them survived. As far as we know...<br /> <br /> Three thousand years later, the Cosmic Destroyers returned and once again, they threatened the Galaxy. They fought their way toward the homeworlds of their enemies. Once again. It seemed they would win the war and overcome their enemies again. But the Ancients managed to pass their knowledge to the future civilizations. What they knew three millenia ago brought salvation to two other races: The [[Terrans]] and the [[Vasudans]]. &lt;br&gt;<br /> <br /> The [[Shivans]] suffered defeat. The fact that who helped the most in defeating the [[Shivans]] is the question of aspect now. Did the Ancients help these two younger races or did they finish what the ancients had been unable to? &lt;br&gt;<br /> <br /> This debate will continue until the [[Shivans]] return and complete their revenge...</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Ancients&diff=51 2005-06-07T20:07:12Z

<p>81.182.82.204: </p> <hr /> <div>=The Ancients=<br /> <br /> Several millenia ago, a proud and expansive empire reached its pinnacle. Subjugating and enslaving other advanced races, defeating all their enemies and colonizing worlds we have not even heard of, these things made them the most powerful and the only empire in the galaxy of FreeSpace. &lt;br&gt;<br /> <br /> But then, something happened what the Ancients had not been expecting and were not prepared for...<br /> <br /> The Ancients met a powerful enemy, an enemy that was the last of their foes. A foe they did not understand: the [[Shivans]]. It was commonly believed all throught their empire that the [[Shivans]] are the cosmic destroyers who have the noble task of removing their greed empire and punish them for their crimes against all living creatures. &lt;br&gt;<br /> Little is known about the war itself, but what we know is enough...<br /> <br /> The [[Shivans]] destroyed the heart and pride of the Ancients: their military fleet. Then, they bombarded their colonized planets with weapons nobody had ever seen... with weapons that are more powerful than any of theirs. It was no doubt they can only lose in this battle. The only question that remained: will we at least survive? &lt;br&gt;<br /> <br /> The answer came quickly...<br /> <br /> It did not take much time for the [[Shivans]] to reach the Ancient homeworld and stab this race into the heart. By doing so, the Cosmic Destroyers sealed the fate of their enemy. The Ancients had little hope left for survival, albeit efforts had been made. They achieved results in their efforts, but they had no way to use their knowledge against their enemy. &lt;br&gt;<br /> <br /> More precisely, this knowledge made the [[Shivans]] defeated, but they were not the Ancients who delivered that blow.<br /> <br /> They discovered the weakness in the Destroyers' defences, they found a way that could have saved their civilisation. But the Cosmic Destroyers were too powerful and when this information was discovered, it was already too late. The Ancients had been extinguished like insects and fleas. None of them survived. As far as we know...<br /> <br /> Three thousand years later, the Cosmic Destroyers returned and once again, they threatened the Galaxy. They fought their way toward the homeworlds of their enemies. Once again. It seemed they would win the war and overcome their enemies again. But the Ancients managed to pass their knowledge to the future civilizations. What they knew three millenia ago brought salvation to two other races: The [[Terrans]] and the [[Vasudans]]. &lt;br&gt;<br /> <br /> The [[Shivans]] suffered defeat. The fact that who helped the most in defeating the [Shivans] is the question of aspect now. Did the Ancients help these two younger races or did they finish what the ancients had been unable to? &lt;br&gt;<br /> <br /> This debate will continue until the [[Shivans]] return and complete their revenge...</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Shivans&diff=108 2005-06-07T20:04:54Z

<p>81.182.82.204: </p> <hr /> <div>=Shivans=<br /> <br /> ==Physiognomy==<br /> [http://freespace.volitionwatch.com/techfs/jeremy/shivans.jpg]<br /> Shivans have multiple eyes, some of which seem to have the function of compound eyes, not unlike some varieties of insects. Shivans also have five legs, and can run equally well over a floor or over a ceiling. It has been hypothesized that Shivans may have spent their evolutionary process in a zero-gravity environment. Each Shivan leg ends in a very strong claw, capable of crushing even the sturdiest of known alloys. Parts of their thorax seem to act as compartments, such as ones that might be found on a space suit. It has been suggested that what we have actually seen have been either robots or organic creatures in some sort of exo-skeleton. However, we have, at present, no reason to support either hypothesis.<br /> <br /> Their insect like carapace does not appear original to the creature's physiognomy, suggesting the Shivans are a cybernetic fusion of biology and technology. The integrated plasma weapon also exhibits properties of an organic artificial fusion. The weapon may be a kind of focusing device powered by the energy of the being itself, though this point is the subject of heated cotroversy. These details are cited as evidence that the Shivans could not have evolved as the Terran or Vasudan species had, but that they were likely constructed by another entity.<br /> <br /> Only a handful of Shivans have ever been captured, and all research on live specimens ended with the GTI's Hades rebellion in 2336. The results of these studies remain highly classified.<br /> <br /> ==History==<br /> Despite what information we've been able to obtain, Shivans still remain, on many levels, an enigma to both the [[Terrans]] and the [[Vasudans]]. Their origin and their destination remain unknown. While many have offered up possible explanations as to why the Shivans seem focused on the destruction of all other sentient species, we still do not know why they seem bent on total xenocide.<br /> <br /> Though the Shivans are obviously xenocidal, their motives and origins have yet to be determined. According to Ancient artifacts, the Shivans seem to possess some kind of sensitivity to subspace disturbances. We do not know if the Shivans returned to this corner of the galaxy by chance, by cycle or pattern, or by their detection of Terran-Vasudan subspace travel.<br /> <br /> ==Culture==<br /> Xenobiologists know very little about Shivan society. A leading hypothesis is the hive mind theory, arguing that Shivan society is broken down in specialized functions driven by a collective intelligence. The most convincing evidence supporting this theory is the behavior of Shivan forces following the destruction of the Lucifer, the turning point of [[The Great War]]. Other experts caution against attributing insectoid properties to the Shivans, regardless of their appearance and behavior. Shivan communication seems to occur in the electromagnetic spectrum; [[Admiral Aken Bosch]]'s ETAK project was successful in decoding their transmissions, but all data concerning that project has been classified at the highest level.<br /> <br /> ==Technology==<br /> Shivan technology has proven baffling for both Terran and Vasudan scientists. Although their weapons and technology by necessity obey the same physical laws, the systems of Shivan craft seem to be fully integrated with the pilot's biology, making it difficult-but still possible-to use their spacecraft for espionage. Additionally, reverse-engineering Shivan technology has led to tremendous advances in shielding, beam weaponry, and other weapons systems. Shivans seem to depend more on primary weapons than secondaries, evidenced by their bombers' low payload capacity. Shivans also rely on their heavy shielding and use little armor plating on their fighters.</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Shivans&diff=50 2005-06-07T20:04:32Z

<p>81.182.82.204: </p> <hr /> <div>=Shivans=<br /> <br /> ==PHYSIOGNOMY==<br /> [http://freespace.volitionwatch.com/techfs/jeremy/shivans.jpg]<br /> Shivans have multiple eyes, some of which seem to have the function of compound eyes, not unlike some varieties of insects. Shivans also have five legs, and can run equally well over a floor or over a ceiling. It has been hypothesized that Shivans may have spent their evolutionary process in a zero-gravity environment. Each Shivan leg ends in a very strong claw, capable of crushing even the sturdiest of known alloys. Parts of their thorax seem to act as compartments, such as ones that might be found on a space suit. It has been suggested that what we have actually seen have been either robots or organic creatures in some sort of exo-skeleton. However, we have, at present, no reason to support either hypothesis.<br /> <br /> Their insect like carapace does not appear original to the creature's physiognomy, suggesting the Shivans are a cybernetic fusion of biology and technology. The integrated plasma weapon also exhibits properties of an organic artificial fusion. The weapon may be a kind of focusing device powered by the energy of the being itself, though this point is the subject of heated cotroversy. These details are cited as evidence that the Shivans could not have evolved as the Terran or Vasudan species had, but that they were likely constructed by another entity.<br /> <br /> Only a handful of Shivans have ever been captured, and all research on live specimens ended with the GTI's Hades rebellion in 2336. The results of these studies remain highly classified.<br /> <br /> ==History==<br /> Despite what information we've been able to obtain, Shivans still remain, on many levels, an enigma to both the [[Terrans]] and the [[Vasudans]]. Their origin and their destination remain unknown. While many have offered up possible explanations as to why the Shivans seem focused on the destruction of all other sentient species, we still do not know why they seem bent on total xenocide.<br /> <br /> Though the Shivans are obviously xenocidal, their motives and origins have yet to be determined. According to Ancient artifacts, the Shivans seem to possess some kind of sensitivity to subspace disturbances. We do not know if the Shivans returned to this corner of the galaxy by chance, by cycle or pattern, or by their detection of Terran-Vasudan subspace travel.<br /> <br /> ==Culture==<br /> Xenobiologists know very little about Shivan society. A leading hypothesis is the hive mind theory, arguing that Shivan society is broken down in specialized functions driven by a collective intelligence. The most convincing evidence supporting this theory is the behavior of Shivan forces following the destruction of the Lucifer, the turning point of [[The Great War]]. Other experts caution against attributing insectoid properties to the Shivans, regardless of their appearance and behavior. Shivan communication seems to occur in the electromagnetic spectrum; [[Admiral Aken Bosch]]'s ETAK project was successful in decoding their transmissions, but all data concerning that project has been classified at the highest level.<br /> <br /> ==Technology==<br /> Shivan technology has proven baffling for both Terran and Vasudan scientists. Although their weapons and technology by necessity obey the same physical laws, the systems of Shivan craft seem to be fully integrated with the pilot's biology, making it difficult-but still possible-to use their spacecraft for espionage. Additionally, reverse-engineering Shivan technology has led to tremendous advances in shielding, beam weaponry, and other weapons systems. Shivans seem to depend more on primary weapons than secondaries, evidenced by their bombers' low payload capacity. Shivans also rely on their heavy shielding and use little armor plating on their fighters.</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Terrans&diff=105 2005-06-07T20:02:58Z

<p>81.182.82.204: </p> <hr /> <div>=Terrans=<br /> <br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran1.jpg]<br /> ==Physiognomy==<br /> Terrans, or humans, are bipedal, carbon-based life forms that evolved from primates several thousand years ago on the third planet in the [Sol] system. They have an internal skeleton that supports and protects all their internal organs, musculature, and external skin. Compared to Vasudans or Shivans, or even many terrestrial animals, humans are physically weak, able to lift only slightly more than their own body weight. Humans have circumvented this weakness by using their powerful brains to develop tools that give them advantages over their environments, and by reasoning to outsmart their competitors. This intelligence and versatility has given the Terran species the flexibility it needed to adapt to the various threats it has faced, and allowed Terrans to evolve from tribal, nomadic primates (not entirely unlike their progenitors) to a spacefaring race.<br /> <br /> ==HISTORY==<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran2.jpg] The Terran homeworld of Earth is the third planet in the Sol system, and is well suited to life. Vast oceans cover two thirds of the planet, and a protective atmosphere guards the planet from radiation. The landscape varies between grassy plains, lush forests, frozen wastes and barren deserts. Terran history has been one of turmoil and strife, due to the conflicting instincts of social grouping and independence.<br /> <br /> The first great age of Earth was that of Antiquity, circa 200 BCE. The Roman Empire, which conquered much of the continent of Europe, was the ancestor of much of present Terran language and culture. The ancient Greeks were the greatest philosophers, scientists and artisans of their day, and most Terran starships were later named after the gods of this culture. Ancient Egyptians formed the basis for Egyptian nomenclature, as their culture thrived in the desert of northern Africa. These were the first nation-states on which Terran government was ultimately based.<br /> <br /> The fall of Rome by barbarian invaders circa 500 CE marked the beginning of the Dark Ages, a time where most of the grandeur of Rome was lost. Civilizations such as the Mongols, the Aztecs, and the Chinese rose and declined. The fragmented states of Europe fought constantly amongst themselves, and developed newer and deadlier technologies with which to defeat their enemies.<br /> <br /> Islamic scientists preserved most of the knowledge of Greece and Rome that was rediscovered in the Renaissance over one thousand years later. Transportation during this time grew to the point where global travel became possible. During the 17th and 18th centuries Europeans discovered, and frequently annihilated, other cultures across the planet in other continents. Colonists settled and prospered over the planet, and the first truly global empire was the British Empire during the 19th century.<br /> <br /> The 20th century saw great sweeping technological advancements that made instantaneous communication possible over the entire planet, but it also saw the first incidences of global warfare. The most profound of these wars took place in the middle of the century and involved almost every nation on the planet. Over 20 million Terrans were killed in the Second World War, and terrible weapons, including nuclear weapons, were developed and used. Out of this drive to overcome the enemy came the First Space Age, with the first orbiting satellites and lunar landings made. However, the collapse of one global power brought a period of relative peace up to the end of the century.<br /> <br /> The 21st century began with a new technology, the Internet. With this any Terran could tap into the network of computers and their users all over the planet and discover any information they might want. This tool was used and abused in various ways to inform and educate the populous at an increasing rate. By the end of the century, the vast majority of collected Terran knowledge had been spread throughout the globe, and most of the economic and health problems that had plagued humanity since its earliest days were solved, adn the nation-state evolved into a global-state.<br /> <br /> By the 22nd century, Earth's population had exceeded 10 billion. Despite the advancements, Earth could no longer support the needs of its people. Development of the Lunar and Martian colonies was stepped up, and the Second Space Age began. Huge terraforming processes were began and artificial gravity space stations were constructed, with most nations uniting in a common endeavor to save humanity. The population of Mars and Luna grew to the thousands, then the millions. With space travel, the Terran species furthered its growth, both in material ways and in immaterial, philosophical ways.<br /> <br /> Exploration of the outer reaches of the Solar system was made a priority in the 23rd century, after the discovery of primitive life forms on the moon of Europa. During the expansive colonization projects, larger and larger space stations and starships grew more efficient. By the latter part of the century mining operations in the asteroid belt beyond Mars and on the moons of Jupiter and Saturn was commonplace, but the speed of light limited Terran exploration. Not until the discovery of Subspace in 2316 did the galaxy open up for real colonization, conquest, and exploitation. The system-state evolved into the inter-system state, and with the formation of the Galactic Terran Alliance, a galactic-state.<br /> <br /> ==CULTURE==<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran3.jpg] Terran culture is founded on the premise of social equality of all Terrans. After witnessing historical atrocities performed by humans solely on the basis that a physical trait or heretige made them somehow inferior, Terran governments forcibly induced human psychological conditioning in the early 22nd century. While unifying the Terran culture as a whole, this also had the unwanted side effects of arrogance and hostility toward alien races.<br /> <br /> Terrans are permitted to choose their own careers, and do what they enjoy within the limits of safety. Customs vary widely depending on the original nationality of the individual. Clothing is always worn and is frequently stylized depending on the occasion. Terran language is based on American English, which was a homogenization of several older languages. Religion is entirely dependant on the individual, with little government interference.<br /> <br /> While the individual human is usually polite, reasonable, and educated, as a group they can often exhibit irrational behavior. Politicians and dictators in the past have exploited these traits for their own gain.<br /> <br /> ==TECHNOLOGY==<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran4.jpg] Terran ship design has not far departed from the utilitarian cylindrical segments and boxes that made up the first Terran spaceships and space stations. Dull greys and beiges were hallmarks of Terran design through the 24th century. They were utilitarian and cheap to produce, with embellishment limited to stripes of paint and squadron insignia. Despite this, Terran design aesthetics have held to the military-industrial themes. Legendary warships like the Apollo, Medusa, and Orion are considered by many to represent the finest in unadulterated Terran design. The familiar lines and sturdy blocks are reassuring reminders of the durability and power of the ships. After Vasudan and Shivan technologies began being implemented, Terran design took a softer turn. Fighters and bombers became the hot-rods of their generation, with the sleek Hercules Mark II, Artemis, and Deimos adorning many a Terran teenager's wall.<br /> <br /> Weaponry on Terran starships is very diverse, reflecting both Terran adaptability for different circumstances and the philosophy that pilots should be able to customize their loadout to their own tastes. All-purpose weapons such as the Subach HL-7, Avenger, and Prometheus are complemented by weapons that have a special effect upon their targets, like the kinetic effect of the Flail rifle and the energy-draining abilities of the Lamprey. Guns with ammunition were used throughout the Unification War until the pulse cannons now in use were developed. Early energy-based weapons were distinctly gaseous in their aural signatures and visual identifications, due to the use of gases like argon and nitrogen used to intensify the laser pulses. Later weaponry used during the second Shivan conflict put more of an emphasis on plasma and electromagnetic weapons, such as the Circe.<br /> <br /> Terran missile design is mostly dependant on brute force, rather than finesse. Heavy ordinance like the Phoenix line of heavy missiles and the Cyclops torpedo annihilate large targets, as Terrans prefer to use their primary weapons against smaller, faster targets. Many of the lighter missiles, such as the Interceptor, used by Terran fighters were only made possible through Vasudan improvements in aspect lock times and engine speeds.<br /> <br /> The heavy photon beam cannons now mounted on all Terran warships were initially reverse-engineered from the superweapons mounted on the Lucifer in 2335 by the GTI engineers working on Project Hades. The ill-fated rebellion of these engineers the next year in their bid to overthrow the GTA led to the classification of the weaponry for several years. Once functional beam weaponry was proven to be practical, reliable, and superbly useful, a Vasudan variant was developed for deployment on the Sobek class of corvettes. These 'slash' beams maximized the spread of the beam fire on a wide arc across the target's hull, increasing the chances of disabling subsystems and turrets. Both Slash beams and Line-of-Sight (LOS) beams are now standard on all Terran warships.</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Terrans&diff=49 2005-06-07T20:02:38Z

<p>81.182.82.204: </p> <hr /> <div>=Terrans=<br /> <br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran1.jpg]<br /> =Physiognomy=<br /> Terrans, or humans, are bipedal, carbon-based life forms that evolved from primates several thousand years ago on the third planet in the [Sol] system. They have an internal skeleton that supports and protects all their internal organs, musculature, and external skin. Compared to Vasudans or Shivans, or even many terrestrial animals, humans are physically weak, able to lift only slightly more than their own body weight. Humans have circumvented this weakness by using their powerful brains to develop tools that give them advantages over their environments, and by reasoning to outsmart their competitors. This intelligence and versatility has given the Terran species the flexibility it needed to adapt to the various threats it has faced, and allowed Terrans to evolve from tribal, nomadic primates (not entirely unlike their progenitors) to a spacefaring race.<br /> <br /> ==HISTORY==<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran2.jpg] The Terran homeworld of Earth is the third planet in the Sol system, and is well suited to life. Vast oceans cover two thirds of the planet, and a protective atmosphere guards the planet from radiation. The landscape varies between grassy plains, lush forests, frozen wastes and barren deserts. Terran history has been one of turmoil and strife, due to the conflicting instincts of social grouping and independence.<br /> <br /> The first great age of Earth was that of Antiquity, circa 200 BCE. The Roman Empire, which conquered much of the continent of Europe, was the ancestor of much of present Terran language and culture. The ancient Greeks were the greatest philosophers, scientists and artisans of their day, and most Terran starships were later named after the gods of this culture. Ancient Egyptians formed the basis for Egyptian nomenclature, as their culture thrived in the desert of northern Africa. These were the first nation-states on which Terran government was ultimately based.<br /> <br /> The fall of Rome by barbarian invaders circa 500 CE marked the beginning of the Dark Ages, a time where most of the grandeur of Rome was lost. Civilizations such as the Mongols, the Aztecs, and the Chinese rose and declined. The fragmented states of Europe fought constantly amongst themselves, and developed newer and deadlier technologies with which to defeat their enemies.<br /> <br /> Islamic scientists preserved most of the knowledge of Greece and Rome that was rediscovered in the Renaissance over one thousand years later. Transportation during this time grew to the point where global travel became possible. During the 17th and 18th centuries Europeans discovered, and frequently annihilated, other cultures across the planet in other continents. Colonists settled and prospered over the planet, and the first truly global empire was the British Empire during the 19th century.<br /> <br /> The 20th century saw great sweeping technological advancements that made instantaneous communication possible over the entire planet, but it also saw the first incidences of global warfare. The most profound of these wars took place in the middle of the century and involved almost every nation on the planet. Over 20 million Terrans were killed in the Second World War, and terrible weapons, including nuclear weapons, were developed and used. Out of this drive to overcome the enemy came the First Space Age, with the first orbiting satellites and lunar landings made. However, the collapse of one global power brought a period of relative peace up to the end of the century.<br /> <br /> The 21st century began with a new technology, the Internet. With this any Terran could tap into the network of computers and their users all over the planet and discover any information they might want. This tool was used and abused in various ways to inform and educate the populous at an increasing rate. By the end of the century, the vast majority of collected Terran knowledge had been spread throughout the globe, and most of the economic and health problems that had plagued humanity since its earliest days were solved, adn the nation-state evolved into a global-state.<br /> <br /> By the 22nd century, Earth's population had exceeded 10 billion. Despite the advancements, Earth could no longer support the needs of its people. Development of the Lunar and Martian colonies was stepped up, and the Second Space Age began. Huge terraforming processes were began and artificial gravity space stations were constructed, with most nations uniting in a common endeavor to save humanity. The population of Mars and Luna grew to the thousands, then the millions. With space travel, the Terran species furthered its growth, both in material ways and in immaterial, philosophical ways.<br /> <br /> Exploration of the outer reaches of the Solar system was made a priority in the 23rd century, after the discovery of primitive life forms on the moon of Europa. During the expansive colonization projects, larger and larger space stations and starships grew more efficient. By the latter part of the century mining operations in the asteroid belt beyond Mars and on the moons of Jupiter and Saturn was commonplace, but the speed of light limited Terran exploration. Not until the discovery of Subspace in 2316 did the galaxy open up for real colonization, conquest, and exploitation. The system-state evolved into the inter-system state, and with the formation of the Galactic Terran Alliance, a galactic-state.<br /> <br /> ==CULTURE==<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran3.jpg] Terran culture is founded on the premise of social equality of all Terrans. After witnessing historical atrocities performed by humans solely on the basis that a physical trait or heretige made them somehow inferior, Terran governments forcibly induced human psychological conditioning in the early 22nd century. While unifying the Terran culture as a whole, this also had the unwanted side effects of arrogance and hostility toward alien races.<br /> <br /> Terrans are permitted to choose their own careers, and do what they enjoy within the limits of safety. Customs vary widely depending on the original nationality of the individual. Clothing is always worn and is frequently stylized depending on the occasion. Terran language is based on American English, which was a homogenization of several older languages. Religion is entirely dependant on the individual, with little government interference.<br /> <br /> While the individual human is usually polite, reasonable, and educated, as a group they can often exhibit irrational behavior. Politicians and dictators in the past have exploited these traits for their own gain.<br /> <br /> ==TECHNOLOGY==<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran4.jpg] Terran ship design has not far departed from the utilitarian cylindrical segments and boxes that made up the first Terran spaceships and space stations. Dull greys and beiges were hallmarks of Terran design through the 24th century. They were utilitarian and cheap to produce, with embellishment limited to stripes of paint and squadron insignia. Despite this, Terran design aesthetics have held to the military-industrial themes. Legendary warships like the Apollo, Medusa, and Orion are considered by many to represent the finest in unadulterated Terran design. The familiar lines and sturdy blocks are reassuring reminders of the durability and power of the ships. After Vasudan and Shivan technologies began being implemented, Terran design took a softer turn. Fighters and bombers became the hot-rods of their generation, with the sleek Hercules Mark II, Artemis, and Deimos adorning many a Terran teenager's wall.<br /> <br /> Weaponry on Terran starships is very diverse, reflecting both Terran adaptability for different circumstances and the philosophy that pilots should be able to customize their loadout to their own tastes. All-purpose weapons such as the Subach HL-7, Avenger, and Prometheus are complemented by weapons that have a special effect upon their targets, like the kinetic effect of the Flail rifle and the energy-draining abilities of the Lamprey. Guns with ammunition were used throughout the Unification War until the pulse cannons now in use were developed. Early energy-based weapons were distinctly gaseous in their aural signatures and visual identifications, due to the use of gases like argon and nitrogen used to intensify the laser pulses. Later weaponry used during the second Shivan conflict put more of an emphasis on plasma and electromagnetic weapons, such as the Circe.<br /> <br /> Terran missile design is mostly dependant on brute force, rather than finesse. Heavy ordinance like the Phoenix line of heavy missiles and the Cyclops torpedo annihilate large targets, as Terrans prefer to use their primary weapons against smaller, faster targets. Many of the lighter missiles, such as the Interceptor, used by Terran fighters were only made possible through Vasudan improvements in aspect lock times and engine speeds.<br /> <br /> The heavy photon beam cannons now mounted on all Terran warships were initially reverse-engineered from the superweapons mounted on the Lucifer in 2335 by the GTI engineers working on Project Hades. The ill-fated rebellion of these engineers the next year in their bid to overthrow the GTA led to the classification of the weaponry for several years. Once functional beam weaponry was proven to be practical, reliable, and superbly useful, a Vasudan variant was developed for deployment on the Sobek class of corvettes. These 'slash' beams maximized the spread of the beam fire on a wide arc across the target's hull, increasing the chances of disabling subsystems and turrets. Both Slash beams and Line-of-Sight (LOS) beams are now standard on all Terran warships.</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Vasudans&diff=106 2005-06-07T20:01:41Z

<p>81.182.82.204: </p> <hr /> <div>=Vasudans=<br /> <br /> ==Physiognonmy==<br /> [http://freespace.volitionwatch.com/techfs/jeremy/vasudans.jpg]<br /> Vasudans, much like [[Terrans]], are carbon based bipeds, standing upright with their two arms and hands used to manipulate tools. These similarities have done much to heal Terran-Vasudan relations and share technologies based on relative compatibility. Usually standing at least two meters tall, Vasudans have brown, mottled skin, powerful muscles and a durable biological system to help them withstand starvation and drought.<br /> <br /> ==History==<br /> Vasudans originate on the fourth planet of the Vasuda Prime system, the only planet in that system that is capable of supporting life. The fourth planet of the Vasuda Prime system (also known as Vasuda Prime) is a relatively hostile world. Both of the twin continents of Vasuda Prime are almost entirely desert, and most of the above-ground water is, even by Vasudan standards, undrinkable. In order to adapt to these surroundings, Vasudans developed quite rapidly.<br /> <br /> ==Culture==<br /> The Vasudans are a civilization of philosophers, artists, and scholars. They immerse themselves in the teachings of those who came before them, perceiving history not as a linear chronology of events but as a space inhabited by both the living and the dead.<br /> <br /> Vasudan society is complex and filled with peril for the outsider ignorant of their culture. Vasudans have a range of social tests and protocols, such as The Conversation. A Terran mishandling of The Conversation is presumed to be one of the major causes of [The 14-Year War]. Prior to the ascension of [Khonsu II], The Vasudan government was parliamentary in nature, presided over by the Imperial family and the Ambassadors, who are quasi-royal go-betweens for the Parliament and the Imperium.<br /> <br /> To the Terran outsider, Vasudan society appears convoluted and ritualistic. The Vasudans themselves may seem arrogant, treacherous, and superstitious. On the other hand, Vasudans tend to view Terrans as aggressive, paranoid, and stupid. Thirty years of peaceful interaction between Terrans and Vasudans has helped to deconstruct these stereotypes.<br /> <br /> The crowning achievement of the Vasudan civilization is its language. For the average Terran, the formalities governing its usage are beyond comprehension. Syntax and vocabulary are dictated by such factors as the speaker's age, rank, and caste, the time of day and the phase of the Vasudan calendar, and the relative spatial position of the speaker to the Emperor. This is further compounded by the existence of several alphabets, dozens of verb tenses, and thousands of dialects. A translation device is standard on all GTVA communications systems, enabling Terrans and Vasudans to understand each other.<br /> <br /> ==Technology==<br /> Vasudan space exploration has been driven primarily by the need to find planets capable of sustaining their species. As resources on Vasuda Prime have diminished, the drive to colonize has intensified among Vasudans in recent decades.<br /> <br /> Because the Vasudan homeworld was primarily desert, the Terrans used Egyptian names to designate Vasudan warships during the Terran-Vasudan War and the Great War. After the defeat of the Shivans, the Vasudans insisted on maintaining this convention. The Emperor strongly identified with the history of Ancient Egypt, particularly the longevity of its civilization. Following their Emperor's example, Vasudans will take on what they call a Terran name from the myths and history of Ancient Egypt.</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Terrans&diff=48 2005-06-07T20:00:26Z

<p>81.182.82.204: </p> <hr /> <div>==Terrans==<br /> <br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran1.jpg]<br /> =Physiognomy=<br /> Terrans, or humans, are bipedal, carbon-based life forms that evolved from primates several thousand years ago on the third planet in the [Sol] system. They have an internal skeleton that supports and protects all their internal organs, musculature, and external skin. Compared to Vasudans or Shivans, or even many terrestrial animals, humans are physically weak, able to lift only slightly more than their own body weight. Humans have circumvented this weakness by using their powerful brains to develop tools that give them advantages over their environments, and by reasoning to outsmart their competitors. This intelligence and versatility has given the Terran species the flexibility it needed to adapt to the various threats it has faced, and allowed Terrans to evolve from tribal, nomadic primates (not entirely unlike their progenitors) to a spacefaring race.<br /> <br /> =HISTORY=<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran2.jpg] The Terran homeworld of Earth is the third planet in the Sol system, and is well suited to life. Vast oceans cover two thirds of the planet, and a protective atmosphere guards the planet from radiation. The landscape varies between grassy plains, lush forests, frozen wastes and barren deserts. Terran history has been one of turmoil and strife, due to the conflicting instincts of social grouping and independence.<br /> <br /> The first great age of Earth was that of Antiquity, circa 200 BCE. The Roman Empire, which conquered much of the continent of Europe, was the ancestor of much of present Terran language and culture. The ancient Greeks were the greatest philosophers, scientists and artisans of their day, and most Terran starships were later named after the gods of this culture. Ancient Egyptians formed the basis for Egyptian nomenclature, as their culture thrived in the desert of northern Africa. These were the first nation-states on which Terran government was ultimately based.<br /> <br /> The fall of Rome by barbarian invaders circa 500 CE marked the beginning of the Dark Ages, a time where most of the grandeur of Rome was lost. Civilizations such as the Mongols, the Aztecs, and the Chinese rose and declined. The fragmented states of Europe fought constantly amongst themselves, and developed newer and deadlier technologies with which to defeat their enemies.<br /> <br /> Islamic scientists preserved most of the knowledge of Greece and Rome that was rediscovered in the Renaissance over one thousand years later. Transportation during this time grew to the point where global travel became possible. During the 17th and 18th centuries Europeans discovered, and frequently annihilated, other cultures across the planet in other continents. Colonists settled and prospered over the planet, and the first truly global empire was the British Empire during the 19th century.<br /> <br /> The 20th century saw great sweeping technological advancements that made instantaneous communication possible over the entire planet, but it also saw the first incidences of global warfare. The most profound of these wars took place in the middle of the century and involved almost every nation on the planet. Over 20 million Terrans were killed in the Second World War, and terrible weapons, including nuclear weapons, were developed and used. Out of this drive to overcome the enemy came the First Space Age, with the first orbiting satellites and lunar landings made. However, the collapse of one global power brought a period of relative peace up to the end of the century.<br /> <br /> The 21st century began with a new technology, the Internet. With this any Terran could tap into the network of computers and their users all over the planet and discover any information they might want. This tool was used and abused in various ways to inform and educate the populous at an increasing rate. By the end of the century, the vast majority of collected Terran knowledge had been spread throughout the globe, and most of the economic and health problems that had plagued humanity since its earliest days were solved, adn the nation-state evolved into a global-state.<br /> <br /> By the 22nd century, Earth's population had exceeded 10 billion. Despite the advancements, Earth could no longer support the needs of its people. Development of the Lunar and Martian colonies was stepped up, and the Second Space Age began. Huge terraforming processes were began and artificial gravity space stations were constructed, with most nations uniting in a common endeavor to save humanity. The population of Mars and Luna grew to the thousands, then the millions. With space travel, the Terran species furthered its growth, both in material ways and in immaterial, philosophical ways.<br /> <br /> Exploration of the outer reaches of the Solar system was made a priority in the 23rd century, after the discovery of primitive life forms on the moon of Europa. During the expansive colonization projects, larger and larger space stations and starships grew more efficient. By the latter part of the century mining operations in the asteroid belt beyond Mars and on the moons of Jupiter and Saturn was commonplace, but the speed of light limited Terran exploration. Not until the discovery of Subspace in 2316 did the galaxy open up for real colonization, conquest, and exploitation. The system-state evolved into the inter-system state, and with the formation of the Galactic Terran Alliance, a galactic-state.<br /> <br /> =CULTURE=<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran3.jpg] Terran culture is founded on the premise of social equality of all Terrans. After witnessing historical atrocities performed by humans solely on the basis that a physical trait or heretige made them somehow inferior, Terran governments forcibly induced human psychological conditioning in the early 22nd century. While unifying the Terran culture as a whole, this also had the unwanted side effects of arrogance and hostility toward alien races.<br /> <br /> Terrans are permitted to choose their own careers, and do what they enjoy within the limits of safety. Customs vary widely depending on the original nationality of the individual. Clothing is always worn and is frequently stylized depending on the occasion. Terran language is based on American English, which was a homogenization of several older languages. Religion is entirely dependant on the individual, with little government interference.<br /> <br /> While the individual human is usually polite, reasonable, and educated, as a group they can often exhibit irrational behavior. Politicians and dictators in the past have exploited these traits for their own gain.<br /> <br /> =TECHNOLOGY=<br /> [http://www.3dap.com/hlp/hosted/fsurp/database/images/terran4.jpg] Terran ship design has not far departed from the utilitarian cylindrical segments and boxes that made up the first Terran spaceships and space stations. Dull greys and beiges were hallmarks of Terran design through the 24th century. They were utilitarian and cheap to produce, with embellishment limited to stripes of paint and squadron insignia. Despite this, Terran design aesthetics have held to the military-industrial themes. Legendary warships like the Apollo, Medusa, and Orion are considered by many to represent the finest in unadulterated Terran design. The familiar lines and sturdy blocks are reassuring reminders of the durability and power of the ships. After Vasudan and Shivan technologies began being implemented, Terran design took a softer turn. Fighters and bombers became the hot-rods of their generation, with the sleek Hercules Mark II, Artemis, and Deimos adorning many a Terran teenager's wall.<br /> <br /> Weaponry on Terran starships is very diverse, reflecting both Terran adaptability for different circumstances and the philosophy that pilots should be able to customize their loadout to their own tastes. All-purpose weapons such as the Subach HL-7, Avenger, and Prometheus are complemented by weapons that have a special effect upon their targets, like the kinetic effect of the Flail rifle and the energy-draining abilities of the Lamprey. Guns with ammunition were used throughout the Unification War until the pulse cannons now in use were developed. Early energy-based weapons were distinctly gaseous in their aural signatures and visual identifications, due to the use of gases like argon and nitrogen used to intensify the laser pulses. Later weaponry used during the second Shivan conflict put more of an emphasis on plasma and electromagnetic weapons, such as the Circe.<br /> <br /> Terran missile design is mostly dependant on brute force, rather than finesse. Heavy ordinance like the Phoenix line of heavy missiles and the Cyclops torpedo annihilate large targets, as Terrans prefer to use their primary weapons against smaller, faster targets. Many of the lighter missiles, such as the Interceptor, used by Terran fighters were only made possible through Vasudan improvements in aspect lock times and engine speeds.<br /> <br /> The heavy photon beam cannons now mounted on all Terran warships were initially reverse-engineered from the superweapons mounted on the Lucifer in 2335 by the GTI engineers working on Project Hades. The ill-fated rebellion of these engineers the next year in their bid to overthrow the GTA led to the classification of the weaponry for several years. Once functional beam weaponry was proven to be practical, reliable, and superbly useful, a Vasudan variant was developed for deployment on the Sobek class of corvettes. These 'slash' beams maximized the spread of the beam fire on a wide arc across the target's hull, increasing the chances of disabling subsystems and turrets. Both Slash beams and Line-of-Sight (LOS) beams are now standard on all Terran warships.</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Species&diff=93 2005-06-07T19:59:39Z

<p>81.182.82.204: </p> <hr /> <div>==SPECIES==<br /> [[Terrans]]&lt;br&gt;<br /> [[Vasudans]]&lt;br&gt;<br /> [[Shivans]]&lt;br&gt;<br /> [[Ancients]]&lt;br&gt;</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Corporations&diff=219 2005-06-07T19:56:41Z

<p>81.182.82.204: Non-canon info excluded</p> <hr /> <div>==Corporaions of the Freespace Universe==<br /> Credit to Galemp for most of this, based on canon information<br /> <br /> ----<br /> <br /> =Terran contractors=<br /> <br /> &lt;b&gt;Triton Dynamics&lt;/b&gt;<br /> <br /> &lt;i&gt;GTF Ulysses, GTF Erinyes, SF Mara (terrans), GTS Hygeia, GTFr Triton, GTI Ganymede, GTD Hades, GTCv Deimos, UD-8 Kayser, GTM-31 Disruptor Missile&lt;/i&gt;<br /> <br /> Triton Dynamics was the second-largest contractor of the Great War, a wholly-owned subsidiary of Galactic Terran Intelligence Research and Development. Triton oversaw the design of many prototypes and advanced fighters, including the Ulysses fighter, Disruptor cannon and Stiletto missile, and was privileged to refit the captured Shivan Dragon fighter. Triton is the without question the most innovative and adaptive company around, renowned for its ability to make things work. The new Erinyes fighter, for example, can carry almost any primary or secondary weapon in its large weapon banks, and Triton adapts Vasudan and even Shivan technologies with ease. Triton Dynamics’ claim to infamy is its large part in the design and construction of the GTD Hades in Delta Serpentis. After the GTI rebellion was ended in 2336 and the collapse of the GTA, Triton became an independent corporation and is now a respectable manufacturer of both military and civilian designs.<br /> <br /> &lt;b&gt;Subach-Innes&lt;/b&gt;<br /> <br /> &lt;i&gt;Subach HL-7,GTM-12 Cyclops, GTFr Poseidon, GTT Argo&lt;/i&gt;<br /> <br /> The small-arms and land vehicle manufacturer Subach-Innes is a major seller to the GTVA army, producing many tanks, transports, and handheld weapons. Due to the high performance of their army models, Subach was the first choice for the GTVA’s fighter-mounted weapons division when Bessimer-Kohn went out of business. Subach proved itself capable of the task by refining the xaser weaponry pioneered by Bessimer, and developed the phenomenally successful Subach HL-7 sidearm. The deployment of the Cyclops torpedo cemented Subach’s hold on the GTVA weapons contract, and it is now experimenting in advanced subspace and meson-based technologies.<br /> <br /> &lt;b&gt;Bessimer-Kohn&lt;/b&gt;<br /> <br /> &lt;i&gt;GTSG Watchdog, GTSG Cerberus, GTSG Alastor, GTS Centaur&lt;/i&gt;<br /> <br /> Bessimer-Kohn was a sister corporation to Han-Ronald, and the single largest weapons manufacturer during the Great War. Energy weapons and reactor producer Bessimer and Sons merged with missile and ballistic weapons manufacturer Kohn Industries shortly after the start of the Unification War, and sold its weaponry to anyone who would buy it. Their plasma turrets were cheap and energy efficient, and installed on every Fenris, Leviathan, and Orion that came off the lines. Their Fury missiles, as well as the MX and Phoenix series of missiles, were standard on Terran fighters long before first contact with the Vasudans. Bessimer-Kohn also produced the Watchdog, Cerberus, and Alastor sentry guns, as well as the Centaur support ship. Plasma turret factories ran at full-tilt until the development of beam weaponry and flak cannons. Bessimer-Kohn suddenly found itself with a huge surplus of unwanted and useless plasma turrets, and with the demise of Han-Ronald, the once-mighty corporation went bankrupt. The GTVA military acquired its assets and divided them up between contractors Subach-Innes and Mesa Corp. The only Bessimer-Kohn weapons still in service are the Hornet missile, Prometheus cannon, and Alastor sentry gun.<br /> <br /> &lt;b&gt;AGAY Fluctuators&lt;/b&gt;<br /> <br /> AGAY Fluctuators handles power management systems for most GTVA ships, though RNI uses their own designs. AGAY developed the Energy Transfer System now in use on all Terran and Vasudan fighters and bombers, following the widespread use of energy-based primary weapons. AGAY's designs also assist in reactor overloads, power storage, and enery transfer.<br /> <br /> &lt;b&gt;RNI systems&lt;/b&gt;<br /> <br /> &lt;i&gt;GTF Hercules Mark II, GTF Myrmidon, GTB Boanerges, GTSG Mjolnir, GTC Aeolus, GTG Zephyrus&lt;/i&gt;<br /> <br /> RNI was a short-lived corporation based in the GTVA colony of Laramis. After Han-Ronald’s decay, the new GTVA decided to find a new contractor to design their fleet from the ground up. The surprising choice of RNI Systems, previously known only for their lightweight alloys and mining colonies, was sound on paper but ultimately doomed. RNI recruited a new generation of architects, shipwrights, and engineers fresh out of university and set them to work, designing and manufacturing the wildly successful Hercules Mark II and Myrmidon fighters, and the famous Aeolus escort cruiser. Sadly, RNI never turned a profit on their military investments. Initial enthusiasm by the military tacticians was diluted by the excessive cost of the upgrades, and Aeolus production was stopped after only twenty-four units. Additionally, many of RNI’s top designers went on to more promising careers at Nankam, leaving the corporation without any staff or financial resources. The RNI assets were purchased by Subach-Innes in 2367, but allowed the corporation to remain as an independently functioning satellite. RNI still manufactures the craft designed in its heyday, but has few new models in development, instead concentrating on mining, metallurgy, and alloys.<br /> <br /> &lt;b&gt;Han-Ronald Corp.&lt;/b&gt;<br /> <br /> &lt;i&gt;GTF Hercules, GTF Loki, GTF Apollo, GTF Valkyrie, GTB Artemis, GTB Medusa, GTB Ursa, GTC Fenris, GTC Leviathan, GTD Orion, GTI Arcadia&lt;/i&gt;<br /> <br /> When someone mentions Terran starship design, they're probably talking about Han-Ronald Corporation, the largest manufacturer of Terran spacecraft during the Great War. Every Terran warship that saw battle against the Shivans in that conflict, with the exception of the Ulysses fighter and Athena bomber, was designed and manufactured by Han-Ronald. The partnership with arms manufacturer Bessimer-Kohn led to significant decreases in subsystem installation costs, one of the keys to its success. Han-Ronald has had strong ties to the GTA military ever since the introduction, and phenomenal success of, the Fenris cruiser in the late days of the Unification War. Since the GTA military invested heavily in Sol-based Han-Ronald, the loss of Sol in 2335 brought significant financial difficulties on the corporation. While the design team completed the Loki scout fighter and was later responsible for the mediocre GTB Artemis, it never recovered from that crippling blow.<br /> <br /> &lt;b&gt;Morgan Technologies&lt;/b&gt;<br /> <br /> Morgan Technologies was a research and development conglomerate in the [[Tau Sigma]] colonies, assisting in terraforming and colonization efforts there. At some point in the events surrounding the Derelict incident, Morgan went rogue and began outright attacks against GTVA installations, convoys, and warships. Their motivation remains unknown, and their flagship, the MTD Augira, is still at large.<br /> <br /> &lt;b&gt;Dynamic Metamer&lt;/b&gt;<br /> <br /> &lt;i&gt;GTB Athena, GTB Zeus, GTFr Chronos, GTDr Amazon, GTT Elysium, GTSC Faustus, GTM Hippocrates&lt;/i&gt;<br /> <br /> One of the few devoted civilian corporations to turn out a military design, Dynamic Metamer provided drones, transports, and cargo containers for civilian purposes since before the discovery of Subspace. Why the GTA gave Dynamic Metamer the contract for the GTB Athena is unknown, but for a time it was a popular choice among bomber pilots for its decent armor and vast afterburner capacity. Dynamic Metamer was unfamiliar with the more advanced GTA weapons systems, however, and the bomber was mothballed after technicians discovered they couldn’t mount Prometheus, Banshee, or Tsunami weapons on it. The company risked losing its first military contract, which had brought in more money in one year than the sales of the Elysium ever had, and asked Triton Dynamics to assist in the design of a replacement bomber. As a result the GTI gained sole ownership of the Zeus strike bomber, capable of mounting the most advanced weaponry they could develop. The Zeus saved Dynamic Metamer their strike bomber contract, but a number of factors, including the development of beam cannons, the Maxim gun, and advanced assault fighters, drained demand for light bombers. After many of the Zeus bombers in service defected to the NTF, Dynamic Metamer sold off the rest of the rights to Triton Dynamics and elected to return to the civilian market.<br /> <br /> &lt;b&gt;Comet propulsion systems&lt;/b&gt;<br /> <br /> Comet's engine designs are unremarkable, slow, sturdy and reliable. Most GTVA capital ships use Comet engine systems because of their compartmentalized systems. Repair crews can isolate, circumvent, repair, or replace engine components in minutes instead of hours, making high-risk rescue missions possible. Many GTVA lives and capital ships have been saved by the choice of Comet's engines. High-performance fighter engines, however, are better left to Nankam and Triton.<br /> <br /> &lt;b&gt;Nankam Aeronautical&lt;/b&gt;<br /> <br /> &lt;i&gt;GTF Ares, GTF Pegasus, GTF Perseus, Artemis DH powerplant, GTD Hecate, GTA Charybdis&lt;/i&gt;<br /> <br /> Nankam fills the niche in the SOC that was once Triton Dynamics’ role in the GTI. Once a manufacturer of high-performance aircraft for atmospheric combat, Nankam was heavily subsidized by the SOC to develop fighters that would outperform standard GTVA craft. The Charybdis AWACS, Pegasus stealth fighter, and various upgrades to the Artemis and Hercules II show promise in Nankam’s future with the SOC. Much like the SOC reaches into every branch of the GTVA, Nankam is a consultant for many of Subach-Innes and Triton Dynamics’ latest designs. The Perseus fighter was successful enough to reach general deployment, and Nankam also had a large part in the design of the Hecate destroyer.<br /> <br /> &lt;b&gt;STX Exploration&lt;/b&gt;<br /> <br /> STX Exploration is a Resource and Mining company, headquartered in Vega but with outposts in resource rich systems all over the GTVA, as far apart as Barnards Star and Mirfak. Though not a weapons or munitions company, it was STX's research in remote-controlled explosive devices that prompted GTVA scientists to begin upgrading the old MX-50 heat seeking missile to the Rockeye MX-64. STX has always maintained a good relationship with the GTVA, providing much of the raw material required for warship construction, and also as a significant contributer of purified deuterium to power the fusion drives of the fleet.<br /> <br /> &lt;b&gt;Snapka/Flegel Weapons Systems&lt;/b&gt;<br /> <br /> Weapons control systems are Snapka’s specialty, enabling dozens of weapon turrets and beam artillery emplacements to track and attack their targets with a minimum of technical difficulty. Their revolutionary beam cannon fire control system, colloquially known as ‘Beam-Free-All,’ was the greatest success for the company. BFA weapons subsystems were installed on the Colossus and every Hecate and Deimos that was ever produced, as well as on many retrofitted Orion-class destroyers.<br /> <br /> &lt;b&gt;Johnson Munitions&lt;/b&gt;<br /> <br /> &lt;i&gt;Fusion Mortar, N-1 Harbinger&lt;/i&gt;<br /> <br /> As a supplier to the GTA and later GTVA terrestrial military, Johnson Munitions pales in comparison to Subach-Innes in terms of size. However, their mortar and mobile artillery emplacements still have a place in the GTVA armies, and Johnson was contracted to build the missile launcher batteries of the Colossus.<br /> <br /> =Vasudan contractors:=<br /> <br /> &lt;b&gt;Mekhu Enterprises&lt;/b&gt;<br /> <br /> &lt;i&gt;GVF Seth, PVF Anubis, GVB Sekhmet, GVS Nephtys, PVFr Bast, GVFr Bes, GVG Anuket, PVC Aten, Mekhu HL-7&lt;/i&gt;<br /> <br /> Mekhu is an extremely diverse Vasudan corporation, extending into military and civilian affairs alike. Providing everything from foodstuffs to insurance services, freighters to computer systems, family-owned Mekhu has served the Vasudan people for nearly 400 years. Mekhu exerts considerable political influence, and was a strong supporter of Khonsu II during his ascension. The diversity of the corporation helped it succeed where many Terran contractors failed, and the Vasudan renaissance of the post-war era is due in no small part to excellent planning by Mekhu’s board of directors.<br /> <br /> &lt;b&gt;Akheton Corporation&lt;/b&gt;<br /> <br /> &lt;i&gt;GVF Horus, GVF Serapis, GVB Osiris, GVB Bakha, GVF Ptah, GVD Hatshepsut, GVA Setekh, GVCv Sobek, GVI Cairo, Akheton SDG&lt;/i&gt;<br /> <br /> Akheton’s designs are far more militaristic in nature than Mekhu’s, yet more graceful than Sahr's, resulting in a perfect blend of Vasudan design and functionality. Preferring finesse to brute force, Akheton has produced many beautiful, fast, and technologically advanced designs for the Vasudan military, and is the envy of many Terran contractors. New designs such as the Serapis, Bakha, and Sobek consistently amaze the Vasudan military with their effectiveness, and tacticians love the way the capabilities of the warships match the strategies they have chosen.<br /> <br /> &lt;b&gt;Sahr Corporation&lt;/b&gt;<br /> <br /> &lt;i&gt;GVF Thoth, GVF Tauret, PVB Amun, Seth powerplant, GVFr Satis, PVD Typhon, GVC Mentu, GVT Isis&lt;/i&gt;<br /> <br /> Sahr is the heavyweight of the three main Vasudan contractors, producing heavily armed and armored designs for offensive missions. Sahr engineers first discovered the benefits of collapsed molybdenum armor and became a large supplier of armor plating to both the Terran and Vasudan militaries. Sahr’s primary shipyards in Altair were captured when the Hammer of Light gained control of that system in 2335, and the heavy machinery and experimental weapons developed by Sahr kept the system in HoL hands for some time. The system was liberated in Operation Templar, and Sahr’s new designs for the Tauret assault fighter and Mentu cruiser serve the alliance well.</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Battle_of_Endor_Syndrome&diff=121 2005-06-07T19:47:00Z

<p>81.182.82.204: </p> <hr /> <div>==Battle of Endor-scheme missions==<br /> <br /> =What do we mean as Battle of Endor-scheme missions?=<br /> The Battle of Endor is a historic and very important battle in the Star Wars universe, which is unique among many science fiction films and universes. The Battle of Endor involved several dozen warships and hundreds of fighters at each side. If you ever hear somebody from the ~FreeSpace community mention about a Battle of Endor-type mission, he is thinking about a mission which involves several warships(often big ones, corvettes and larger) facing each other with space teeming with fighters. In ~FreeSpace, people are advised not to choose this type of mission for massive reasons. They are listed below.<br /> <br /> =Why should not I make such missions?=<br /> Here are the few, but convincing reasons why you should not:<br /> *Frame per second: Not everybody has a machine that is capable of handling such a large number of craft. This problem is even worse if the person in question [[FreeSpace Open]], which increases the hardware demand when its enhanced graphical features have been turned on.<br /> *The FreeSpace engine: There is not much that can be said here/ The engine is not designed for massive battles. The AI malfunctions, warships collide, fighters become less accurate and even less intellignet than they are usually.<br /> **Another note on the engine: The Retail engine (not [[FreeSpace Open]]) tends to crash when there is such a large load on the engine. [[FreeSpace Open]] is less sensitive, but even that programme cannot handle these types of missions very well. If it could, we would have fewer problems.<br /> *Beam weapons: Beam battles are neat and everything in FreeSpace, but having numerous warships shooting at each other at the same time is considered overkill. At the least, the player might accidentally run into a beam weapon and die at once, but warships tend to unintentionally hit their friendlies and that 'drops mission balance into the dustbin.'<br /> *Mission designer's nightmare: If you are a precise and circumspecting mission designer, you will find making such missions terribly painful and nerve-wracking. Testing these missions is not the easiest thing to do, either.<br /> <br /> =I still insist on doing a Battle of Endor-scheme mission, what should I do=<br /> Go ahead, with time and experience you will discover for yourself why this is a bad idea.<br /> <br /> =See also=<br /> [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=26 Article about the Battle of Endor scheme at VolitionWatch]</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Battle_of_Endor_Syndrome&diff=46 2005-06-07T19:45:27Z

<p>81.182.82.204: </p> <hr /> <div>==Battle of Endor-scheme missions==<br /> <br /> =What do we mean as Battle of Endor-scheme missions?=<br /> The Battle of Endor is a historic and very important battle in the Star Wars universe, which is unique among many science fiction films and universes. The Battle of Endor involved several dozen warships and hundreds of fighters at each side. If you ever hear somebody from the ~FreeSpace community mention about a Battle of Endor-type mission, he is thinking about a mission which involves several warships(often big ones, corvettes and larger) facing each other with space teeming with fighters. In ~FreeSpace, people are advised not to choose this type of mission for massive reasons. They are listed below.<br /> <br /> =Why should not I make such missions?=<br /> Here are the few, but convincing reasons why you should not:<br /> *Frame per second: Not everybody has a machine that is capable of handling such a large number of craft. This problem is even worse if the person in question [FreeSpace Open], which increases the hardware demand when its enhanced graphical features have been turned on.<br /> *The FreeSpace engine: There is not much that can be said here/ The engine is not designed for massive battles. The AI malfunctions, warships collide, fighters become less accurate and even less intellignet than they are usually.<br /> **Another note on the engine: The Retail engine (not [[FreeSpace Open]]) tends to crash when there is such a large load on the engine. [[FreeSpace Open]] is less sensitive, but even that programme cannot handle these types of missions very well. If it could, we would have fewer problems.<br /> *Beam weapons: Beam battles are neat and everything in FreeSpace, but having numerous warships shooting at each other at the same time is considered overkill. At the least, the player might accidentally run into a beam weapon and die at once, but warships tend to unintentionally hit their friendlies and that 'drops mission balance into the dustbin.'<br /> *Mission designer's nightmare: If you are a precise and circumspecting mission designer, you will find making such missions terribly painful and nerve-wracking. Testing these missions is not the easiest thing to do, either.<br /> <br /> =I still insist on doing a Battle of Endor-scheme mission, what should I do=<br /> Go ahead, with time and experience you will discover for yourself why this is a bad idea.<br /> <br /> =See also=<br /> [http://www.volitionwatch.com/articles/ArticleDisp.php?ID=26 Article about the Battle of Endor scheme at VolitionWatch]</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Mission_design&diff=55 2005-06-07T19:44:14Z

<p>81.182.82.204: </p> <hr /> <div>&lt;br&gt;[[FRED Tips]]<br /> &lt;br&gt;[[References]]<br /> &lt;br&gt;[[Backgrounds]]<br /> &lt;br&gt;[[Plot Development]]<br /> &lt;br&gt;[[Mission Chatter]]<br /> &lt;br&gt;[[The World of SEXPs]]<br /> &lt;br&gt;[[The FRED Academy]]<br /> &lt;br&gt;[[Battle of Endor-scheme]]</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=FRED_Academy&diff=61 2005-06-07T19:43:12Z

<p>81.182.82.204: </p> <hr /> <div>===FRED Academy===<br /> ==What is the FRED Academy and what is its purpose?==<br /> The FRED Academy is an attempt by the community to help develop the skills of new [[FREDders]]. Too often new people join the community and work for a little while on a campaign before getting bored by the solitude of working on a mod singlehanded and leave.<br /> The idea of the academy is to let these people work as part of a team on their first few missions while similtainiously helping improve their skills.<br /> People who just want to brush up their FREDding skills are also welcome to join too.<br /> <br /> The Academy will also serve as a place where the hosted campaigns can spot talented new FREDders and sign them up<br /> <br /> ==How does the Academy work?==<br /> Basically the [[FREDders]] write missions for one of the campaigns described in the FRED Academy main thread. The missions are then playtested by the other members of the Academy and passers-by looking for missions to play. They post their impressions of the mission. What worked, what didn't and if any bugs were found.<br /> In addition to this general testing missions will also be tested by some of the more able [[FREDders]] in the community. Not only will these people spot bugs etc but they will be on hand to advise how to correct them.<br /> <br /> ==How can I enter the FRED Academy?==<br /> &lt;b&gt;FOLLOW INSTRUCTIONS:&lt;/b&gt;<br /> *Go to the [http://www.3dap.com/hlp/ Hard Light Productions forum] and register, if you have not registered yet<br /> *Go to the FreeSpace Campaigns forum<br /> *View the thread named FRED Academy and read all the necessary info<br /> *If you decide to enrol, post in the thread, mentioning your intentions of joining<br /> <br /> or<br /> <br /> *You can contact karajorma by sending him a Private message via Hard Light Productions<br /> *You can also contact an other member of the Community, TopAce by sending a message via ICQ to #235325080 or send him a PM via Hard Light Productions</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=FRED_Academy&diff=44 2005-06-07T19:41:56Z

<p>81.182.82.204: </p> <hr /> <div>===FRED Academy===<br /> ==What is the FRED Academy and what is its purpose?==<br /> The FRED Academy is an attempt by the community to help develop the skills of new FREDders. Too often new people join the community and work for a little while on a campaign before getting bored by the solitude of working on a mod singlehanded and leave.<br /> The idea of the academy is to let these people work as part of a team on their first few missions while similtainiously helping improve their skills.<br /> People who just want to brush up their FREDding skills are also welcome to join too.<br /> <br /> The Academy will also serve as a place where the hosted campaigns can spot talented new FREDders and sign them up<br /> <br /> ==How does the Academy work?==<br /> Basically the [FREDders] write missions for one of the campaigns described in the FRED Academy main thread. The missions are then playtested by the other members of the Academy and passers-by looking for missions to play. They post their impressions of the mission. What worked, what didn't and if any bugs were found.<br /> In addition to this general testing missions will also be tested by some of the more able [FREDders] in the community. Not only will these people spot bugs etc but they will be on hand to advise how to correct them.<br /> <br /> ==How can I enter the FRED Academy?==<br /> &lt;b&gt;FOLLOW INSTRUCTIONS:&lt;/b&gt;<br /> *Go to the [http://www.3dap.com/hlp/ Hard Light Productions forum] and register, if you have not registered yet<br /> *Go to the FreeSpace Campaigns forum<br /> *View the thread named FRED Academy and read all the necessary info<br /> *If you decide to enrol, post in the thread, mentioning your intentions of joining<br /> <br /> or<br /> <br /> *You can contact karajorma by sending him a Private message via Hard Light Productions<br /> *You can also contact an other member of the Community, TopAce by sending a message via ICQ to #235325080 or send him a PM via Hard Light Productions</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Mission_design&diff=45 2005-06-07T19:40:41Z

<p>81.182.82.204: </p> <hr /> <div>&lt;br&gt;[[FRED Tips]]<br /> &lt;br&gt;[[References]]<br /> &lt;br&gt;[[Backgrounds]]<br /> &lt;br&gt;[[Plot Development]]<br /> &lt;br&gt;[[Mission Chatter]]<br /> &lt;br&gt;[[The World of SEXPs]]<br /> &lt;br&gt;[[The FRED Academy]]</div>

81.182.82.204 https://wiki.hard-light.org/index.php?title=Mission_design&diff=42 2005-06-07T19:33:21Z

<p>81.182.82.204: </p> <hr /> <div>&lt;br&gt;[[FRED Tips]]<br /> &lt;br&gt;[[References]]<br /> &lt;br&gt;[[Backgrounds]]<br /> &lt;br&gt;[[Plot Development]]<br /> &lt;br&gt;[[Mission Chatter]]<br /> &lt;br&gt;[[The World of SEXPs]]</div>

81.182.82.204