Skip to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LexManos

Forge Code God
  • Joined

  • Last visited

Everything posted by LexManos

  1. Kinda need the full log not the 'OMG THERE WAS A CRASH' part, but the actual part that shows WHAT the crash was.
  2. at tconstruct.client.pages.CraftingPage.drawCraftingPage(CraftingPage.java:69) Seems like a error in tinkers construct, go talk to them.
  3. Ah that is actually a legitimate bug, just a oversight in our switch to the gradle system. I've fixed it and it will be in the next build. But pre-gradle builds {such as the one this guy is using} should be fine.
  4. If you did then you moved things around and screwed it up. The libraries folder needs to be there and include the libraries that the installer downloads.
  5. *facepalm* It's our official download site, its linked in like 50 different stickied threads across the forums, as will as linked in the header of every page... But I guess that's not enough...
  6. 1.5.2 is not supported, either read the EAQs to solve the issue yourself, or stop using 1.5.2.
  7. Ya.. gunna need a bit more effort on your end. Please provide more details.
  8. 1.7 is not a long way off, it's rather close. We will be doing a final wrap up 1.6.4 recommended build before we switch over to 1.7 development. Like we do for every MC version. That will be coming soon
  9. You dont edit the MC jar, at all in 1.6+ Use the installer provided in the downloads page.
  10. Basically, 1.7 destroys everything. Especially when it comes to IDs. Not supporting the old method is not a choice made to hurt older mods. It's simply that Minecraft has changed, and people need to adapt. But anyways, speculation is not really important until 1.7 is in production.
  11. The src versions is for writing mods. You want to use the installer if you want to install it into your client -.-
  12. http://stackoverflow.com/questions/513832/how-do-i-compare-strings-in-java
  13. IIRC that particular line means that the player tried to login to a world that is not loaded, for example. They logged out in the twilight forest, and then you removed the twilight forest mod. Simplest way to fix is to kill the player's .dat file. Or you could go in and reset there dimension to 0 using a nbt editor
  14. Forge doesnt reload anything like this. We didnt add anything related to this, this is all either vanilla minecraft, or optifine.
  15. LexManos replied to Techcable's topic in Suggestions
    Lets first off start by saying, that your definition of 'API' is wrong, or, more specifically narrow. Bukkit is a Abstraction Layer Forge is Compatibility Layer {Amungst other things} Forge and Bukkit are both APIs. Hehehehe.. give me a second.. I need to compose myself hehehe Why re-implement something that already exists? If you want a bukkit plugin, go use bukkit... Forge and bukkit have two completely different design philosophies. And, because of that, 1) they can live together {see: MCPC} and 2) You can do things in one that you cannot do in another. Yes, we could start writing a abstraction layer like you want, but we're not going to. Bukkit exists, and the next major system like that should come out is the official one, throwing our hat into that is a futile effort and will just fracture the community more. As for dead mods vs dead plugins... there is nothing wrong with dead mods. Mods die, people move on, typically better mods are produced. And hell if you REALLY want to play a older mod you still can. There is nothing stopping you from loading up a old version of MC and going to town.
  16. Use the Installer for the old version. Or better yet, don't use 1.5.2 anymore. We do not support it.
  17. Interesting, its not telling us anything, If there is an error, something is swallowing it. But either way, i'm gunna blame this on the fact your computer can't handle 512 textures.
  18. Naw, this is normal, as it attempts to download the compressed version of libraries before it downloads the uncompressed version. Note the .pack.xz Only worry about things when it ACTUALLY errors saying the process failed. We could clean it up.. but meh... As for Mojang, our installer traffic is NOTHING compared to there EVERY launch traffic. So they don't care.
  19. industrialcraft-2_1.117.921 is a 1.5.2 mod, update it.
  20. We're american MM/DD/YYYY not DD/MM/YYYY. You can tell this by the 13, as there is no 13th month. And as for 1.7, no we havent made any builds for 1.7 yet. As MCP has not been released for 1.7 yet.
  21. 1.7 is a MAJOR change to the internal code, everyone is going to have to re-write a large chunk of there code as is. We ran into a bit of an issue with how the Mojang team coded certian parts of the games {Anonymous inner enum classes u.u} which has forced us to write a new set of programs to handle that. So the MCP team, cpw, and I have decided to do a bit of house cleaning and code reorganization to move the code base that you deal with in minecraft, closer to the official code base. Namely with the reconstruction of inner classes. However, as this is a major change, we are taking it seriously, and making sure things are put through there passes. Names are cleaned up. We don't get this opportunity often, to re-name classes.. There are also other changes going on with MCP under the hood, that I don't know if i'm allowed to speak publicly about yet. But, I assume you we are working on it. Admittedly, it is kinda annoying me off that it is taking so long to come out, but I know it's for the better. Also, big shout out to AbrarSyed, his work on ForgeGradle is pretty much complete {still has the actual end-modder decompile process to do but meh}. If you guys wanna go check that out. I'm sure he will be glad to have testers. It's a little complicated to setup right now but will be ungodly easy once we actually pull in and start building this stuff officially. Combine the work, with me being hit REALLY hard by the con flu, ya not good. Anyways, just wanted to give another heads up, things are being worked on. The MCP team are working there buts off to get a good release out. But remember, one of the major players, Searge, was hired by Mojang. So he's working on both ends to make Minecraft better!
  22. Yes I saw it, it said IncompatibleClassChangeError: Implementing Class This typically means you screwed up and installed a mod for a different version of minecraf then what it was made for. Also, another note, video logs are a PITA text logs are better. Either way its a issue with the mods in your setup, not something we can handle.
  23. You have the wrong versions of the mods installed for the mc version you're using. Either way, this is obviously a error in the mod.. why did you come here?
  24. I know what the issue is, Im just curious of why it's creating fake players on the CLIENT.... I'll wait till the actual modders bring this up.
  25. Humm hes using FakePlayer in a odd way, namely rendering. I'll have to look into it later, but not sure if I actually wanna fix this one. The FakePlayers were more designed for performing actions in world as a player not rendering them. {Breaking blocks and the like}

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.