[MC-3786] Ghasts firing at a portal can deactivate it, potentially trapping someone in the nether Created: 24/Nov/12  Updated: 26/Dec/12  Resolved: 24/Nov/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.5
Fix Version/s: None

Type: Bug
Reporter: Kellen Peterson Assignee: Unassigned
Resolution: Works As Intended Votes: 0
Labels: None
Environment:

Survival multiplayer server


Confirmation Status: Unconfirmed
Game Mode: Survival

 Description   

We had an interesting experience today! We have a portal on our multiplayer server to the nether, and some un-scrupulous person took out a few blocks of our portal room - a ghast then fired at me through the hole, hitting the portal! The portal was deactivated, and no more purply goobly doorway for me. I happened to not have any iron on me at the moment.. I didn't want to have to suicide and lose all my stuff!

Anyway, a friendly server denizen offered to relight it, but it was still active on the other side! He went through it anndd... it created a new portal 6 spaces away from the original facing a different direction.

Apologies if as designed, hopefully someone at least gets a chuckle out of this.



 Comments   
Comment by [Mod] Torabi [ 26/Dec/12 ]

What I find odd is that it doesn't either deactivate the portal on the other side, or reactivate the nether portal when someone goes through from the other side.

I suppose this is because it's searching for the nether portal blocks itself, and not the obsidian structure, but when this happened to me, the second nether-side portal overlapped the first one. It was messy.

Comment by Raphael [ 24/Nov/12 ]

No.

Comment by Kellen Peterson [ 24/Nov/12 ]

Should the portal be killed on the other side though in this case? That was the confusing part.

Comment by Kumasasa [ 24/Nov/12 ]

Life is no bed of roses... Not even in Minecraft

Comment by Raphael [ 24/Nov/12 ]

Yes, its intended. Never go into the nether without a lighter!

Generated at Sun Jan 12 12:02:23 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.