Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: Fergus on September 07, 2004, 11:23:35 am
-
The first problem is that I have no idea how to post images or missions, because of this the second problem is more acute. I have never really used forums much before (I try to ignore ' a picture is worth a 1000 words' principle) so the help really isn't filling me with knowledge (neither am I technically competent)
The second problem is that I have a mission that until a while ago worked fine. However, now whenever I try to play it the game crashes and I get an error message (also I have to restart to use several other programs). The mission can still be accesed in FRED though, so if it is an in mission fault it can be fixed.
But before I can fix the mission I need to be able to post it.
-
Use a free host such as Tripod (http://www.tripod.lycos.com/) or Geocities (http://www.geocities.com), sign up, upload the files you want to show.
Then when posting give us a link to the file you want us to download or see. As for images you can also use [lvlshot]link to image[/ lvlshot] (without the space between / and lvlshot) or use [IMG]link to image[/ IMG] (again without the space between / and IMG) if the picture is small enough (so I've been told hundreds of times ;) :p ).
-
okay lets try this
mission click here (http://willy-murdo.tripod.com/sitebuildercontent/sitebuilderfiles/cruiser_defense.zip)
good luck
-
ooh tripod. Bad choice.
Most browsers actually will interpret linked files based on content rather than extension though, so if you're stuck with free hosting you can change the extension on a jpg, for example, to .txt and at least Geocities will let it through.
-
You can use his link by using the command "save as" or "save where" (don't know the command in windows with english as their language") and then decompressing the file in your own HDD. :p
-
True. But then one would have to know it was a zip file.
-
You mean like... looking at the link?
-
Ok, can't argue with that one :p
My point about tricking the hotlinking ban still stands though.
-
You should try to vary your CBAnis a bit. For example, you might use cb_sm2-10_d.ani (A sath Flypast) for the second stage. There's a full list of the CBAnis on the FS2 reference guide.
http://freespace.volitionwatch.com/fs2/refguide/fs2refguide.chm
There are a few spelling errors in places (weve (needs an apostrophe) departue, simpelest. They mostly look like fairly minor typoes though. Run it through a spell checker and you should be fine.
Some of the ship names should probably be changed to ones more fitting with their species general conventions - eg. turn Helios 1 and 2 into somehting hindu, or just a general demon/nasty and Thunder into something egyptian sounding.
Some of your crew numbers seem a bit inflated. We know the official figure for an Orions crew is roughly 10000 (Koth says so). Try to base your numbers off that (Ie. cruisers with several hundred, corvetted with several thousand, etc.
Your Return to Base directive should be chained to the RTB event, and put on an event that fires either when Alt-J is pressed, or when Alpha 1 has departed.
Instead of making ships like Alpha 1 and Epsilon 2 invulnerabe by default, do it when their hull drops below about 25%. This is, I'll admit, slightly riskier, since things like beam shots and big shockwaves can do more damage than 25% of a fighters hull, but 99% of the time you'll be OK, and it makes the mission feel a little more real if these guys can take damage.
Also, a BG would be nice, but if this is still a WIP, then I assume that'll come.
All that said, it's still a pretty good mission - I'm basically just nitpicking to get some of the finer details right. Good stuff.