Re: Teamwork
Perhaps I missed the point you are trying to make.
I thought “cover” means occupy the space at the spawning point, so it can’t be used to spawn there. If you mean “cover” as in standing close, watching and killing people as they spawn, then I totally agree with you. I do it all the time when I cap a flag. It’s not an exploit whatsoever, since the opponent have his chance to defend and fight back.
But since you have said “they got their one chance”, I have to assume “cover” means “blocking” a spawn point.
Using this can’t be blamed on players, though, only on DICE for implementing such a poor design. I have to admit it takes a lot of coordination and teamwork to pull it off, but still it’s not a good decision from DICE to allow it. This shouldn’t be a game of chess, where you can’t move your king, if the enemy forbids it.
Sure there must be one.
How about spawning at the flag is made random within the area of the flag?
You kill two birds with one stone:
- you can’t deny spawning at a flag, by blocking all the spawning points.
- you make spawn rape harder, since the enemy is not predictable anymore.
Blocking all the spawn points could become more of an issue now, since squad hopping has been removed. Where should a SL spawn when he’s dead, if the enemy is blocking all the spawn points at the disputed flag? He can’t resign and spawn back on a new SL, he is forced to spawn at a different flag and so loose the fight by lack of representation.
Let me put it another way: what would anybody think when he’s trying to spawn at a flag and he can’t do so, for no apparent reason?! “Stupid bug! Let me report this one, too!”
Originally posted by SERIALBUTCHER
I thought “cover” means occupy the space at the spawning point, so it can’t be used to spawn there. If you mean “cover” as in standing close, watching and killing people as they spawn, then I totally agree with you. I do it all the time when I cap a flag. It’s not an exploit whatsoever, since the opponent have his chance to defend and fight back.
But since you have said “they got their one chance”, I have to assume “cover” means “blocking” a spawn point.
Using this can’t be blamed on players, though, only on DICE for implementing such a poor design. I have to admit it takes a lot of coordination and teamwork to pull it off, but still it’s not a good decision from DICE to allow it. This shouldn’t be a game of chess, where you can’t move your king, if the enemy forbids it.
Originally posted by Chris_Redfield
How about spawning at the flag is made random within the area of the flag?
You kill two birds with one stone:
- you can’t deny spawning at a flag, by blocking all the spawning points.
- you make spawn rape harder, since the enemy is not predictable anymore.
Blocking all the spawn points could become more of an issue now, since squad hopping has been removed. Where should a SL spawn when he’s dead, if the enemy is blocking all the spawn points at the disputed flag? He can’t resign and spawn back on a new SL, he is forced to spawn at a different flag and so loose the fight by lack of representation.
Let me put it another way: what would anybody think when he’s trying to spawn at a flag and he can’t do so, for no apparent reason?! “Stupid bug! Let me report this one, too!”
Comment