Tinker's Construct Game Breaking Bug

[Dlane_skyward]

So I found out that if you place any of the "Seared" blocks on bedrock level it will instantly crash your game. I was playing around in creative mode, trying to extend a smeltery down further, and when I tried putting the seared bricks on Y: 0, I got this crash http://pastebin.com/7GZy5SeF . The world is still playable, but if you load the chunk you did that in afterward, it will crash again. When I first did this, it was on my server, so to get back on my server I had to delete my player data. When I tried teleporting back the that area, my game crashed.

Known packs - FTB Unleashed 1.1.3 and FTB Unleashed 1.1.6

 

[Yusunoha]

So I found out that if you place any of the "Seared" blocks on bedrock level it will instantly crash your game. I was playing around in creative mode, trying to extend a smeltery down further, and when I tried putting the seared bricks on Y: 0, I got this crash http://pastebin.com/7GZy5SeF . The world is still playable, but if you load the chunk you did that in afterward, it will crash again. When I first did this, it was on my server, so to get back on my server I had to delete my player data. When I tried teleporting back the that area, my game crashed.

Known packs - FTB Unleashed 1.1.3 and FTB Unleashed 1.1.6

you might want to post this over here http://forum.feed-the-beast.com/forum/modpack-bugs.126/

 

[Juanitierno]

Tinkers construct has a github where you can report bugs: https://github.com/SlimeKnights/TinkersConstruct

 

[Pokefenn]

All bugs for TiC 1.5 are directed to FTB, i do not suggest you report bugs to them for things like this...

 

[Yusunoha]

it can be considered a heads-up for other players to not do this in their current world with these modpack versions

 

[Sunstrike]

Just to be sure people are aware of this; the TCon dev team policy on bug reports is "Don't report stuff for old MC versions" -- Right now, this means we only take 1.6.4 bugs. Other bugs should be reported to pack maintainers, not us and definately not our Github tracker, which is for current issues alone.

That said, if you reproduce it in 1.6.4 with latest dev build, we'd like to hear about it! Our latest builds are available over on MCF or from Tanis (our build server).