xXxElitexXxgecko is a bug abusing jerk!

xXxElitexXxgecko is a bug abusing jerk!
Post by: chumii - April 25th, 2016, 4:40:15 am

So me, A34sponge, PieterHenry, flagrocker and a bunch of other people were going to team up on xXxElitexXxgecko because he is a major jerk. so we were gonna PVP in the warzone, but before we got out of the safe zone he killed like 5 of us. i dont know how you can kill players in a safe zone but he did it. 5 times. :evil: :evil: :evil: :evil: :evil: :evil: :evil: :evil:

xXxElitexXxgecko is a bug abusing jerk!
Post by: DaCoolCreeper - April 29th, 2016, 11:08:42 pm

He can do that if he is on fire and you hit him. Called Combat tag. You used to be to disable it with /ct

Re:xXxElitexXxgecko is a bug abusing jerk!
Post by: SiggiJG - May 2nd, 2016, 8:20:09 am

If you're in PvP, and then enter the safe zone, you will still be vulnerable to PvP until you are left unharmed for at least 20 seconds. This is to prevent players from trying to escape PvP. Are you sure you were in the safe zone the entire time?

If you enter /pvp command, this also makes you vulnerable to PvP from anyone else who also types that command, even if they're in the same faction as you, or if they're in an allied faction.

Re:xXxElitexXxgecko is a bug abusing jerk!
Post by: chumii - May 20th, 2016, 3:51:24 pm

Yes we were in safezone 2 minutes after we PVPed and he killed us.
Unfair? Loss of invis pots and power bow

xXxElitexXxgecko is a bug abusing jerk!
Post by: patman96 - July 2nd, 2016, 11:22:49 pm

Locking due to old topic.

-Pat

Powered by SiggiForum. Copyright © 2018 Siggi.io. Use of this website, and the CubeBuilders game server subject to Terms of Service.  View our Privacy Policy.  CubeBuilders is neither endorsed nor affiliated with Mojang Synergies AB.  "Minecraft" is a trademark of Mojang Synergies AB.  Cookies are stored in your browser by this website for the purposes of improving your experience.  By accessing this website, you consent to the placing of cookies on your system. For information on Cookies, see our Cookies page.