JaariAtmc
-
Posts
3045 -
Joined
-
Last visited
-
Days Won
112
Everything posted by JaariAtmc
-
Make your own thread, don't hijack other peoples threads. That being said, add JavaLegacyFixer to the modpack you are trying to play.
-
The issue isn't the zipfile, the issue is that you are using a Forge version (1180) that is so ancient that it actually doesn't contain the fix for Java 8 (1217). You really, REALLY need to use the recommended or latest version of Forge for 1.7.10 (R:1558 | L:1614)
- 1 reply
-
- 1
-
-
I did a bit of random searching, the case can be found here: http://api.technicpack.net/modpack/modernization-prereleases The main modpack can be found here: http://api.technicpack.net/modpack/modernization-pack
-
Besides that, you are not listening, but we already know that you don't do that.
-
[B#347] 2016/03/28 17:11:33 [INFO] Picked up _JAVA_OPTIONS: -Xmx512M Please download this file, then RightClick->Run as Administrator. This should clear Java Settings that are being stored in your OS, which interfere with Technic. This script was written by the Moderator Khio, and can be trusted. http://iamtrue.net/clearJavaEnvVars.bat
-
Tekkit Legends crashes when started
JaariAtmc replied to EasterBqnny's topic in Tekkit Legends Discussion
Hello Easter, In order to help you, we will need your Launcher Log. You can find the log here: In order to get your logs, please go into the Launcher Options (upper-right corner), then on the bottom-left corner of that screen, click \"Open Logs\". The logs are all called `techniclauncher_YYYY-MM-DD.log`, with YYYY being the Year, MM being the Month, and DD being the day. We need the Logs from when you were/are having your issues. Please upload the contents of the log to paste.ubuntu.com and give us the link. -
For your first question, you would have to compare mods (and the versions) for that. I only have the modlist of your current pack. For your second question, please look into this Plugin, as it allows you to remove blocks from console. It also allows you to check what the block exactly is, maybe an idea to confirm what kind of mobspawner it is? Mind that the plugin has been made for 1.6.4.
-
Well Jake, As Plowman has said, as well as what you could've easily found on Google, you either need to talk to the moddev of GalaxySpace, or you need to change your configs (and make sure client and serverside is the same). Then again, why listen to me? Thought you had such a great team to fix this for you. (For anyone wondering, there's a bit of friction between me and "Modernization".)
-
Upload the contents of the log to paste.ubuntu.com and give us the link to it. We wouldn't have been able to view the attachment anyways, unfortunately, as they do not work on these forums.
-
-
"...Looks into crystal ball... Nope, nothing sorry. We need your log if we want to help you. In order to get your logs, please go into the Launcher Options (upper-right corner), then on the bottom-left corner of that screen, click \"Open Logs\". The logs are all called `techniclauncher_YYYY-MM-DD.log`, with YYYY being the Year, MM being the Month, and DD being the day. We need the Logs from when you were/are having your issues. Please upload the contents of said log to paste.ubuntu.com and copy the link you get. We need it to check what is causing your error.
-
Please download this file, then RightClick->Run as Administrator. This should clear Java Settings that are being stored in your OS, which interfere with Technic. This script was written by the Moderator Khio, and can be trusted. http://iamtrue.net/clearJavaEnvVars.bat
-
You have a corrupted TileEntity (in this case, a monster spawner) at the following coordinates: 101,19,125 You will have to delete the mob spawner if you want people to stop crashing.
-
That's because you have (and keep having) 32-bit java installed. Install 64-bit java, found here: `Windows Offline (64-Bit)`. http://java.com/en/download/manual.jsp
-
" Minimum build GalactiCraft3: 1.7-3.0.12.446" "GalacticraftCore{3.0.12} [Galacticraft Core] (GalacticraftCore-1.7-3.0.12.375.jar)"
-
Oh haha, you got a case of Xmx 256M/512M/1024M. Should've figured that was a possibility too.
-
The download link of the modpack changed, please update this on the launcher as well. As of now, both links you provide are unusable.
-
Try updating your Intel HD graphics card drivers over at https://downloadcenter.intel.com/ (use the automatic update button) If it doesn't work, downgrade to java 7u80. http://cdn.lemonmc.com/jre-7u80-windows-x64.exe
-
Hexxit fix doesn't work at all. Your mapwriter config file has corrupted, with a random apostrophe being the cause of it. You can look for the apostrophe and remove it, or you can just delete the config, but this results in the deletion of all your waypoints (markers) on your minimap. You can find the config file at C:\Users\Celine\AppData\Roaming\.technic\modpacks\hexxit\saves\mapwriter_mp_worlds\serverIP\mapwriter.cfg
-
Besides this, you are using java 7/8 64bit right?
-
Put RAM allocation at 3-4 GB. You are allocating too much RAM (and yes, this happens so often).
-
You forgot to remove DamageIndicators. Remove that, try again and post a new log if it still crashes.
-
Do you happen to have Windows 10 and Intel HD graphics card?
-
Let's see: InventoryTweaks, Optifine, TabbyChat, Version Checker, Waila, Xaero's Minimap and Custom Main Menu. Possibly Resource Loader and the Voice Chat mod.
-
Hehe, you wouldn't believe (or you actually would) how often this thing happens to people...