LexManos

Your suggestions are good in theory on projects that have full control and want to provide all the abstraction out of modders hands. This IS NOT what Forge is. Forge is spcifically desinged to go against this type of design. If you want a abstraction layer and data orientated mods, youyou out of luck in the minecraft community. This may be something we introduce in the future (once i get forge and fml merged, get some of the update processes streamlimed, deal with other non-forge projects, and so forth). But for now not going to happen because that is not what this project is.

at mrtjp.core.world.BlockUpdateHandler$.onTick(blocktickhook.scala:46) mrtjp is broken, remove it.

I have looked, and speak with the Mojang devs often. There is nothing really important in the 1.8.3-7 updates that Forge doesn't already provide. And if you don't want to wait then by all means start updating yourself. Decobfusicate all the changes mappings for the new MC version. Address the reflection and generics changes that were introduced. Deal with the FML/Forge code base Merge. Remember while doing all of this to maintain as much backwards compatibility as you can. I was HOPING to have the update done last week so that there would be a week of testing before I went off to minecon. But i've been sitting here twiddling my thumbs waiting on Abrar. Hes JUST NOW finished {I think?} so I will be looking into STARTING the update process tomorrow. I fly out tuesday morning so there won't be much I can do for tuesday/wednesday. So, to surmise, either help, or quit bitching. Also I know what i'm talking about when it comes to shit crap.

Ya pretty much. You start reading the stack top down, you had java internals then scala internals, which are all known to be fine. And the you his this mrtjp stuff which is a mod and is what is calling the loop thats triggering the error. And then below that is forges event code which i know is good and doesnt have anything that would cause that exception. So mrtjp it is.

Do note coremod. We have plenty of events for you to do whatever the heck you want on the screen -.-

We do not support 1.6.4 on the forums anymore, update.

Forge is currently on 1.8.0 There is no real benifit for 1.8.1+ so we are using this time to do some reworking of our systems. Once Abrar finishes everything up {And I get back from Minecon} i'll be doing a 1.8.7 update. For now tho, there is no reason you as the end user should care for 1.8.7 vs 1.8.0 Forge. All major security/bug fixes are in Forge directly and don't need the update.

You 'mrtjp' mod is throwing an error. Remove whatever it is.

Update to 1484+

I'd advise just removing optifine, but to each their own. Point is it is not current compatible with the latest version. They need to update on their end.

Optifine needs to update.

Not sure to much about the perspectives but that is a equivelncy to the 1st/3rd person transforms that items have. As for IRetextureable you implement that in your model class, and if the blockstate.json says it needs new textures it calls this function. This is to allow you to use one model object on disc, and just retexture it using the blockstate.json. For example: Wool would all use CUBE_ALL with each state specifing a different colored texture. See: http://mcforge.readthedocs.org/en/latest/blockstates/forgeBlockstates/

Not sure how that is working.... Try adding -Dfml.skipFirstTextureLoad=false to the java arguments. Somehow Minecraft is detecting that your graphics card can not support a texture large enough to stitch everything together. Sadly this doesn't have much context in the 1.7.10 version {Why are you using 1.7.10?} in 1.8 it has a lot more debug data.

Basic modding You installed a 1.8 coremod On 1.7.10 THIS NEVER WORKS

So you've narrowed it down to 30 builds, mind being a bit more specific, a lot has changed in 30 builds. This is why we have the build numbers. Wither way yes, I'm gunna yell at fry, pretty sure hes the one who borked it.

Text is always better -.- But you have a 1.8 coremod installed on 1.7.10, this will not work.

[19:37:10] [Client thread/ERROR] [FML/]: The mod GravityGun (GravityGun) requires mod versions [iChunUtil@[5.4.0,6.0.0)] to be available [19:37:10] [Client thread/DEBUG] [FML/]: Mod sorting data [19:37:10] [Client thread/DEBUG] [FML/]: GravityGun(GravityGun:5.0.0): Gravity-Gun-Mod-1.8.jar (required-after:iChunUtil@[5.4.0,6.0.0)) [19:37:10] [Client thread/DEBUG] [FML/]: iChunUtil(iChunUtil:5.0.0): iChun-Util-Mod-1.8.jar (required-after:Forge@[1.8-11.14.0.1281-1.8,)) Tho im not quite sure why it is not showing you the friendly 'missing mod' screen...

Interesting, this is indeed the fireball. Something is causing it to not find the particle texture for it. However if it doesn't find the specific one the model mesher should return missingno not crash. Try without some of the coremods you have installed. If you could track it down to the exact build tho it would be nice. Reporting it to fry, looks like he broke more crap.

Then talk to chickenbones

Update to build 1482+ and post your FML log. I added some debug data to this to see what is going on. This doesn't really tell us anything beyond your gfx card cant handle minecraft.

logs

Try lowering your view distance, and also try cyceling your mods out, something is trying to render things incorrectly.

Well have you tried it without NEI? It does some rendering things that could derp up the state. This looks like lighting is being turned on/off.

You're installing a REALLY REALLY old version. Use the recomended 1.7.10 build. files.minecraftforge.net

https://github.com/MinecraftForge/MinecraftForge/commit/4235ca36ea32a89458e018677418e3fda1b84711 We can not support mods such as Optifine who wholesale replace classes such as this one causing the missing method error. Its up to their end to fix that. As for your second issue with your resource pack. That is because the pack is broken. Vanilla hides broken models in variants. We do not. Hiding these broken models does not allow the resource pack creates an opportunity to fix them. So go yell at the resource pack creators and tell them to fix their broken models. The logs should spit out exactly which models are broken.