stack trace bug
LadyCailinBot opened this issue ยท 4 comments
CMDHELPER-2988 - Reported by kookster
Comment by PseudoKnight
kookster, you use the worst titles in the issue tracker. When I saw this title I checked the author to see if it was you. Sure enough. lol
Anyway, this is a Minecraft error. Tile entity data is stored at a location where there is no block type that supports it. CH is just triggering it by causing a chunk load with pinfo(), which does a line of sight iteration.
(TIP: I've mentioned this before, but use pinfo(player(), index) instead of pinfo()[index]; block iteration isn't cheap)
Comment by kookster
ladycailin said file a bug for the stacktrace and didnt give specifics as to what was causing the issue, so she got a very fancy title. So if anyone is to blame of the title, blame ladycailin. I make these just for her.
Comment by PseudoKnight
Well, I'm no expert on the subject, but if you don't know what to put, just use an important part of the stacktrace, like "Attempted to place a tile entity where there was no entity tile". If it's not obvious what's important, just use the exception name "java.lang.Exception". People who know more can rename it appropriately, but it at least makes it distinguishable from most other issues. java.lang.Exception is pretty non-descript, but at least it's something.
LadyCailin probably didn't have time to look at it. It's theoretically easier to address issues in a tracker systematically, but good bug reporting helps.