Jump to content

Question

Posted

Title: Tekkit 1.1.0

Version: 1_0_3

OS: Windows 7 Home Pro

Java Version: Java Version 1.7.0_21

Description of Problem:

Minecraft is crashing shortly after the MOJANG screen.

Error Messages:

Minecraft has crashed!

----------------------

Minecraft has stopped running because it encountered a problem; Failed to start game

A full error report has been saved to C:\Technic\tekkitmain\crash-reports\crash-2013-06-08_11.12.51-client.txt - Please include a copy of that file (Not this screen!) if you report this crash to anyone; without it, they will not be able to help fix the crash :(

--- BEGIN ERROR REPORT 58130af7 --------

Full report at:

C:\Technic\tekkitmain\crash-reports\crash-2013-06-08_11.12.51-client.txt

Please show that file to Mojang, NOT just this screen!

Generated 6/8/13 11:12 AM

-- System Details --

Details:

Minecraft Version: 1.5.2

Operating System: Windows 7 (amd64) version 6.1

Java Version: 1.7.0_21, Oracle Corporation

Java VM Version: Java HotSpot 64-Bit Server VM (mixed mode), Oracle Corporation

Memory: 1088405360 bytes (1037 MB) / 1295450112 bytes (1235 MB) up to 3810328576 bytes (3633 MB)

JVM Flags: 0 total;

AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used

Suspicious classes: FML and Forge are installed

IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0

FML: MCP v7.51 FML v5.2.12.716 Minecraft Forge 7.8.0.716 70 mods loaded, 70 mods active

removed for brevitity

>Constructed->Pre-initialized->Initialized

LWJGL: 2.4.2

OpenGL: GeForce GTX 690/PCIe/SSE2 GL version 4.3.0, NVIDIA Corporation

Is Modded: Definitely; Client brand changed to 'fml,forge'

Type: Client (map_client.txt)

Texture Pack: Default

Profiler Position: N/A (disabled)

Vec3 Pool Size: ~~ERROR~~ NullPointerException: null

java.lang.IllegalArgumentException: Slot 700 is already occupied by powercrystals.minefactoryreloaded.block.BlockFactoryFluid@7c2c98cc when adding bau5.mods.projectbench.common.ProjectBenchBlock@53e3b8c4

at net.minecraft.block.Block.<init>(Block.java:340)

at net.minecraft.block.BlockContainer.<init>(SourceFile:9)

at bau5.mods.projectbench.common.ProjectBenchBlock.<init>(ProjectBenchBlock.java:27)

at bau5.mods.projectbench.common.ProjectBench.initMain(ProjectBench.java:97)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:494)

at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)

at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)

at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)

at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)

at com.google.common.eventbus.EventBus.post(EventBus.java:267)

at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:165)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)

at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)

at com.google.common.eventbus.EventBus.dispatch(EventBus.java:314)

at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)

at com.google.common.eventbus.EventBus.post(EventBus.java:267)

at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:98)

at cpw.mods.fml.common.Loader.initializeMods(Loader.java:690)

at cpw.mods.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:206)

at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:448)

at net.minecraft.client.MinecraftAppletImpl.func_71384_a(SourceFile:56)

at net.minecraft.client.Minecraft.run(Minecraft.java:733)

at java.lang.Thread.run(Unknown Source)

--- END ERROR REPORT 784f5996 ----------

Error Log:


Description: Failed to start game



java.lang.IllegalArgumentException: Slot 700 is already occupied by powercrystals.minefactoryreloaded.block.BlockFactoryFluid@7c2c98cc when adding bau5.mods.projectbench.common.ProjectBenchBlock@53e3b8c4

	at net.minecraft.block.Block.<init>(Block.java:340)

	at net.minecraft.block.BlockContainer.<init>(SourceFile:9)

	at bau5.mods.projectbench.common.ProjectBenchBlock.<init>(ProjectBenchBlock.java:27)

	at bau5.mods.projectbench.common.ProjectBench.initMain(ProjectBench.java:97)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

1 answer to this question

Recommended Posts

  • 0
Posted

This is the same crash that gr8wolf posted in http://forums.technicpack.net/threads/tekkit-1-1-0-crash-after-mojang.46522/ , and I'm getting the exact same thing, even after a clean install of 1.1.0. This is likely a good part of why they haven't released it yet, and you need to force the game to launch this version still. I also doubt anyone official is going to help with bugs with unreleased versions. The key part is here:

java.lang.IllegalArgumentException: Slot 700 is already occupied by powercrystals.minefactoryreloaded.block.BlockFactoryFluid@71220f39 when adding bau5.mods.projectbench.common.ProjectBenchBlock@7315a135

There is a item ID conflict between a new pack being added (looks like mod: ProjectBench, item: ProbjectBench Block). It's conflicting with an existing item added by the MineFactory Reloaded block, and seems to be something fluid related?

There's not a lot you, I or anyone else is going to be able to do until they fix the mod pack and eliminate the conflict.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...