[MC-643] Issue with bringing wolves into the Nether Created: 26/Oct/12  Updated: 11/May/17  Resolved: 08/Nov/12

Status: Closed
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: None

Type: Bug
Reporter: Joshua Ian Messina Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Windows 7
java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b05)
Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)


Issue Links:
Duplicate
duplicates MC-54 mobs are immediately transfered back ... Resolved
Confirmation Status: Unconfirmed
Game Mode: Survival

 Description   

I attempted to bring a wolf with me into the Nether. My Nether portal is in a tight area, so I had to push the wolf into the portal. When I did so, the wolf disappeared as I expected. When I entered the Nether, the wolf was there as well, sitting inside the portal. However, about 1 second after I entered the Nether, the wolf warped back to the Overworld. However, the wolf did not warp back to the Nether in a similar fashion. It remained in the Overworld. I had to lead it away from the portal and then back to the portal in order for it to go back to the Nether. Every time I have tried to bring a wolf with me to the Nether this has happened.

What I expected to happen:
I expected the wolf to remain in the Nether with me.

What actually happened:
The wolf went back to the Overworld

Steps to Reproduce:
1. Push a wolf into a Nether Portal, letting it disappear
2. Enter the Nether through the same portal
3. Wolf is seen sitting for a moment, then disappears
4. Return to Overworld through same portal, wolf is there sitting.

Additional Details:
I don't know if this is relevant, but I am using the texture pack vonDoomCraft version beta 2.7. I patched the JAR file with mcpatcher-2.4.2_03.



 Comments   
Comment by Amaranth (Travis Watkins) [ 26/Oct/12 ]

As mentioned, this is a duplicated of MC-54 and is thus being closed.

Comment by Matti Ruohonen [ 26/Oct/12 ]

I posted a possible workaround in the comments of MC-54, until this issue hopefully gets fixed.

Comment by Chalmes (Jon) [ 26/Oct/12 ]

Duplicate of MC-54

Generated at Sun Jan 12 11:51:44 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.