[MC-7820] Using /give with large data value on wool crashes game Created: 18/Jan/13  Updated: 06/Sep/15  Resolved: 17/Mar/13

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

Type: Bug
Reporter: Michael F Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: data-values, entites, wool
Environment:

Linux ubuntu 64bit (both server and client). Latest java 1.7. It is also a bit snowy outside...


Attachments: Text File crash-2013-01-18_17.02.52-client.txt     Text File crash-2013-01-18_17.10.02-client.txt    
Issue Links:
Duplicate
duplicates MC-11894 Crash with invalid wool values Resolved
CHK:
Confirmation Status: Community Consensus
Game Mode: Creative

 Description   

When using the command "/give PLAYERNAME 35 1 700", which translates to wool with a data value of 700, it crashes the game. Now creating a wool block with data value of 700 is silly but I wouldn't expect it would crash just ignore my data value. If you were to do the same with glass (block 20) it will ignore you and give you data value of 0. After crashing out I just tried to reconnect and I believe the faulty entity is still around and it crashes me out immediately. Apologies if this is a dupe I have searched and did not found anything smiler.



 Comments   
Comment by Tails [ 26/Feb/13 ]

Note:

Description: Rendering entity in world
java.lang.ArrayIndexOutOfBoundsException: 700
	at aki.a(SourceFile:20)
	at bed.a(SourceFile:6996)
	at bed.a(SourceFile:6588)
	at bfg.a(SourceFile:82)
Comment by Brian [ 10/Feb/13 ]

I found the same problem. It looks as if giving a wool with a damage value over 15 results in an OutOfBounds exception. After this happens, the only way to fix the level is to remove that item from the level.dat, otherwise the level is unplayable.

Comment by Michael F [ 18/Jan/13 ]

If I delete my player.dat file it allows me to login with no problems; however the bug still exists when I then try it again

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