Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Petrarch of the VBB on February 18, 2003, 02:34:25 pm
-
What's this about shields now blocking beams? I don't agree with it at all, as it means that AAA is no longer a threat. Is there any way i can disable it?
-
Originally posted by Petrarch of the VBB
What's this about shields now blocking beams? I don't agree with it at all, as it means that AAA is no longer a threat. Is there any way i can disable it?
:eek2: What cretin did this?!
-
IIRC the SCP guys only want to implement that for fighter beams
-
Fighter shields would be fried instantly by a real beam. Though AAA would become useless.
If you say its for fighter beams only, then its good :D
-
it doesn't matter, because the big beams destroy the shields and the ship near instantly, and small fighter beams should affect shields.
-
As Carl said. It's supposed to be this way; shields not blocking beams was a bug in the original build.
Rest assured, beams will still knock you about, and they're quite dangerous if you have low shields.
-
or we could have the shield multiplier increased
-
Well if you guys pay attention closely while playing the original freespace, you'll notice that when under beamfire, your shields would sometimes get fu)(0red along with your hull. OF course this happened with collisions a little too. Maybe you could make it fully for collisions. Making beams affect shields makes the beam techj more clear and making the shields affect collisions makes the shield tech more clear (like why it stops maxims and missiles, but no debris or another fighter)
-
i thought that shields not blocking beams was done to justify the absence of shields on capships
-
Shields on Capships = No fun on gamplay
-
Originally posted by KARMA
i thought that shields not blocking beams was done to justify the absence of shields on capships
I always thought it was to represent the fact that they're using a GIANT ****ING GUN on you.
:D
-
Originally posted by Shrike
I always thought it was to represent the fact that they're using a GIANT ****ING GUN on you.
:D
;7
Erm.....people actualy requested that beams could be blocked by shields. And there still effective if you have been pounded by missiles/lasers/flak and AAF fire then your shields are no more and then you die:D Atleast i did:D
I am making no sence:blah:
-
too much b33r again?
-
Yeah, i need beams to be blocked by shields, for my NW project.
-
It sucks, tho. You can now fly along, straight at a Deimos, at 20 m/s, and not get ripped up. You dont't need any controls anymore!
-
I really like the idea of beams being blocked by shields. However, there should be a limiter, like a only a ship with a certain shield strength or size class can block a beam.
-
Have the be blocked by shields, but don't turn off there mass/***** slap you silly mode.
-
this has reminded me to the shield piercing flag thing done
update; done :)
-
Shields should still take damage from beams though.
-
Ugh... this has ruined the game balance for me. Could you guys at least give us mission makers the ability to turn this behaviour off in the mission or at the command line? The very point of beams was that they were dangerous because they penetrated shields. :no:
Sid.
-
That's my point exactly.
-
Originally posted by SadisticSid
Ugh... this has ruined the game balance for me. Could you guys at least give us mission makers the ability to turn this behaviour off in the mission or at the command line? The very point of beams was that they were dangerous because they penetrated shields. :no:
Sid.
I agree, except put the toggle in FRED. I've had very little experiance with command flag thingies.
If it has to be a startup command flag, answer this:
Is it possible to use multipule command flags on startup?
-
Originally posted by SadisticSid
Ugh... this has ruined the game balance for me. Could you guys at least give us mission makers the ability to turn this behaviour off in the mission or at the command line? The very point of beams was that they were dangerous because they penetrated shields. :no:
Sid.
I agree, except put the toggle in FRED. I've had very little experiance with command flag thingies.
If it has to be a startup command flag, answer this:
Is it possible to use multipule command flags on startup?
EDIT: Personally, I disagree with the idea of beams being blocked by shields almost completely.
BTW, the 'Lasers' should really be 'Plasmas'
-
Originally posted by SadisticSid
Ugh... this has ruined the game balance for me. Could you guys at least give us mission makers the ability to turn this behaviour off in the mission or at the command line? The very point of beams was that they were dangerous because they penetrated shields. :no:
Sid.
I agree, except put the toggle in FRED. I've had very little experiance with command flag thingies.
If it has to be a startup command flag, answer this:
Is it possible to use multipule command flags on startup?
Personally, I disagree with the idea of beams being blocked by shields almost completely.
BTW, the 'Lasers' should really be 'Plasmas'
-
um... I did just make a shield pierceing flag
-
Raptor, triple post /\. :nod:
-
Yes. Raptor? How did you manage that?
-
Oh heck.......
I kept on changing it. Trying to be more, er diplomatic, to avoid insulting anyone.....:nervous:
BUT, like an idiot, instead of using EDIT, I was hitting the BACK button on my toolbar. :gulp:
I would delete the first two posts, except the system won't let me:mad:
-
Ahh, so you're not out of order, the Whole Freakin System is out of order! Yes?
-
Originally posted by Petrarch of the VBB
Ahh, so you're not out of order, the Whole Freakin System is out of order! Yes?
Well, maybe. It was saying that I don't have access to this forum. Asking me if I was tring to edit someone elses post:wtf:
But, I'll admit, I messed up. Big time:o
Note to self, always use EDIT to change posts
If one of the admins would be so kind, could you please remove the first two. Please?
-
Happens to me all the time. Keep pressing quote instead of edit.
HA! My post count is 1337!