Minecraft Username: @ChargerBoltz5
Brief Description: I am not taking damage while in the Nether
Instructions: 1. Try to hurt yourself. 2. Watch health bar not change.
How many times did you recreate this bug?: Several, with different types of damage (falling, fire, lava)
Result: No damage taken
Expected Result: Damage taken
Evidence:
**EDIT** Damage seems to be working now :p
Thread Tools
Thread Tools
-
ChargerBoltz5 BuilderBuilder ⛰️ Ex-President ⚒️⚒️
- Joined:
- Jun 30, 2014
- Messages:
- 1,397
- Trophy Points:
- 28,090
- Gender:
- Male
- EcoDollars:
- $0
- Ratings:
- +1,340
-
OlympiansAreGods Building FanaticEcoLeader ⛰️⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ III ⭐ Premium Upgrade
This is hapening to me :/
-
@JamieSinn figure out what is going on, and we will discuss a proper fix on skype next time we chat.
-
generaljoecool BuilderBuilder ⛰️ Ex-EcoLeader ⚜️⚜️⚜️
In the case that the explanation I gave in-game isn't enough I'll write up the full explanation. If there are any more questions about this, I will gladly answer to the best of my ability.
Set up:
Make sure you have any / all cheats toggled off and /fly disabled to make testing easier.
Go to the border of spawn of spawn, and set two homes. One inside of the spawn region, which I will refer to as "NTest1" and one somewhere outside of the spawn region, which I will refer to as "Ntest2".
Information on reproducing the bug:
Using home Ntest1, or any other method that will teleport you into the spawn region -- such as /Spawn or walking through the nether world portal at spawn -- will grant you immunity to all damage sources even after you leave the protected region.
In addition, it seems that a user that entered the Nether this way will be able to normally damage other non-bugged users in pvp, however remain completely immune to taking any damage from the person they are attacking.
Information on how to enter with normal damage:
Entering the nether from a means that doesn't teleport you into the spawn region -- like a home outside the spawn region (Ntest2) -- will allow you to take damage normally. Walking into the spawn region and walking back out will still allow you to take damage normally once you leave the protected region. There does seem to be an exception to this though. Where if someone attacks you while in the spawn region, it will then apply the damage immunity to all types of damage, as if you teleported into the spawn region.
If a user that is taking damage correctly, attacks a user that cannot take damage, it would cause the following effects:
- Particles will emit from the attack
- The sword will graphically show it has taken damage, however /dura shows that the item has taken no damage
- The damage-bugged user will not flash red to indicate any damage was taken, or play any sounds that would go with attacking.
Notes on testing:
- There does not seem to be any randomness at all to the testing, as every test conducted in the same way will yield the same result
- Reconnecting to the server does fix the issue of not taking damage as long as it is done outside of the spawn region.
- Taking fire or fall damage while in the spawn region might be related to this bug, however I am unable to get an answer with certainty of if that is an intended feature or a bug.
-
@generaljoecool: Most of that data fits the bug information I collected in a thread in march. (Although the graphical PvP analysis is new :p)
However, one thing doesn't match...
-
generaljoecool BuilderBuilder ⛰️ Ex-EcoLeader ⚜️⚜️⚜️
I see what you are saying 314, and I decided to do more testing on the matter. First off, I always thought that taking fire and fall damage in spawn was an intended feature change, however I added to the notes of it being a potential bug -- as no one I asked was able to give me a definitive answer of if it was a bug or not.
In addition, while doing further testing on walking in and out of the spawn region, I was able to find another reason that caused damage to not get correctly re-enabled, and I have edited my post to include it. I still believe there is no randomness in this bug, just more ways to cause it to happen that aren't discovered yet. -