[MC-8034] While one TNT in a minecart wont break rails, Two or more TNT in a minecart on a rail, with one active breaks all rail and blocks. Created: 21/Jan/13  Updated: 23/Mar/13  Resolved: 21/Jan/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w03a
Fix Version/s: None

Type: Bug
Reporter: Brandon Schneider Assignee: Unassigned
Resolution: Works As Intended Votes: 0
Labels: None
Environment:

Windows 7 :Curent java


Issue Links:
Duplicate
is duplicated by MC-9169 Tnt carts blow up tracks Resolved
Relates
relates to MC-7879 Minecart with TNT doesn't blow up rai... Resolved
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

Put the summary of the bug you're having here

What I expected to happen was...:
Do to new updates track should not break only blocks around the track.

What actually happened was...:
After placing one TNT in a minecrat on an activator rail other TNT in a minecrat explodes as just TNT breaking all track and blocks.

Steps to Reproduce:
1. ... Place an activator rail(powered) on ground with other track set up(round shape).
2. ... Place one TNT in a minecart on regular rail next to activator rail (place on normal rail next to activator rail)you must have two TNT in a minecart on the track.
3. ... Place last TNT in a mincart on activator rail(active) and let the TNT in a mine cart explode.
4. ... All track and block are broken.



 Comments   
Comment by Brandon Schneider [ 21/Jan/13 ]

Just checking have a good day.

Comment by Kumasasa [ 21/Jan/13 ]

One Minecart is ignited by the activator rail ("controlled explosion"), that wil co-ignite the other ("uncontrolled explosion"), therefore -> Working as Intended

Comment by Dean Baset [ 21/Jan/13 ]

Intended. To quote dinnerbone... "Controlled explosions are the Safest Explosions!"
They aren't controlled if they are not blown up by a detector rail. The second explosion was caused by an explosion, not a detector rail, and therefore not controlled, and wasn't safe.

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