[Chrisatsilph]

Ive been using FRED2 for about 1 week and I want to see if im missing anything from my missions that im making.
You can have ago at this mission and list some things I could do to improve it. 

Note:
1) Event names a wacked out to the max, maybe I should use proper event names?
2) This mission happend BEFORE the Iceni self-destructs.
3) Try not to use cheats 
4) This is in the single mission section in the tech room.

[attachment deleted by ninja]

[Marduk]

The sun the sun the sun. It hurtsis the eyes much. I'd suggest you either get rid of it entirely, or move it so it isnt in the player's face for 75% of the mission. Also the color of the nebula makes the default text color very hard to read.

Use the team loadout editor! weapon-D is multiplayer stuff, for one, and allowing every single weapon or ship isnt realistic. And it also can make the mission break when intrepid people who find it cathartic to use an erinyes with dual maxim guns to kill shivans end up disabling warships which shouldnt get disabled. ***

And beam-free-all the capital ships. just because and all. Unless theres a reason their antifighter beams shouldnt work.

And when youre making briefing icons, change the 'ship type' to whatever the icon represents. (for instance the Powerlax shows up as an Ares)

And you can use send-message-list to send multiple messages in the same event, with a time delay between them so theres no need for a new event. so there's no need for all of the 'is-event-true-delay's

Maybe launch bombers from the destroyer to hit the awacs so there's something actually gunning for it. And the same for the reinforcement wings of fighters. I dont see why they'd be jumping in with a functional destroyer right there with a working fighterbay. And maybe vary the types of fighters coming at you too.

And if there's an Awacs vessel, there shouldnt be any problem with sensors, nebula or no. You can use the awacs-set-radius sexp (under the special tab) to change the radar radius given by the awacs vessel.

*** continuing on that end: use ship-subsys-guardian(-threshold) to prevent subsystems from getting destroyed which shouldnt be, like engines. Or have them repair using a different sexp right before the ship is supposed to jump out and then they will actually jump out, rather than sitting there staring at each other.

and proper event names doesnt really matter. unless there's some secret kill-code in the engine which melts your harddrive if an event is named something it doesnt like.

All in all not bad for the amount of time playing with the editor. You might want to take a stab at a a Fred Academy mission though -->http://www.hard-light.net/forums/index.php/board,125.0.html

[Colonol Dekker]

I like this. it warns the cockles of my heart to see a brand new fredder have a stab at a mission and not throw out a mission like that jad boe one. Potential. I see potential. Once the basic editors have been grasped, honeing of skills by virtue of the aforementioned academy must be taken up. +1 Dekker point.

[Mobius]

I really like attempts like this one. Remember to read The FAQ^TM(link is in my signature), it is full of precious hints.

There are many projects looking for FREDders, you might "get a job" in the immediate future

[Chrisatsilph]

Thanks for the advice guys, It really does get your confidence up 

Btw I swear that I did put beam free for all on the ships but maybe I forgot to lol I put them on all the other ones ive made probaly forgot this time lol.

Thanks for telling me about the Awac settings, ive been looking for the Awac settings all over FRED2 when its in the simpliest place.

[karajorma]

A couple of the mistakes Marduk mentioned are in the common mistakes section of my FAQ so take a look at that at least. If should help you watch out for similar pitfalls in the future.

[Chrisatsilph]

Just had alook at my mistakes, Next time Ill make sure it is Mistake proof, well I hope