Forum Discussion

Screion's avatar
10 years ago

Unrevivable Insta-death Death

If for whatever reason a players body falls into deep water or any other insta-death area they will die again instantly after revival. It does not matter if another player revives the player, if the player uses a self-revive or the end of the wave revives the player.

This has already happened to me twice in real coop Ops environments and is easy to reproduce. And if the player gets automatically revived at the end of a wave he ends up unrevivable for the entire next wave.

3 Replies

  • Anonymous's avatar
    Anonymous
    10 years ago

    This problem seems very exploitable in multiplayer and private games for easy revival experience (if what you said about players being able to revive is true)...

    It is strange as an "insta-kill zone" (or an out of bounds zone) would vanquish the player though the game is intended to make the player "unrevive-able" in this state to prevent this bug from occurring. The best way to avoid this is to stay close to the intended areas so minimal bugs would happen (as I never encountered this bug once).

    From what you said, you somehow bypassed the "unrevive-able" trigger in "insta-kill zones" allowing for self-revives and player revives to be used though this is useless as you would be revived in the same "insta-kill zone" that got you in this limbo in the first place. To clarify, does the automatic revival re-vanquishes them or leaves them "unrevive-able" once vanquished by a enemy? If it is the second option, it is likely the game thinking you would have to be vanquished in an "insta-kill zone" hence postponing it until it receives the information of "you have been vanquished".

    Sorry I may not be able to give you a wanted answer but I hope this might clear things up for you. If you find this useful, please press the XP and Accept Solution button if needed. 🙂

    I hope this does not harm your experience again. Have a nice day!

    -VoltScience: Exposition Mage

  • Screion's avatar
    Screion
    10 years ago

    @VoltScience

    Let me give you an example so you understand what i mean:

    You play as Imp. You are down to 5 HP. A Cactus is shooting at you. You use a double-jump in hope to avoid the shots. The Cactus hits you mid-air, you are out. However that projectile accelerates your now dead body to the speed of light and fires it to the far end of the map. That far end is filled with deep water and your body sinks to the ground.

    The spot where the projectile hit you now emits an aura for revival. Now a nice Scientist comes by, notices the aura and revives you. However your body is in deep water and the revival will bring you up where your body is. Which of course insta-kills you.

    Video demonstration:

    https://www.youtube.com/watch?v=vriHC0fiJq8

    The original GW also had such issues where you could be revived with your body being stuck in the ceiling. Which caused you being stuck inside the walls. Halfway outside the map. This has been addressed by reviving players on the floor and no longer in the ceiling.

  • Anonymous's avatar
    Anonymous
    10 years ago

    @Screion

    Ah, now I understand. Thank you for clarifying. It seems to be a bug triggered by another bug (or bad mechanic) which is the cactus shooting your (rather sensitive) rag-doll corpse. This just sends you flying into an insta-death zone which gives your effect.

    Popcap should be fixing this bug by reducing the knock-back of projectiles on rag-doll corpses to ensure such a flying effect should not happen though it should be fixed overall by adding another trigger flag/event flag to detect you are in an insta-death zone overall rather than the "you got vanquished by the zone" flag they current have in place which it simply vanquishes you and makes you unrevive-able.

    -VoltScience: Exposition Mage

About Plants vs. Zombies™ Franchise Discussion

Zombies trying to enter your house? Keep them in check and discuss the best gardening techniques on the community forum.27,692 PostsLatest Activity: 35 minutes ago