DICE/EA....Spawn Gaurd please...next patch ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Real_CaGeD

    #31
    Re: DICE/EA....Spawn Gaurd please...next patch ?

    Yes, spawn guard,,,,cmon e.a./dice do it, just do it. You pandered to all the other whiners and ruined the game with 1.2. I dont see what the problems with a spawn guard are?

    Comment

    • Sgt.BoscoBA

      #32
      Re: DICE/EA....Spawn Gaurd please...next patch ?

      NO, if you put spawn guard in place how am i supposed to pwn the re-res that spawn up all discombobulated? You know the ones, they lay on the ground for 30 sec. after spawn cause they have the map window open... LOL. Then cry cause they get worked when they pop up....

      Comment

      • imported_Warrior[DD]

        #33
        Re: DICE/EA....Spawn Gaurd please...next patch ?

        I know I will get flamed for using Black Hawk Down as a reference but I am going to do it anyways. Your spawn armor in BHD is only good for the five to 7 seconds unless you use your weapon once you use your weapon the spawn armor is gone. If you are being spawn raped the rapers know about this spawn armor and wait till it wears off, on the other hand the rapee's can use it to hide or spot there enemy before getting shot (fair chance). Even if you have a flag the problem in BF2 is most peeps know where the spawns at the flags are and camp them for easy kills. How many times have you respawned at a flag and gotten killed instantly???

        Comment

        • vbl

          #34
          Re: DICE/EA....Spawn Gaurd please...next patch ?

          Originally posted by Jesse
          If they can take calculations for a parabollic trajectory of artillery, then add a radius function to have the artillery land anywhere from the center to whatever radius you specify as the deviation, I'm sure they could easily throw one in there using recycled code. That is, if it doesn't exist already.

          Code:
          ObjectTemplate.create SpawnPoint SquadLeaderSpawnPoint
          ObjectTemplate.PreCacheObject 1
          ObjectTemplate.setScatterSpawnPositions 1
          ObjectTemplate.setSpawnPositionOffset 0/0/0
          Not sure that will randomize it, but I don't see how it couldn't be randomized, given they can throw many more calculations at the arty and still get it within a radius, with very little effort. Maybe something like

          Code:
          ObjectTemplate.setSpawnPointRadius xxxx
          Where X is some value from the absolutle position of the spawn point. If it is zero, the function simply defaults to what BF2 has now. If the number is greater than 0, it picks a spot in that area.

          I'm just saying that you could do a 1x3 triad of spawn points with little more than modifications to the maps.

          Comment

          • ConscriptVirus
            Member
            • Oct 2007
            • 6369

            #35
            Re: DICE/EA....Spawn Gaurd please...next patch ?

            actually even tho i hate it...there shouldnt be a spawn guard...if u kno that tanks are surrounding one flag..why spawn there..ur just asking to be killed...i tend to spawn at a place where there's no action (but pretty close) so i can let my comp smooth out with the ram

            Comment

            • Terroser

              #36
              Re: DICE/EA....Spawn Gaurd please...next patch ?

              Mu suggestions is Take A GODAM AT KIT

              tank you.

              people who need protection are just not so smart people because,
              there is always a flag near or a squadleader where you can spawn.

              Comment

              • pYura

                #37
                Re: DICE/EA....Spawn Gaurd please...next patch ?

                Originally posted by HowieMandel
                Ok for starters, as a long term player thus far, the specific spawn points at flags, are little obvious and open. Which when cornered at one peticular flag you have your little tanks and apc's and nade tossers with ammo bags at their feet spamming like freaks, to kill newly spawned soldiers. This isnt a huge problem, but it does suck.

                Why not implement a "spawn-gaurd". Where as when a person spawns, he has say, 5 seconds or so, to be able to actually;
                1.) figure out exactly where he is on the map.
                2.) MOVE, without dying from, apc spam, tank spam, claymore spam, nade spam, etc.
                3.) actually, have a chance at making the game continue, to escape, which in the end is more fun for everyone.
                very cool idea! just dont forget to add that at this short period is not able to shoot so it wont give an unfair advantage ...

                Comment

                • markan dorka

                  #38
                  Re: DICE/EA....Spawn Gaurd please...next patch ?

                  Spawn guard isn't actually as good idea as it sounds, it just creates too many problems.

                  Dealing with people with guard on combined with regular targets is just too much hassle. Also, it gives the *advantage* to guy spawning - guy firing at you doesn't know when it ends (wasting bullets and getting his deviation up for nothing), but you can fire the instant the guard wears off.

                  Also, it'd be downright exploitable - fresh spawned guys would just run up and break a cap with nade in their hands .. invincible spec ops running up to a tank to plant their C4 once their guard wears off and they're too close to be shot.

                  Then again, I'm partial, I don't see a problem with current system. I think there's just 2 solutions at all to spawnkilling anyway (if it ever was a problem that is :P) :

                  - make spawning areas inaccessible, in DoD, each team has their spawn area blocked by a ramp that prevents movement from one direction, and usually guys who manage to enter it get instagibbed anyway .. in BF2, this'd require major map reworking, and can't be done without redesigning the maps (that'd be one huge patch)

                  - add some more spawnpoints.. I don't think each flag should have 2-3 points, but some. I think Sharqi has perfect setup - 3 uncappables for MEC, and city entrance + tv station has extra points for USMC. Come to think of it, almost all maps have several spawn points at uncappable (or several uncappables), which kind of makes me wonder why spawnraping ucb is any issue at all. Maybe give 1 more to some cappables - flags that are very important or are very prone to raping. Also, places like wake airfield should get 3 spawnpoints to choose from, instead one, that teleports you to 3 very different locations you have no control over. I dunno if they can add spawn points without recompiling the entire map anyway, so this one may be moot as well.

                  I don't like the idea of larger random spawn areas in flag vicinity (this is somewhat happening already - there's at least 2 separate locations to spawn in each flag).. it's major boon to freshly spawned defenders, and I'd rather spend my time promoting stuff that keeps up the game speed and flow anyway :P

                  Comment

                  • [MyIS]Spetsnaz

                    #39
                    Re: DICE/EA....Spawn Gaurd please...next patch ?

                    Originally posted by HowieMandel
                    Ok for starters, as a long term player thus far, the specific spawn points at flags, are little obvious and open. Which when cornered at one peticular flag you have your little tanks and apc's and nade tossers with ammo bags at their feet spamming like freaks, to kill newly spawned soldiers. This isnt a huge problem, but it does suck.
                    Spawn camping is a valid tactic. Always has been, always will. If you're attacking, you usually have multiple flags to spawn on. For example, in Karkand, the US has 3 main spawn points that cannot be capped.

                    If someone is camping the spawn point in the back, let them sit there and go after the flags.

                    If someone is camping the left spawn point, spawn on the right and take them out.

                    if someone is camping on the right spawn point (the usual occurence), spawn on the left and take them out.

                    It's a very simple concept.

                    If you're MEC and all you have is the Hotel flag, you can easily get spawn camped because there are only 3 spawns there and 3 vehicles on the whole map.. so it fits. However, if you lose all your flags that is the price you pay.

                    The entire point of game is to create a challenge. If you can't handle the challenge... play SP

                    Why not implement a "spawn-gaurd". Where as when a person spawns, he has say, 5 seconds or so
                    I'm assuming you only mean to implement this on uncappable spawn points. Doing so for the rest would be a very bad idea (the word ludicrous comes to mind).

                    Even if you do implement it for uncappable spawns, it's only giving the assaulting team an advantage.. and why would you want to do that? Most maps are very balanced and if an entire team tries to spawn camp they will usually lose half of their flags (unless the team being spawn camped sucks, which is their fault).

                    1.) figure out exactly where he is on the map.
                    He should know, he's spawning there. This all pertains to experience and skill. On the maps that I frequent, I will spawn and know where I am immediately. Just a reflex.

                    2.) MOVE, without dying from, apc spam, tank spam, claymore spam, nade spam, etc.
                    There is already a 1 second spawn guard. If you put a claymore directly in front of a spawn, when someone spawns it will blow but they will be unhindered.

                    Also, there's no such thing as:

                    "Tank spam", "APC spam", etc.

                    Why do people create these words? How can you "spam" with a tank? Just think before you say it. A tank's purpose is to kill stuff with its big gun, MG and treads. How can you "spam" that?

                    3.) actually, have a chance at making the game continue, to escape, which in the end is more fun for everyone.
                    Not really. I love spawn camping. It feels like a victory and brings alot of joy. If you beat the other team, you should be able to reap the benefits of racking up your kill rate.


                    ---

                    And remember... they can do the same to you!

                    Comment

                    • filthyscumbag

                      #40
                      Re: DICE/EA....Spawn Gaurd please...next patch ?

                      In Wolfenstein or ET you were able to look around your area from your dead fixed position after you were killed. This helped to spot your enemys position.

                      Comment

                      • « R²» HKS

                        #41
                        Re: DICE/EA....Spawn Gaurd please...next patch ?

                        I agree there should be more spawn points per cp. However I don't necessarily agree to the spawn shield for all cp's. Not because I camp, I don't but it should only be for uncaptureable bases.

                        In fact why not have a server side option that lets a server admin to choose whether or not a uncap should have a spawn shield over the base. The way I would propose it is that only spec ops can enter a uncap to destroy commander assets. He can defend him self to a certain number of kills, once this number has been reached (to avoid spawn camping) his health would slowly go down. This would encourage the spec ops to only blow commander assets and then leave the uncap. They could still hide out in an uncap until they reach the pre-set defensive kills, in case they need to re-blow the commander assets again.

                        Say a tank rolls into an uncap without all flags taken 1st and tries to rape an uncap. It would = a death or health depleting until he left the uncap. A plane tries to rape an uncap, same deal their health could deplete more rapidly because of the much higher speed. If there was a penalty involved it would stop this cheap style of gameplay which is encouraged by the stats system.

                        If DICE won't add a solution to this we will make our own in the form of a script, which we are currently working on.

                        Comment

                        • Ghilleman

                          #42
                          Re: DICE/EA....Spawn Gaurd please...next patch ?

                          It sounds like a good idea, unfortunately, we live in reality. in reality, this means that spawn points would be near impossible ot capture, as the defenders would get their moments of invincibility long enough to repluse the attack, and kill 1-2 guys before the armor dies. I agree with ^^^ and that this should apply to un-cappables ONLY.

                          Comment

                          • imported_bigpappa
                            Member
                            • Oct 2006
                            • 2159

                            #43
                            Re: DICE/EA....Spawn Gaurd please...next patch ?

                            i think all guns should be replaced with fluffy pillows...

                            Comment

                            • redrider

                              #44
                              Re: DICE/EA....Spawn Gaurd please...next patch ?

                              I dont think that there is a problem at cappable flags. The main problem I have with spawn camping is when the game starts and I spawn for the first time at an uncappable and low and behold Im camped right away.
                              I think a better solution is to make the spawn points at uncappable flags hard to get to. With maybe a hill that the enemy has to climb to get there and to get there it takes the enemy about 10 seconds to get there from thier nearst spawn point and another 10 seconds to climb the hill or to go around to the climb up place. Any change more than this would be exploited by someone, as such things are.
                              As for myself I usually wont plan on spawn camping the enemy but if Im walking along or in a fire fight and see them spawn thier dead meat. On the other hand if I get spawn camped at an uncappble flag the rest of the time im on that server, that day, its gonna be spawn camp city.
                              I have played on servers where the other team didnt spawn camp so if they got down to only having one uncappable flag left to spawn at I will give them a few meters to spawn and move. Its like returning the favor. Besides I enjoy playing the game and dont enjoy target practice. Right now, the best defense for spawn camping is to just leave the server. The reason being, it aint gonna get any better.
                              On some maps I count on being spawn camped and set myself up to kill the spawn campers. Spawn campers usually arent very good players and have to spawn camp or they will score less than 10 points a round. Karkand is a good example I usually spawn as a medic (when playing as USMC) and immediately switch to my med kit. I know there is usually a sniper or lame guy with a G36 lineing me up in his sites as soon as I spawn.
                              Finally I am getting tired of people requesting changes be made to the game so they will have an advantage or wont get killed so much, when all we usually get from this is something nerfed and more bugs. I for one would be very happy if the game stayed as it is now and all the bugs were fixed. No, spawn camping isnt a bug. Neither is the way your jet performs against AA or the way some people use a PKM, but the red name tag thing is a bug. Ok. . . . . . .Red

                              Comment

                              • poisonsoul

                                #45
                                Re: DICE/EA....Spawn Gaurd please...next patch ?

                                You know what I hear when I read this.

                                Invincibility hack!

                                So implement it and I'll wait for the hack to appear. Then I'll download and use and pwn. :nerr:

                                Comment

                                Working...