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. If it's rendering issues the first test is always to try without optifine.
  2. A difference saying 'only on right' means that you've only ADDED stuff, which is to be expected when you add mods. I would say *something* derped up when your HDD got full that wiped out the ID list for the first run. On the server, you don't have a choice of if you wanna run with the changed id set or not, it just runs. What I would do is try and find your old saves from before things derped, and see what the id configs were. Make sure they are the same. If not, you could just continue on as is and have your chunk loads at 4095.
  3. Read the eaqs and don't report your own post to get extra help -.-
  4. Interesting, nothing is telling us what is wrong, there isn't much we can do to suggest, beyond just trying different mod combinations to try to find out whats causing it. Nothing in the log is helpful.
  5. Actually 1.5.2 is before they started including the version number in the file name, so you MUST remove it. Or, you could add the jar to your class path manually.
  6. For the love of god, either use the spoiler tag, or pastebin/gist Scrolling through 40 pages of logs ach time we look at the thread is bad... anyways it's NOT the same error this one is different: 2013-11-29 11:26:18 [sEVERE] [ForgeModLoader] A fatal exception occurred during the server starting event java.lang.NullPointerException at universalelectricity.prefab.flag.ModFlag.readFromNBT(ModFlag.java:34) at universalelectricity.prefab.flag.ModFlag.<init>(ModFlag.java:27) at atomicscience.ZhuYao.serverStarting(ZhuYao.java:719) Seems like a issue with UE/atomic science.
  7. Check your AV's and Firewalls something seems to be blocking your connection. I hear Avast likes to be a pain. Might wanna disable it, or, download the libraries manually as instructed in the EAQ.
  8. Use the installer, and use the recommended build.
  9. Try deleting: C:\Users\Nwachukwu\AppData\Roaming\.technic\tekkitmain\saves\Survival\DimensionalDoors\Limbo-23\forcedchunks.dat Seems that it has gotten corrupt and may be killing your startup.
  10. Looks like a energy net issue in IC2 and 'advGenetics' You'll have to speak with there authors to figure out anything more.
  11. Yaya you added logs! Simple use, use the recomended build of Forge. The latest is not compatible with Optifine.
  12. Well, there was this solar flare that happened to pass just right pass the moon, causing the solar radiation to bounce off the moon and come through your window at just the right angle to fry the exact bits on your hard drive that were storing optifine. Causing a single 1 to flip to a 0. And well, as you well know a single misplaced bit can cause the entire thing to go haywire! You need to go our and make sure all of your windows are covered in aluminum foil so that this won't happen in the figure then you have to go in and figured out exactly which bit got flipped by opening optifine in notepad and just trying changing random pieces. and hope that it works... Or, if you can't tell my sarcasm, give us the logs or we have no way of knowing what they heck is wrong with your setup -.-
  13. Looks like ATG is not 1.6.4 compatible. You need to tell them to update, it's a simple update.
  14. Seems like a issue with pixelmon, try talking to them.
  15. mod_ZanMinimap{Not available} [mod_ZanMinimap] (ZansMinimap1.6.4.zip) Unloaded Thats not a server mod.
  16. Run it manually from the console and show us what happens.
  17. There is nothing preventing you from opening two on our end. Logs would provide more detail, it's probably locking a file. You may want to change the --gameDir of one of the instances.
  18. you dont edit jars at all. Use the installer. Also, make sure you're using the recommended build.
  19. Then you need to run the jar manually, and get us a log. There is always a log to post somewhere. If there is something happeneing on your screen even you clicking a mouse TELL US.
  20. For those who haven't seen: https://mojang.com/2013/11/minecraft-snapshot-13w48a/ We are working on it, there is a LOT of changes going on behind the scenes to make the codebase saner. And give everyone the ability to work on things how they want to. Combine that with the fact that we knew 1.7.3 was coming, you can see why we are taking our time to get things done correctly. MCP wise everything is looking great, I'm hounding on Abrar to get the gradle side for the update done. Then it's time to work. We'll see how stable 1.7.3 is, and see if there's gunna be a 1.7.4. Sadly, as MCP is a closed source thing {though some of it has become open} you guys can't see all the work we're doing but trust me, we're working on it. But re-doing almost the entire modding process is not a easy task.
  21. run the forge jar, not the minecraft_Server jar. The minecraft_server jar is completely untouched and is used as a library.
  22. The latest should work fine. The recomended is pre-gradle and as such we cant change the place the assets are downloaded from. What you need to do is go into your .minecraft folder and copy the assets folder into the jars folder in your workspace.
  23. Whatever service or mod you're using is adding a custom logging system which is breaking the one MC/Forge uses. I'd talk to your server host if they are the ones applying that logging.
  24. NBT data is not synced between the client and server. So if you change anything on the server you will need to send a packet to inform the client that it's changed.

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.