TileEntity and TileEntitySpecialRenderer are 2 different things, your registerRenderer method is never called in the main mod class so after loading your mod knows that theres a new tile entity, but he doesnt know that theres a special way to render it
well for this bug well just say that the code in execute in a serial manner so if theres no println that means theres no registration... that woudl also mean that nobody is calling your client proxy registerRendering()
because if something was calling your registerRendering then surelly there would be a print and you would register your tile entity renderer. but since theres no println, then NOTHING in this function is EVER executed
not exactly
if you do System.out.println("thsi code was executed") and "thsi code was executed" never shows up..... can you conclude that ....thsi code was NEVER executed ?
always use something like
System.out.println("yes the coded executed this")
because System.out.println() will only appear like this "2013-07-23 22:14:05 [sTDOUT] " and then you dont know what is sending thsi line, while if you use System.out.println("yes the coded executed this") you know exactly which lines has printed this code
yeah i understand, but this is a java issue not a forge issue, you should be able to find this in google easily
(btw mine has 18-19k , but yeah id consider 10k a big mod )
i obviously use a logger every single day of my life at work. but clearly it may be overkill for a minecraft mod... just saying. maybe im wrong and your mod is reaaaaaally big and you actualy need it. but i consider that im doing a big one and i dont need a logger
why cant you just use System.out.println like 99% of us ? this seems like a lot of effort to see
[sTDOUT][MyMod] penis 1
[sTDOUT][MyMod] penis 2
[sTDOUT][MyMod] penis 3
[sTDOUT][MyMod] penis 4
[sTDOUT][MyMod] penis 5
yeah... thsi makes no sens, this is literally the equivalent of comparing apples and hammers. To the eyes of the compiler this statement makes no sens.