[Lonestar]

Originally posted by karajorma


Just being pedantic but of course a designer should Beta-test his missions.

He just shouldn`t be the ONLY person to beta test. I`ve played far too many beta missions that are far closer to alpha because the designer hasn`t played it enough.

Yeah they shld, but they will not get a good gauge on the difficulty for players who never seen the mission, nor will they see some obvious mistakes. Of course the designer needs to test his own missions to ensure it works like he planned, but otherwise he shld steer clear. Ive made more mistakes testing my own mission, then sending it to someone else for testing did.

For some reason (and its prolly just me) i miss the most obvious mistakes, as i had been working on it for so long it just escaped me. Kinda weird, but yeah as the dude says, Test your own, but get others to test for you to complete the beta stages.

[karajorma]

I knew what you meant Lonestar it's just that I`ve beta tested a few missions that it appears the designer hasn`t even played let alone tested.

Hell I've played some released missions like that

[Lonestar]

Originally posted by karajorma
I knew what you meant Lonestar it's just that I`ve beta tested a few missions that it appears the designer hasn`t even played let alone tested.

Hell I've played some released missions like that

When running Fredzone i got that daily. People would submit missions and we would spend literally months beta testing and repairing them with the author so they would be good for multiplayer play and valid for PXO.

I found it better to have the designer just send me the changes and ill test them, then i wld tell them what they need to fix (in fred terms), have them fix it and resend to me for beta testing again.

At times some said there mission was tested, by the creator extensiviely. However when FZ got it, it seemed as tho it wasnt tested at all. Through no fault of the designer, as i can tell it was something easily overlooked when concetrating on the big picture.

So we adopted a beta testing team, who knew fred inside and out, so this way when problems were reported a solution was immediately available. Turned out better then having the designer test it.

I know what you mean about supposed finished missions, sometimes it boggled me as to what people considered "finished", and also another thing that bugs me is the insane amount of shivans people think exist, furthermore existed during the FS2 wars in specific areas.

Who has ever actually even heard in a tech briefing about 50,000 shivan fighters let alone seen them firsthand in a cargo escort mission? I could go on about how the cargo, if it was that important shld be protected by a Collossus but ill stop there...

[Miburo]

Originally posted by Tiara


Pfffffff... I just get in a space suit and and get my axe. Then shoot myself out an airlock!

*CHOPCHOPCHOPCHOP*

No more beam cannon for you mister Sathanas 1!

My excact sentences, but instead of Axe I would have a Katana

[Tiara]

Originally posted by Miburo


My excact sentences, but instead of Axe I would have a Katana

Hmmm... I also could slip into my assasins suit and slit the Sathanas beam cannon conduits

[Woolie Wool]

Hmmm...

It took about 10 seconds of constant fire with Kaysers to destroy one of a a Ravana's beam cannons so it seems that a blade would have a hard time destroying the beam cannons of a Santhanas. Also, what if a Shivan outside of a ship attacked you? In case you haven't played very much FS, a Shivan's claw can crush most metals. Human flesh would be no problem.

[Hippo]

the shivans did attack you outside the ships... its in the Silent Threat movies, the freespace1 boarding party movie, and the FS1 credits...

BTW... Akhatohn SDG can do more turret damage than kaysers...
BTW2... this is a FreeSpace forum, most if not all people here have played FreeSpace

[Tiara]

Originally posted by Woolie Wool
Hmmm...

It took about 10 seconds of constant fire with Kaysers to destroy one of a a Ravana's beam cannons so it seems that a blade would have a hard time destroying the beam cannons of a Santhanas. Also, what if a Shivan outside of a ship attacked you? In case you haven't played very much FS, a Shivan's claw can crush most metals. Human flesh would be no problem.

We were just joking And I have played FS (FS1, FS:ST AND FS2)

Still I could place a nuke/GTVA mini meson ala B5 Thirdspace on the Artifact on the Sath and watch it go BOOOOOOOOOOM!

[Hippo]

ok W.W., make what you think the perfect escort mission is, and email it to me at [email protected] and i'll test it

[Woolie Wool]

I am making something like an escort mission, where you have to protect a Demon destroyer (you are a pilot for a new faction called the Terran-Shivan Alliance), but most of the ships attack YOU. The threats posed to the Demon are, in order of appearance in the mission, a Sobek (easily destroyed by the Demon), a wing of Osiris bombers, a wing of Ursas, two damaged Aten cruisers with BFRed cannons,  and a wing of Boanerges or Boanergeses or whatever the plural should be spelled. Otherwise, the opposition is supposed to mop up you and your fellow pilots so they can send in more cruisers, bombers, and corvettes later.

One difference from many FS2 missions is that you play as Beta 1. You relieve Alpha wing, whose three ships are down to 5% hull integrity and their shield generators destroyed. You have to keep them alive for a few seconds until they can warp out.

Here are the objectives:

Protect TSD Doomgiver (primary objective)
Eliminate wing of xenocidic Shivans who are attacking Alpha wing
Protect Alpha wing until they warp out (primary objective)
Destroy all hostile ships that warp in (I mentioned the first wing of GTVA ships (Cancer) in the briefing by accident)
Then return to base

I don't know how to make objectives work right, so I'll send my mission to you. I placed two objectives in: Protect the Demon destroyer (which was named the SD Monster at first but I changed the name to TSD Doomgiver but didn't change the objective), and destroy Cancer wing. However, I can't make the objectives work right and prevent destroy-hostiles objectives from appearing in the briefing. Can anyone help?

[karajorma]

Originally posted by Woolie Wool
I don't know how to make objectives work right, so I'll send my mission to you. I placed two objectives in: Protect the Demon destroyer (which was named the SD Monster at first but I changed the name to TSD Doomgiver but didn't change the objective), and destroy Cancer wing. However, I can't make the objectives work right and prevent destroy-hostiles objectives from appearing in the briefing. Can anyone help?

Make the objective invalid from the ojectives editor. When the hostiles appear use the relevent SEXP (objective-vaild or somesuch) to turn the objective back on again.

[Woolie Wool]

I was reading a tutorial about SEXPs when I read your post and just learned how to make objectives work.

[diamondgeezer]

Originally posted by Woolie Wool
I was reading a tutorial about SEXPs when I read your post and just learned how to make objectives work.

Hence the saying "DO THE ****ING WALKTHROUGH"[/b]

[Lonestar]

mkay.

Dude if your going to make a Story i highly suggest finding some Universe timelines (http://ugcworld.com/fredzone) and find other information to make it make sense in the FS2 universe, unless of course u just want to screw around....

[Galemp]

My, what a ridiculous mission that would be! Silly Newbies.

Doomgiver, eh? I think we might have an FPS fan here... just a hunch...