LexManos

There are a plethora of ways to get the logs GIVE THEM TO US. Without them all I can say is you screwed something up. No clue what, that would be in your logs.

It is not our job to be compatible with mods. We keep as much vanilla compatibility as we can. beyond that mods need to update. As for this in particular, not our problem that he hasn't updated to 1.7. It's been out for almost a year now he is being lazy. Also as a note, the methods he is going about doing what he is wanting to are stupid and do nothing but destroy compatibility with other mods. You should stop using this mod immediately and tell him to behave.

I know exactly what you want to do. And I know you can do it without editing base classes You have reflection You have ATs You have many alternatives.

Yes Yes Nothing you are wanting to do requires base edits. Please do some research and try to solve your own problems. Its actually rather simple and is done quite often in Minecraft. There is a plethora of ways to deal with it.

This can be done without any base edits, you can do it yourself So most likely it will not be accepted unless you provide a good reason.

It is more likely that you're using it wrong. So post code, post loaded binaries. -Dlegacy.debugClassLoading=true -Dlegacy.debugClassLoadingSave=true

This is not a Forge issue, if your entities are written correctly they will render. As a personal note, I do not support nore endorse anything related to Pixelmon so I am locking this thread before it goes any further.

You have somehow messed up your save, perhaps your server crashed while running and was not cleaned up properly. I would suggest rebooting the computer the server is running on. And then backing up your world, and deleting the level.dat.lck file in your save folder.

However you are running minecraft is adding its own security manager to java, this is not supported. You should run minecraft normally.

You need to make sure you run your 1.6 world using the LATEST 1.6.4 version of Forge AND THEN update to 1.7.10. This will work fine IF the mods are prepared for the update. If not shit like this happens and you have to start new. It's up to the mods to fix update issues like this by having a '1.7 prep' version you can run that will save the proper information to the world.

You will have to contact your server provider, it appears they are not installing all the necessary libraries that Forge needs. log4j being the current one in question, which is provided by the vanilla minecraft_server jar. This si a configuration issue with your provider or yourself, nothing to do with us.

We do not support 1.6.4 anymore more in any way on this forum. Update.

No way in hell are we supporting 1.2.5, let alone DEVELOPING for 1.2.5. You are on your own if you wish to work on such old systems, and judging by the fact that you cant solve a simple issue like this, I don't think you should be doing what you are doing.

http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html#jre-8u11-oth-JPR

Looks to me that one of the mods you have installed has set the max stack size of torches to 16. This is not a vanilla or forge thing, you would need to start taking out mods and seeing which one will cause it. It's rather simple, create a single player world in creative and try stacking things, remove a mod and try it again. Rinse and repeat until you can stack again, and it is most likely the last one you removed.

1.6.4 is no longer supported, update to atleast 1.7.10

This is not a 'fix' this should just be a json array of all values not just the one hand picked values {and jesus did you hand pick it in a inefficient way!}

{no-classifier}: Base jar decomp: Decompiled code, post cleanup but pre patches/injection fmled: fml injected/patches fmlinjected: added fml code mcp: binary in mcp names mcped: ... shouldnt exist... may be old version that is dea src: Source for recomped includes fml patches, forge patches and fml/forge code in MCP names srg: the binary classes in srg form {unique identifiers} There are others, but they are essentially the same stuff, just various stages of being ready for you as a modder to use.

At this moment, no it is not officially supported. It is going to be a developmental branch that will eventually get merged into master once our changes we want to do are fleshed out and tested. ONLY THE OFFICIAL MASTER BRANCH is supported.

As on the pixelmon forums, most likely an issue on their end, if not they should be smart enough to file a proper bug report.

1.6.4 is not supported anymore, update.

Update: 02/02/2014: http://www.minecraftforge.net/forum/index.php/topic,27505.0.html Fry has finally finished up the ModelLoader registry, 1.8 is officially released. Get to going! Update: 11/26/2014: Whelp guys, since it's my birthday have a present: http://www.minecraftforge.net/forum/index.php/topic,22782.msg129821.html#new Forge: It's time to say... In light of recent events over in the bukkit community, 1.8's pending release, and the EULA changes. It has come time to say, Forge WILL continue to be updated and developed. I can understand everyone's feelings about the EULA changes, and the fact that 1.8 will be a colossal update, especially on the client side. It is no secret that a lot of us who are working on major projects for the community feel stressed, overworked, attacked, {insert any bad adjective/verb here}. That being said, unlike EvilSeph and TNT, I work on Forge as my sole source of income {the adsense on the forums, adfly, and a bit from Curse} I have made no secret of this. This means that I don't have the luxury of just being able to quit. Beyond that, I truly do enjoy what I do. I love to program and I love to tackle issues, digging my hands as deep into a project as I can. But at times, the stress of the community can get to me. Recently, being attacked by those in the community I trusted because they got persuaded by someone who should of never had that influence -.- Combine it with the stress of a pending update, and the 10~ projects I have to update for that u.u. My solution, Vacation! This was intended to start this monday, the 25th, however because of the certain person above, I started it early {last Wednesday}. For my vacation, I will be staffing a awesome anime convention called Kumoricon. I have been staffing this convention for almost 10 years so {god I feel old} so this is not unplanned. This is happening in Vancouver, Washington, Officially it is Friday-Monday, but well, staff works a lot longer then that. If anyone is in the area, or are planning on attending give me a shout. This is also the reason I am not up in Seattle with the rest of the FTB/Curse team. As both conventions are the same weekend. It kinda sucks, but Kumoricon > PAX, as we were here first, so suck it you all! So, what does this mean for Forge? Not much, the plan was always to take the 1.8 update slow as it is a massive re-write to the rendering system, we are taking this opportunity to re-write some things in Forge/FML that we have wanted to do to hopefully increase performance/flexibility/stability of Minecraft itself. Once I get back from the convention on Tuesday night I will probably fall into a post-con coma for a day or so. And then I will get to work updating MCP/FML/Forge/.... So just hold on to your hats. For modders, 1.8 isn't actually that scary of a beast, the MAJOR change is to the rendering system to introduce model based blocks instead of the RenderBlocks mess. At this point I do not know the full extent of this change. Or any of the other changes that were introduced. Tho I can say just like every other MC update there is a lot of boiler plate code that MAKES things look like a big change when it's not {for example one thing you will run into is A LOT of functions have changed from taking (int x, int y, int z) to taking (BlockPos position)}. So don't worry too much, when we get closer to actually updating we will have someone make a primer of the important changed bits. Once Forge is out for 1.8, 1.6.4 will be even MORE dead. I will expect the community as a while to start shaming those modders who are still developing for it! Everyone knows my stance on that, so I won't get into it, but please for my sanity and yours at least update to 1.7.10 u.u So ya, I will see you all next week after con. Note: The title is supposed to be a joke, but i'm bad at them. I fully support Seph and TNT in whatever they wish to do or not do. Life goes on I hope they find another project that is rewarding and enjoyable to them. Update: Okay, so I am now back from con. Few things to note, I worked 22 hour days at the con, rolled my ankle twice and am currently recovering and decompressing. Then I come back and catch up on all the current drama that is going on in the minecraft community, most notably of which is Wolf's DMCA to Bukkit. I will refrain from making public comment about this as 1) I am not a lawyer {tho I do have way more experience in this type of law then most of you} 2) I agree with his intentions if not the manner in which it is going down. 3) Drama dramama dramamamamamamamammamamaqmam So, as it sits, we are going forward with updating to 1.8, we are revamping and discussing a lot of how we are going to address things that will be changing at the core level of FML/Forge/Modding. Don't be scared it's actually for the better! And should make modders lives even easier! As such I expect to have a buildable version of 1.8 done *sometime* this week, but I have no clue when a release will be coming. So just hang on. Edit by luacs: https://twitter.com/LexManos/status/508198938629771264

CustomModLoadingErrorDisplayException

It continues on. As for time being changed by /time set, you have to allocate for that in your time comparison. When it changes, you're pretty much screwed anyway for getting real numbers, so you just have to deal.

Its inside the forgeSrc jar which is attached if you use any standard IDE. Or you could view the source on our github. Or you could view the source in the userdev download Or you could view the javadocs in the javadocs download There are plenty of places to find things, basic of development, reference documents.